Controller Ownership
Prevent ambiguous control when multiple clients are present on the same local network.
ESPFlight Docs · v1 • Validated v1 documentation path
# Single active control intent
The v1 documentation and application flow are designed around one active controller for a Drone session. A second client should not be able to silently compete for flight commands while the first client believes it owns control.
# Implementation expectations
Make acquisition and release of the active control session explicit.
Tie state-changing commands to the active session/context.
On loss of the active link, enter the documented failsafe path rather than accepting ambiguous control.
Do not infer that a connected socket is automatically authorized to command flight state.
NETWORK LIMIT
Protocol 2 on v1 is still intended for a trusted private local network. Session ownership is not a replacement for encrypted hostile-network authentication.