11 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
thatguygriff	dd1cc76580	Treat 404 as auth error and persist refreshed tokens ... The DKN Cloud NA API returns 404 (not 401) when tokens are expired, which caused the integration to silently fail with UpdateFailed indefinitely instead of attempting a token refresh or triggering reauth. Refreshed tokens were also only held in memory, so they were lost on Home Assistant restart. - Add 404 to auth_error_statuses on is_logged_in, refresh_access_token, and fetch_installations. - Persist refreshed access + refresh tokens back to the config entry after each successful coordinator update. - Skip the entry reload listener for token-only option updates to avoid a reload loop on every refresh. - Log API 4xx responses at WARNING with the body so failures are visible in HA logs without enabling debug logging.	2026-05-26 09:58:57 -03:00
Sebastien Lavoie	aa81851243	resimplify	2026-03-30 20:49:57 -04:00
Sebastien Lavoie	04e1d488f9	Dynamic fan speeds	2026-03-30 20:35:13 -04:00
Sebastien Lavoie	0dab86d205	Send + ack	2026-03-30 10:07:01 -04:00
Sebastien Lavoie	7f8bc63c62	Smoke test	2026-03-30 08:07:20 -04:00
Sebastien Lavoie	f7aa9ac00f	Fix socket connection	2026-03-29 10:06:16 -04:00
Sebastien Lavoie	f805015b74	Implement write actions	2026-03-29 09:52:40 -04:00
Sebastien Lavoie	1e1df6a2e7	Implement socket connection	2026-03-29 09:40:54 -04:00
Sebastien Lavoie	8a4d040bac	fix: implement DKN Cloud NA authentication	2026-03-29 09:22:43 -04:00
Sebastien Lavoie	0beaa71fdc	feat: add DknCloudNaClient stub	2026-03-29 08:44:43 -04:00