Contribute › ADS-B receivers
Connect an ADS-B receiver
If you run an ADS-B receiver, send what it hears to Almighty as well as to every network you already feed. It takes one line of configuration and a few kilobits a second of upload.
New to this, or setting up a new Pi? Become an Almighty Feeder has what to buy, where to put the antenna, and a one-line installer that adds Almighty to what you already run (or sets everything up):
curl -fsSL https://almighty.live/feed/install.sh | sudo bash -s -- YOUR-STATION-KEY
This page is for setting it up by hand.
- Feed
wss://feed.almighty.live/v1/feed/beast(Beast,beast_reduce_plus_out), through the bridge- MLAT
wss://feed.almighty.live/v1/feed/mlat(optional), through the bridge- Your feeder
https://feed.almighty.live/feeder/YOUR-UUID- Network status
- feed.almighty.live/status
1. Register in the Almighty app (Settings → Contribute) and add a station to get its key
There's no sign-up on this website. In the app, open Settings → Contribute, join (sign in, accept the Contributor Terms) and tap Add a station. Choose ADS-B receiver, give it a name and put a pin where it is (only you see it).
For an ADS-B receiver, also enter your feeder's readsb UUID (the one you'll use below; see
Your UUID). The station's page in the app then shows whether we're hearing from your feeder
and links to its dashboard, https://feed.almighty.live/feeder/YOUR-UUID.
ADS-B feeds identify themselves with the UUID, not the station key, so the key isn't needed in the configuration below.
2. Your UUID
A UUID identifies your feeder to us, so you (and the app) can see its stats. It looks like
3f2504e0-4f89-41d3-9a0c-0305e82c3301. Your station already has one: the app
shows it with the station's key (it's worked out from the key, so the one-line installer needs nothing
else). Use that one below.
If you'd rather keep the UUID you already use for other aggregators (ultrafeeder's UUID=
setting, or a feed script's UUID file), enter it on your ADS-B station in the app (its Feeder button)
instead.
Keep it to yourself: anyone with it can see your feeder's page (which never shows where you are).
The bridge: why there's one more piece
Almighty's feed server runs on Cloudflare, which takes secure WebSockets but not the raw TCP connections other networks use (port 30004 and 31090 aren't open). So a small program on your receiver, almighty-feed-bridge (one Python 3 file, no extra packages), takes readsb's and mlat-client's connections on your own machine and carries each to us over a WebSocket. What we receive is exactly what they would have sent. Your UUID has to belong to a station registered in the app, or the bridge is turned away.
On a Pi or Debian/Ubuntu machine, set it up as a service (the file; the one-line installer does this):
sudo curl -fsSL -o /usr/local/bin/almighty-feed-bridge https://almighty.live/feed/almighty-feed-bridge.py
sudo chmod 755 /usr/local/bin/almighty-feed-bridge
almighty-feed-bridge --uuid YOUR-UUID --beast-listen 127.0.0.1:30154 --mlat-listen 127.0.0.1:31154
To start it at boot, a systemd service, /etc/systemd/system/almighty-feed-bridge.service
(then sudo systemctl daemon-reload && sudo systemctl enable --now almighty-feed-bridge):
[Unit]
Description=Almighty feed bridge
Wants=network-online.target
After=network-online.target
[Service]
User=nobody
Environment=ALMIGHTY_FEED_UUID=YOUR-UUID
Environment=ALMIGHTY_BEAST_LISTEN=127.0.0.1:30154
Environment=ALMIGHTY_MLAT_LISTEN=127.0.0.1:31154
ExecStart=/usr/bin/env python3 /usr/local/bin/almighty-feed-bridge
Restart=always
RestartSec=10
NoNewPrivileges=yes
[Install]
WantedBy=multi-user.target
In Docker, run it as a sidecar container instead (below).
3. sdr-enthusiasts ultrafeeder (Docker)
Add the bridge as one more service in your compose file, and point Almighty's entries in
ULTRAFEEDER_CONFIG at it (entries are separated by ;):
ultrafeeder:
environment:
- ULTRAFEEDER_CONFIG=
...your other aggregators...;
adsb,almighty-feed,30004,beast_reduce_plus_out,uuid=YOUR-UUID;
mlat,almighty-feed,31090,uuid=YOUR-UUID
almighty-feed:
build: (the services/aggregator/feed-bridge folder of our repository: the image isn't published yet)
container_name: almighty-feed
restart: unless-stopped
environment:
- ALMIGHTY_FEED_UUID=YOUR-UUID
Then run docker compose up -d. Leave the mlat entry out if you don't want MLAT. Or run the
one-line installer, which runs the bridge on the host instead and adds the entries for you when
ULTRAFEEDER_CONFIG comes from your .env file.
Never send MLAT results back to aggregators (ultrafeeder doesn't, by default). The mlat
entry only sends timing data, and gets our results back for your own map.
a docker-compose.yml open in an editor, with the ultrafeeder service's ULTRAFEEDER_CONFIG list ending in the two almighty-feed lines above, and the almighty-feed service under it.
4. adsb.im feeder image
- Run the one-line installer on the adsb.im device, with your station key: it starts the bridge there and adds
Almighty to adsb.im's list of aggregators, pointing at the bridge.
curl -fsSL https://almighty.live/feed/install.sh | sudo bash -s -- YOUR-STATION-KEY - In adsb.im's web page, Setup › Data sharing: tick Almighty and put your feeder UUID in its UUID box (replacing the one adsb.im made up).
- Press Apply. After a minute or so your feeder shows at
https://feed.almighty.live/feeder/YOUR-UUID.
adsb.im can't send WebSockets itself, so a plain entry in its own list of aggregators (a host and port 30004, as other networks have) can't work for us; the bridge has to run on the device.
5. Plain readsb
Add one connector to readsb's options (on Debian or Raspberry Pi OS: /etc/default/readsb, in
NET_OPTIONS):
--net-connector 127.0.0.1,30154,beast_reduce_plus_out,uuid=YOUR-UUID
That's the bridge on the same machine. Then sudo systemctl restart readsb. readsb
reconnects on its own if the connection drops. If you fed us directly before
(feed.almighty.live,30004), remove that connector.
--net-connector can be given several times, one per aggregator.
6. mlat-client (optional)
MLAT works out where aircraft are when they don't broadcast a position, from the times several receivers heard
them. It needs your receiver's exact position (to the metre, and its height), which we keep private (see below).
--alt is the antenna's height in metres above sea level. With wiedehopf's mlat-client:
mlat-client \
--input-type beast --input-connect 127.0.0.1:30005 \
--server 127.0.0.1:31154 \
--lat 51.47000 --lon -0.45000 --alt 30 \
--user your-name --uuid YOUR-UUID \
--results beast,connect,127.0.0.1:30104
--results sends the MLAT positions back into your own readsb (port 30104, readsb's MLAT input) for
your local map. Add --privacy if you don't want your receiver even roughly shown on any MLAT sync map.
7. Check it's working
https://feed.almighty.live/feeder/YOUR-UUIDshows Connected, messages a second and how many aircraft we're getting from you. It can take a minute after you connect.- In the app, Settings → Contribute: the station turns Online within a couple of minutes, with a link to that page. Still offline? Check the UUID you entered in the app is the one in your configuration.
- The network status page shows whether the feed server is up.
8. What we do with your data
- What we receive: the messages aircraft broadcast that your receiver hears, with timing data; your feeder's UUID; your IP address (that's how the internet works); and, only if you run mlat-client, your receiver's position and height.
- What we do with it: combine it with other feeders' data and with other open sources to show live aircraft in the Almighty app and web app. MLAT positions go back to the feeders that helped work them out.
- What we never do: publish or share your IP address or your receiver's position. Your feeder's page shows only counts. We don't sell the raw feed.
- Aircraft privacy: aircraft whose owners opted out of public tracking (the FAA's LADD list, PIA addresses) are not shown in the Almighty app.
- How long: live data is kept for minutes; aircraft tracks for up to 24 hours (to draw where a plane has flown); your UUID's first and last connection times until you ask us to remove them; your IP address only in server logs, which are overwritten as they fill up.
- Terms: feeding as a registered contributor is covered by the Contributor Terms.
- Stopping: remove the line from your configuration, and delete the station in the app. To have your UUID's records removed, contact us with the UUID.
Thank you for feeding.