GitHub/homeassistant-dkncloudna
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity
29 Commits 1 Branch 1 Tag
bff10aadb50029130cabcf314b42bcc3d00b4bcc
Commit Graph
2 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
thatguygriff bff10aadb5 Merge pull request 'Treat 404 as auth error and persist refreshed tokens' (#1) from fix/token-refresh-404 into main
Validate / Hassfest validation (push) Failing after 1s
Details
Validate / HACS validation (push) Failing after 0s
Details 
Reviewed-on: #1
 2026-05-26 13:08:18 +00:00
thatguygriff dd1cc76580 Treat 404 as auth error and persist refreshed tokens
Validate / Hassfest validation (pull_request) Failing after 20s
Details
Validate / HACS validation (pull_request) Failing after 0s
Details 
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