@camstack/addon-provider-homematic 1.2.161 → 1.2.163

package/CHANGELOG.md

@@ -7,6 +7,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.2.163] - 2026-10-30
+
+### Changed
+
+- A Homematic CCU3 / RaspberryMatic is now added as an integration (host, interfaces, optional WebUI login) with a connection test and LAN discovery, and appears as a Gateway device with a link to its WebUI; devices are adopted beside it. Remove and re-add an existing CCU.
+
+## [1.2.162] - 2026-10-29
+
+### Changed
+
+- Homematic value changes now log (debug) when accepted and when dropped, with the reason
+
 ## [1.2.161] - 2026-10-28
 
 ### Changed

package/README.md

@@ -39,3 +39,22 @@ Edit these from System, Addons, this addon, Settings (a device's own settings ar
 See [CHANGELOG.md](./CHANGELOG.md) for what changed in each version.
 
 <!-- readme:generated:end -->
+
+## Setup
+
+1. In CamStack: Integrations, add **Homematic**. Pick the CCU found on your network (the scan asks each host of the
+   local /24 networks whether it is a CCU3 or RaspberryMatic WebUI) or type its **host / IP**. Choose the
+   **interfaces** to bind, and set the **callback host** if the hub has more than one address (it must be one the
+   CCU can reach, never 127.0.0.1; blank infers it). The WebUI **username and password** are optional: they unlock
+   friendly names and rooms, and the password is stored in the CamStack keychain, never in an environment variable,
+   a command line or a log line. **Test** asks every enabled interface and, with credentials, logs in.
+2. Open the integration's discovery. The CCU appears as one **Gateway** device (online state, host, and a link to
+   its WebUI); every CCU device appears as a candidate, or as one candidate per entity under the **Entities**
+   filter. Ids carry the integration, so two CCUs never collide. Products are siblings of the gateway, not its
+   children.
+3. A CCU that is down when CamStack starts is retried with a growing delay, and again on every integration change.
+4. Reboot and firmware update of the CCU are not offered: the library has no call that restarts the CCU, and its
+   firmware call installs an update on a radio device by address.
+
+Two CCUs on one hub share the default callback port (2128): give the second one another **callback port**.
+An older broker-based CCU is not migrated: remove it and add the integration.