Compatibility
Define compatibility by electrical, firmware, protocol, and capability behavior—not by appearance.
ESPFlight Docs · v1•Validated v1 documentation path
#What compatibility depends on
ESP microcontroller/module behavior supported by the firmware.
Sensor support and orientation.
Electrical connections and power architecture.
Motor outputs and pin assignments.
Firmware configuration or required code changes.
Application / Firmware protocol compatibility.
Capabilities actually supported by the hardware + firmware combination.
#Custom hardware
A compatible board does not need to look identical to the Hardware Reference. If you change pins, sensors, power design, or other hardware-facing behavior, document the variant and update firmware configuration/code where required.
IDENTITY DIRECTION
As the ecosystem grows, explicit maker, product, revision, firmware, protocol, and capability metadata can reduce guesswork. Treat such metadata as a formal requirement only when it is specified and versioned.