4 Commits

Include renames

Author	SHA1	Message	Date
Kydoimosandanthropic/claude-opus-5	3929546ea5	fix(climate): write mode-correct setpoints and stop REST reverting live state ... Two independent bugs made a second change (e.g. adjusting the target temperature right after switching cool -> heat) fail to take, and made Home Assistant settle back on a previous state while DKN Cloud NA showed the correct one. Wrong setpoint key on write: _writable_temperature_property_for_mode() ignored its hvac_mode argument and resolved the key from real_mode/mode in the cached device payload. That payload still describes the pre-change state, so a heat setpoint was emitted as setpoint_air_cool: the unit switched to heat but the heat setpoint never moved. The same defect broke AUTO in steady state, where real_mode=cool made the write target setpoint_air_cool while the read used setpoint_air_auto, so the value could never appear to change. target_temperature() and writable_target_temperature_key() now accept the mode the caller intends, and that mode takes priority over anything in the device payload. Device-reported modes remain a fallback only for payloads that do not expose the requested mode's setpoint. async_set_temperature() no longer re-sends power+mode; async_set_hvac_mode() already sent them, and the stale-cache condition guarding the resend was always true. It now waits (bounded) for the cloud to echo the mode before sending the setpoint, matching the ensure_mode ordering the smoke test uses. REST snapshot reverting live state: The coordinator merged {**existing, **device}, letting the lagging REST /installations snapshot win over live Socket.IO pushes. Once the socket confirmed a write, _reconcile_optimistic dropped the overlay, leaving nothing to stop the next poll from reverting the state. Socket-pushed values are now tracked per device and applied after the REST payload. They are discarded when the socket session changes, since updates may have been missed while it was down and REST becomes authoritative again. Also report hvac_action and target_temperature against the effective (optimistic-aware) mode so the action cannot contradict the reported mode while a change propagates. Co-authored-by: anthropic/claude-opus-5	2026-09-19 09:48:10 -03:00
thatguygriffandClaude Opus 4.7	494c6df2c3	fix(climate): keep optimistic state until DKN cloud catches up ... The DKN cloud REST endpoint lags behind the unit for several seconds after a write, even though the unit itself and the DKN app reflect the change immediately. The previous 2.5s optimistic-overlay TTL expired well before the cloud caught up, so the next coordinator publish (REST poll or socket device-data push) carried stale values and the HA UI reverted to the previous setting. Extend the overlay TTL to 30s as a safety bound, and track the underlying device key + expected device value alongside each overlay. On every coordinator publish, clear overlays whose device key now reports the expected value (cloud has confirmed). The TTL still caps how long a silently-failed write can hold a wrong value. Co-Authored-By: Claude Opus 4.7 <[email protected]>	2026-05-27 09:49:04 -03:00
Sebastien Lavoie	1e1df6a2e7	Implement socket connection	2026-03-29 09:40:54 -04:00
Sebastien Lavoie	17e44e4546	feat: add manifest.json and constants	2026-03-29 08:43:05 -04:00