Which firewall ports does a node need?

Outbound HTTPS (443) for updates and push, plus outbound MQTT (1883 or 8883) if you use a broker. Nothing needs to be reachable inbound — management is via the local web UI on the LAN, or through a reverse proxy you control.

What happens when the network drops?

Detection continues. The node buffers events locally and republishes them when the link returns — MQTT with clean session off replays retained state, REST clients catch up through the since parameter. Uptime and buffer depth are visible in GET /api/v1/status.

Do multiple nodes pair with each other?

They correlate. Each node timestamps independently; the correlation service (or your own consumer) matches detections of the same emitter across nodes to estimate bearing and rough position. We document the correlation fields in the API draft rather than hiding them in a closed console.

How long is detection data kept?

On the node: configurable ring buffer, days not weeks. In your systems: your call — the device is the source, retention policy belongs to you. Operator identity fields, where present in decodes, are treated as personal data under GDPR and worth handling deliberately; we say the same thing on the privacy page.

Power over Ethernet?

Yes — 802.3af. A node draws under 8 W including the radio, which is why one cable is normally the whole install.

Question not answered here? Send it — technical questions get an engineer’s answer, and the good ones end up on this page.

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