Use it
Glossary·
The eight words this site uses precisely: frame, cmd, notify, memo, gateway, queue, endpoint, evidence.
In 10 seconds
A frame is one BLE write or notify; its second byte is the cmd. A memo is Opus audio the ring stored
after four taps. A gateway is whatever holds the BLE link (phone or ring-cli bridge) and posts to tiny.
The queue carries agent commands back to the gateway; the ring shows up in your fleet as an endpoint.
- frame
- one packet on the wire: 10-byte header
FE FC · cmd · total · index · len, then payload. Long replies span several frames,indexcounting up. → Framing - cmd
- the one-byte command id, identical in request and reply (
07opens heart rate,0Bcarries the ticks). Hex here, decimal in the raw JSON. → Commands - write / notify
- direction: the host writes to
33F3, the ring notifies on33F4. Nothing uses a GATT read. → Protocol - memo
- a voice note the ring stores in flash after four taps:
u32 counter · u16 0 · 12 × 40 B Opusper packet, 16 kHz mono. Pull40/34, delete36. → Audio · Voice memos - live stream
- the same Opus packets streamed while you talk (
30mode 1/2,32/33). Refused on the charger. → Audio - cradle
- the charger. A ring on it still reports HR ~80–103 and 31 °C; tiny drops them (
cradle_excluded). → Health platform - gateway
- whatever holds the ring's one BLE link and speaks HTTPS to tiny: the tiny iOS/Android app, or
ring-cli bridge. → Phone gateway · Bridge - queue
ring_commandson the worker: the agent enqueuesfind · battery · measure_hr · …, the gateway claims and runs them over BLE, results return as events. → Agent tools- endpoint
- the ring as a fleet device with capabilities, reachable with
use_device invoke— a projection of the queue; the ring never talks HTTP. → Ring as endpoint - evidence
evidence/*.jsonlandcaptures/*: request bytes, reply bytes, timestamp per proven behaviour. A row is ✅ only with a line here. → Full ledger- APK-only
- a command LoraFit can build that no capture or live run has exercised — documented, not proven. → Commands