Feeding ADSBHub
If you wish to feed ADSBHub, follow the steps below.
Last updated
Was this helpful?
If you wish to feed ADSBHub, follow the steps below.
Last updated
Was this helpful?
The main goal of is to become a ADS-B data sharing centre and valuable data source for all enthusiasts and professionals interested in development of ADS-B related software.
The docker image contains the required feeder software and all required prerequisites and libraries. This needs to run in conjunction with ultrafeeder
(or another Beast provider).
First-time users should obtain a ADSBHub Station dynamic IP key. Follow the directions for steps 1 and 2 at , ensuring your station is set up as a client and the data protocol set as "SBS" (see below.)
Existing users should sign in to their ADSBHub account, go to their "Settings" page, click on their station (in the bar at the top of the settings table) and retrieve their station key.
In your station preferences, you should set the following:
Feeder type: Linux
Data Protocol: SBS
Station mode: Client
.env
file with ADSBHub Station KeyInside your application directory (/opt/adsb
), edit the .env
file using your favourite text editor. Beginners may find the editor nano
easy to use:
This file holds all of the commonly used variables (such as our latitude, longitude and altitude). We're going to add our ADSBHub Station Key to this file. Add the following line to the file:
Replace YOURSTATIONKEY
with the station key you retrieved earlier.
The single quotes ('
) are important, as the station key from ADSBHub contains special characters that would confuse docker compose
if the single quotes were missing.
For example:
Open the docker-compose.yml
file that was created when deploying ultrafeeder
.
Append the following lines to the end of the file (inside the services:
section):
To explain what's going on in this addition:
We're creating a container called adsbhub
, from the image ghcr.io/sdr-enthusiasts/docker-adsbhub/adsbhub:latest
.
We're passing several environment variables to the container:
SBSHOST=ultrafeeder
to inform the feeder to get its ADSB data from the container ultrafeeder
TZ
will use the FEEDER_TZ
variable from your .env
file.
CLIENTKEY
will use the ADSBHUB_STATION_KEY
variable from your .env
file.
Once the file has been updated, issue the command docker compose up -d
in the application directory to apply the changes and bring up the adsbhub
container. You should see the following output:
We can view the logs for the environment with the command docker logs adsbhub
, or continually "tail" them with docker logs -f adsbhub
. The logs will be fairly unexciting and look like this:
Once running, you can visit to view the data you are feeding to ADSBHub.
If you want to look at more options and examples for the adsbhub
container, you can find the repository