Nexa Aviation - Receiver onboarding

Nexa Receiver onboarding

A readsb / dump1090 receiver sends only the current aircraft.json snapshot to Nexa over HTTPS using its own token.

Gateway

Receivers

Active

Agent

0.2

Package

nexa-feeder-agent-0.2.tar.gz - SHA-256

The package contains no tokens or receiver-specific configuration.

Installation

1. Register on the Nexa side

nexa-feeder-register receiver-id "Receiver name" LAT LON 25

The command returns a one-time token; Nexa stores only a one-way token hash. The last parameter controls public location accuracy in km.

2. On the receiver host

tar -xzf nexa-feeder-agent-0.2.tar.gz
cd nexa-feeder-agent-0.2
export NEXA_FEED_TOKEN='TOKEN-FROM-REGISTRATION'
sudo -E ./install.sh PUBLIC_URL/feed/v1/aircraft receiver-id
unset NEXA_FEED_TOKEN

3. Diagnostics

systemctl status nexa-feeder-agent
cat /run/nexa-feeder-agent/status.json

The agent automatically detects common readsb/dump1090 paths. The local token uses mode 0400 and is never logged.

Receivers

The public API exposes only a rounded location according to the privacy-km policy. Exact coordinates remain in the Nexa database.