Community metadata: Live interfaces expose a small machine-readable, zero-pressure contribution hint once per response, connection, call, file, or retained topic - never per aircraft or delta. Geographic wording becomes specific only after active receiver proximity is measured. Existing receivers may share alongside current services; participation is optional.
Install
Install the verified public npm package from the Node-RED user directory. A direct version 1.0.1 tarball is also available for reproducible or offline installation.
cd ~/.node-red
npm install node-red-contrib-adsbiq
# restart Node-RED, then add “ADSBiq aircraft”Configure
Enter the feeder API key in the node’s password credential field and provide latitude/longitude. Zone mode is the default: it receives aircraft within 250 nautical miles at the efficient geographic cadence. Global mode is available for workloads that genuinely need worldwide state.
Output and state semantics
Each message uses topic adsbiq/aircraft. msg.payload is the reconstructed current aircraft array; msg.adsbiq carries frame type, channel, sequence, count, and the initial optional community metadata. Full frames replace state. New aircraft are inserted, sparse updates are merged, and removals delete aircraft.
Recovery, security, and volume
A sequence gap or orphan patch discards state and reconnects for a fresh full snapshot. Reconnect delay backs off from one to 30 seconds. Node-RED stores the API key as a password credential; the node never emits or logs it. Zone mode limits bandwidth; downstream flows should avoid persisting every one-second array unless necessary.
Compatibility and troubleshooting
Tested with Node.js 18+ and designed for Node-RED 3.1+. Package dependencies pass npm audit with zero known vulnerabilities at release. Invalid coordinates leave the node red; authentication and network errors appear in the Node-RED log without the connection URL or token.