Kept in this browser only. It is never put in the URL.
Device—
Status—
Lock—
Speed mode—
Battery—
Signal—
Last frame—
button → reply
—
scooter's own reply time
—
path
—
KEY
—
The device restores default settings on power-off and on unlock
(spec 1.3.8), so a mode chosen before unlocking is discarded. Set the
mode after the scooter is open.
These three go straight out on the open socket and the scooter answers
within a few hundred milliseconds. They are not queued: queuing waits
for the device's next frame, which costs ten to twenty seconds for
nothing on this fleet.
Unlock and Lock ask for the single-use KEY (R0) on pointerdown,
a tenth of a second or so before the click lands, so the command that
follows spends a KEY it already has. A press the prepare did not reach
in time sends its own R0 and costs what it always did. The KEY reading
above says which of the two a given press got.
These two are queued: they go out on the device's next
frame, so expect a wait. The external-lock path has no direct endpoint.
Idle.
Wire log
RX is the scooter talking, TX
is this server. Both come from the same hash-chained capture the gateway
writes to disk, so what you see here is the evidence file, not a
separate rendering of it.