Detection hardware earns trust by not changing underneath you. Firmware updates ship on two channels: stable (default; security fixes and decoder updates, no interface changes) and beta (opt-in; new decoders and features land here first). Updates are signed; the unit refuses unsigned images and rolls back automatically if a signed image fails to start twice.

What an update may change

• Protocol decoders — as new aircraft and broadcast formats appear, these are the most frequent updates
• RF-spectrum signature data, where the model uses a signature library
• Security fixes — published with a CVE reference when one exists

What updates will never change without a version-major bump and a written notice: the REST payload schema, the MQTT topic layout, and your stored configuration.

Release log

Firmware 1.0 is in pre-release; the public changelog opens here when it ships. Integrators registered for the draft programme get breaking-change notices by email before each release — ask to be registered, it costs nothing.

Content last reviewed: 2026-09-11. Interface draft v0.9 — locked against firmware 1.0. Questions: contact engineering.