SukramJ/homematicip_local 2.2.2b1 on GitHub

What's Changed

Fix Interface Port Resolution: Interface ports are now correctly resolved using aiohomematic's default port mapping when no port is explicitly configured. Previously, unconfigured ports were passed as None, which could cause connection issues. The fix uses the configured port if available, falls back to the interface's default port, or uses port 0 for JSON-RPC-only interfaces (CUxD, CCU-Jack).

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 INITIALIZED state (initialized but never connected) can now recover. The state machine now permits INITIALIZED → DISCONNECTED transitions, enabling proper state reset for reconnection attempts.
Fix JSON-RPC Port Handling: TCP pre-flight checks now skip port 0 (used by JSON-RPC-only interfaces). CUxD and CCU-Jack rely on JSON-RPC via central ports (443/80) rather than individual XML-RPC ports. Additionally, a new JSON-RPC port pre-flight check verifies service availability before client creation.