Telemetry Protocol
Treat telemetry as controller-reported state and keep application behavior synchronized with it.
ESPFlight Docs · v1•Validated v1 documentation path
#Telemetry principles
Application ARM state should follow telemetry/acknowledged firmware state.
Telemetry should make connection and flight-state transitions observable.
Flight-time telemetry in v1.0.0 represents accumulated powered-flight time, not total ARMED duration.
A changed field or semantic should be versioned/documented with protocol compatibility in mind.
#Do not infer safety state
Client UI state should not silently replace controller state. For safety-critical transitions such as ARM/DISARM and assisted-flight commands, use the firmware-confirmed state and command acknowledgements.