๐งช Testers Wanted!
Help us validate experimental features before general release. Enable optional settings and share your feedback.
๐ Optional Settings Documentation
โ 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
New Features
- Simple Schedule Services: Added
get_schedule_simple_profileandget_schedule_simple_weekdayservices. These return schedule data in a simplified format that is easier to read and use.
Deprecations
- Schedule Services: Deprecated
set_schedule_profile,set_schedule_weekday,get_schedule_profile, andget_schedule_weekdayservices. These will be removed in April 2026. Useset_schedule_simple_profile,set_schedule_simple_weekday,get_schedule_simple_profile, andget_schedule_simple_weekdayinstead. A warning is now logged when using the deprecated services.
Bump aiohomematic to 2026.1.13
Bug Fixes
- CUxD/CCU-Jack Recovery Fix: Fixed recovery mechanism for JSON-RPC-only interfaces (CUxD, CCU-Jack). Recovery now checks the JSON-RPC port (80/443) instead of failing at the TCP check stage. This prevents the central unit from entering a FAILED state when these services are actually available
- Device Availability Not Updating: Fixed devices not showing as unavailable when UN_REACH changes. All entity states are now refreshed when device availability changes
- HmIP-MP3P LED Auto-Off: Fixed LED turning off after 10 seconds on HmIP-MP3P sound player devices
- VirtualDevices Init Timeout: Fixed initialization timeout causing client failure for virtual devices
- Device Cache After Firmware Updates: Fixed device structure changes after firmware updates. Cached descriptions are now removed and refreshed from the CCU, preventing errors like "Non-existent Channel 3"
- Device Replacement/Re-pairing: Fixed device replacement and re-pairing handlers. Old device entries are now properly removed and recreated with fresh data
- Hub Entities with Secondary Client Failures: Fixed system variables and programs not appearing when secondary clients (e.g., CUxD) fail to initialize
- Connection Recovery Port Detection: Fixed port detection during connection recovery for all client implementations
- Channel Names Not Loading: Fixed channel names not loading when using InterfaceClient (JSON-RPC). The nested channels array from the JSON-RPC response is now processed correctly