You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Raise a repair or error when login succeeds but zero installations/chargers are returned #443
After the Zaptec account email address was changed, the integration kept its config entry loaded for about two weeks with 23 of 25 sensors unavailable. No warning at default log level, no reauth, no Repair, no persistent notification. The cause only became visible with DEBUG logging.
What happened
Login (/oauth/token) still returned 200 with the old username, so ConfigEntryAuthFailed was never raised.
/api/installation and /api/chargers then returned 200 with a 36-byte body (an empty list), so the hierarchy contained zero chargers.
first_time_setup produced zero tracked devices and logged "Zaptec setup complete".
The Zaptec app (logged in with the new address) showed the charger and all sessions normally, so the charger and the cloud were fine.
A reload of the entry and a charger firmware update changed nothing.
Reconfiguring the entry to the new address fails with unique_id_mismatch (the entry's unique id is the old username), so the entry had to be deleted and added again.
Debug log (default level shows nothing)
[custom_components.zaptec.zaptec.api] @@@ REQUEST POST to 'https://api.zaptec.com/oauth/token'
[custom_components.zaptec.zaptec.api] @@@ RESPONSE 200 length 1424
[custom_components.zaptec.zaptec.api] TOKEN OK
[custom_components.zaptec.zaptec.api] Discover and build hierarchy
[custom_components.zaptec.zaptec.api] @@@ REQUEST GET to 'https://api.zaptec.com/api/constants'
[custom_components.zaptec.zaptec.api] @@@ RESPONSE 200 length 37969
[custom_components.zaptec.zaptec.api] @@@ REQUEST GET to 'https://api.zaptec.com/api/installation'
[custom_components.zaptec.zaptec.api] @@@ RESPONSE 200 length 36
[custom_components.zaptec.zaptec.api] @@@ REQUEST GET to 'https://api.zaptec.com/api/chargers'
[custom_components.zaptec.zaptec.api] @@@ RESPONSE 200 length 36
[custom_components.zaptec] Zaptec setup complete
Suggestion
After discovery, if the hierarchy contains no chargers, log a warning and raise a Repair (or fail the setup with ConfigEntryError), so the user is told that the account is valid but sees no installation or charger. Optionally also make the config entry's unique_id independent of the username, or allow reconfiguring the username.
I don't think #415 covers this: it only relaxed the validation models, and an empty installation/charger list already passed validation, so setup still completes silently with nothing tracked.
#450 makes setup fail in this case, with an error on the integration card naming the account username (the username is kept out of the log).
The second part (unique_id tied to the username, so reconfiguring to a new email fails) isn't addressed there and would need a separate change.
Activity
steinmn commentedon Oct 17, 2026
Should already be handled by #415, which will be included in 0.8.8
rhammen commentedon Nov 1, 2026
I don't think #415 covers this: it only relaxed the validation models, and an empty installation/charger list already passed validation, so setup still completes silently with nothing tracked.
#450 makes setup fail in this case, with an error on the integration card naming the account username (the username is kept out of the log).
The second part (unique_id tied to the username, so reconfiguring to a new email fails) isn't addressed there and would need a separate change.