What's Changed
Integration
- HmIP-WGT and HmIP-WGTC show their heating schedule. They also have a switch schedule, and the
climate entity and the climate schedule services only knew that one. The climate entity and its
services now use the heating schedule.get_scheduleandset_schedulestay on the switch schedule
of these devices. The new heating schedule sensor is called "Climate week profile". The config panel
still shows the switch schedule only.
Dependencies
Bump aiohomematic to 2026.11.3
- Support for new devices: thermostats HmIP-WT, KW-STATH, KW-UKETRV, HmIPW-WGT and HmIPW-WGTC, dimmers
HmIP-WUA, ELV-SH-WUA and HmIP-UDI-PB2 - Fix: HmIP-DLD and HmIP-DLP report a jammed lock, HmIP-DLP exposes
ERROR_JAMMED - Fix: HmIP-WSM keeps its run time on current firmware, HmIP-BDT-I dimmer uses the correct channels
- Fix: the switch schedule of HmIP-WGT and HmIP-WGTC has the correct targets and accepts entries
- Fix: HmIPW-WTH and HmIPW-SCTHD use the limits configured on the device
Bump aiohomematic-config to 2026.11.1
- Fix: the climate schedule commands of the config panel (
get_climate_schedule,set_climate_schedule_weekday,set_climate_active_profile) reach the heating schedule of HmIP-WGT and HmIP-WGTC, which also have a switch schedule
Bump openccu-loom-client to 2026.11.3
- For the openccu-loom backend (Beta) only; no runtime effect on the direct-CCU backend, where the client is not loaded. Fixes
switch_set_on_time,light_set_on_timeandvalve_set_on_time, which had no effect on that backend, climate entities that were not created there with this release, and device actions, device triggers and the per-device central-link services, which failed there; HmIP-WGT and HmIP-WGTC get their heating schedule with openccu-loom 0.97.1 or newer