☕ Support This Project
If you find this integration useful, consider supporting its development:
Your support helps maintain and improve this integration. Thank you! 🙏
What's Changed
Bug Fixes
- Fix Interface Port Resolution: Interface ports are now correctly resolved using aiohomematic's default port mapping when no port is explicitly configured. JSON-RPC-only interfaces (CUxD, CCU-Jack) now correctly pass
Noneinstead of a port number, as they don't use XML-RPC ports.
Bump aiohomematic to 2026.1.50
Changed
- Port Handling Refactoring for JSON-RPC Interfaces:
InterfaceConfig.portchanged frominttoint | Nonefor cleaner semantics. JSON-RPC-only interfaces (CUxD, CCU-Jack) now properly useNoneinstead of the workaround value0. This provides improved type safety and eliminates validation workarounds throughout the codebase.
Bug Fixes
- Fix Hub Data Not Refreshing After Reconnection: Hub data (System Update, Programs, Sysvars) is now refreshed after successful reconnection. Previously, stale information persisted—for example, "Update available" would display even after the CCU completed firmware updates during disconnection.
- Fix Client Recovery for Secondary Interfaces: Recovery for CUxD and CCU-Jack clients now succeeds when other clients already exist. The issue stemmed from attempting to create all clients simultaneously; the fix creates the specific failing interface client directly instead of recreating all clients.
- Fix Clients Stuck in INITIALIZED State: Clients stuck in
INITIALIZEDstate (initialized but never connected) can now recover. The state machine now permitsINITIALIZED → DISCONNECTEDtransitions, enabling proper state reset for reconnection attempts. - Fix JSON-RPC Port Handling: TCP pre-flight checks now correctly skip interfaces with
Noneport. CUxD and CCU-Jack rely on JSON-RPC via central ports (443/80) rather than individual XML-RPC ports. A new JSON-RPC port pre-flight check verifies service availability before client creation.