If your stack already speaks MQTT, a receiver drops into it without a custom integration. The unit publishes every detection to your broker over LAN — no cloud relay, no vendor account. You point it at a broker host, port, username and topic prefix in the local web UI.

Topics

• <base>/status — retained heartbeat every 30 s (firmware, RSSI of uplink, free memory)
• <base>/detection/rid — decoded Remote ID reception
• <base>/detection/rf — RF-spectrum event, non-decoded
• <base>/notice — device events: reboot, antenna fault, temperature warning

QoS 1, clean session off — a disconnected controller catches up on what it missed. Payloads are UTF-8 JSON, one message per detection, same field names as the REST payload so your parser is written once.

Home Assistant example

mqtt:
  sensor:
    - name: "Ridfinder last detection"
      state_topic: "site1/gate2/detection/rid"
      value_template: "{{ value_json.detail.serial }}"
      json_attributes_topic: "site1/gate2/detection/rid"

That is enough for an automation like “notify when a drone broadcasts Remote ID at the north fence”. The draft spec includes a second example feeding Node-RED, and a table of every JSON field with units. Ask for the draft and we send it.

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