Conversation
, custom-components#420) Zaptec has no "is authorized" observation: ChargerCurrentUserUuid (722) holds the token of whoever authorized the current session, and is empty when nothing is authorized. - "Authorized by" and "Last session authorized by" sensors show the RFID token, or "HA/Zaptec App" for a remote authorize, which this integration cannot distinguish from one made in the Zaptec app. - An "Authorized" binary sensor, deliberately not diagnostic: with delayed charging the charger stays in Connected_Requesting after authorizing, so this is the only way to tell "authorized, waiting for the car" from "waiting for authorization" (custom-components#420). The prefix rule lives in authorization.py so both platforms derive their value from it and cannot disagree. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Sep 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Zaptec has no "is authorized" observation:
ChargerCurrentUserUuid(722) holdsthe token of whoever authorized the current session, and is empty when nothing
is authorized.
remote authorize, which this integration cannot distinguish from one made in
the Zaptec app.
CompletedSession.AuthenticationCode. Zaptec leaves that empty forremote-authorized sessions, which therefore read Unknown.
charging the charger stays in
Connected_Requestingafter authorizing, sothis is the only way to tell "authorized, waiting for the car" from "waiting
for authorization" (Time delyaed charging and release status #420).
Where the installation does not require authorization the binary sensor reports
Unknown rather than "Not authorized", which would otherwise look like a fault
while the car charges normally.
The prefix rule lives in
authorization.py, so both platforms derive theirvalue from it and cannot disagree.
Depends on #425: Zaptec clears 722 by sending it without a value, and without
that fix the token never clears.
Verified on a Go 2 (fw 3.3.0.0): 722 is not pushed over the live stream — 710
and 721 are — so it follows the poll interval. Authorizing from HA's own button
is picked up within a couple of seconds, since the button triggers a poll.
Fixes #200, #420
🤖 Generated with Claude Code