9 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
thatguygriff	2770eda23b	Merge pull request 'fix(climate): keep optimistic state until DKN cloud catches up' (#4) from fix/climate-state-revert into main ... Reviewed-on: #4	2026-05-27 12:53:08 +00: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
thatguygriff	d8bcd9195c	Merge pull request 'Skip validate workflow on ARM64 runners' (#3) from ci/skip-on-arm into main ... Reviewed-on: #3	2026-05-26 14:06:48 +00:00
thatguygriff	86d3a45877	ci: gate validate jobs on github.server_url instead of runner.arch ... The runner.arch context isn't populated for job-level if conditions on Gitea Actions, so the previous guard didn't skip on ARM64 Gitea runners. Switch to checking github.server_url, which is reliably 'https://github.com' on GitHub-hosted runs and the Gitea host everywhere else.	2026-05-26 11:06:23 -03:00
thatguygriff	5618ecf3fc	ci: skip validate workflow on ARM64 runners ... The hassfest and HACS validator actions both depend on amd64-only Docker images (ghcr.io/home-assistant/hassfest, hacs/action). On ARM64 runners — like the Gitea Actions instance hosting this fork — those images pull but fail with "exec format error" because no multi-arch image is published. Validation still runs on GitHub's amd64 ubuntu-latest runners, where it actually matters for HACS distribution.	2026-05-26 11:03:00 -03:00
thatguygriff	2248b7197a	Merge pull request 'Update README to reflect implemented functionality' (#2) from docs/update-readme into main ... Reviewed-on: #2	2026-05-26 13:42:02 +00:00
thatguygriff	a7ceca779b	Update README to reflect implemented functionality ... The "Known Limitations & Roadmap" section claimed device control was not implemented and that Socket.IO was unused. Both are now inaccurate — climate control (mode, temperature, fan speed, swing) ships via Socket.IO machine events, and live device-data updates come over the same socket connection. Replace that section with a "How It Works" overview and a smaller "Known Limitations" list reflecting the actual remaining gaps.	2026-05-26 10:10:53 -03:00
thatguygriff	bff10aadb5	Merge pull request 'Treat 404 as auth error and persist refreshed tokens' (#1) from fix/token-refresh-404 into main ... Reviewed-on: #1	2026-05-26 13:08:18 +00: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