The enrolment the Anker app does, done here: 0108 a2=7 opens the reader,
0908 brings back the UID. The frames this sends are byte-for-byte the
ones the app was captured sending — checksum included — which is what the
new test asserts.
Adding and removing now write the charger as well as the account: the
device write is the app's own message, the account write is the inferred
one that carries the name, and either may fail without the other.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Caught on the charger's own command topic while a card was removed and
added back in the Anker app. Enrolling at the charger is three MQTT
messages and no REST call: open the reader, take the UID the tap
publishes, write it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Named from a live capture on an A5191: 0904 carried the nine UIDs the
account's own card list answers with, and 0908 arrived the moment a card
touched the reader, carrying its UID — and arrived without one when the
window closed empty. 0911 names the OCPP backend the charger is pointed
at. A UID is bytes, not a number, so type 0x04 now reads as hex.
With the frame log on, the command topic is subscribed too: the app's own
commands are the half no capture has seen.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
