@MaxW nice job on the Home Assistant Add-on thanks for the great work. Easy to install and configure 
I sent Flightradar24 an email at [email protected] and asked them for a sharing key which they sent me about 5hrs later
Make sure you include your coordinates in the email and you should be good to go.
Thanks for adding the feature!
going to test it asap. let you know
Is there any way this can be configured to use an ADS-B receiver that isn’t USB using TCPIP? I can connect to my Beast Mode-s ADS-B receiver by accessing port 30334 as it outputs a continuous steam of RAW data - I currently use PlanePlotter to visualise the planes and it is configured as a Beast Mode-s receiver via TCPIP. Thanks
1 Like
Okey… Everything is running smooth and fine here… 
Did manage to got hold of another RTL-SDR dongle and installed Thom-X docker image on it, did put it on the other side of my house improving the coverage.
Is there any way to include that RTL to the add-on?
Here is a nice Lovelace card for monitoring your data. For the data, you will need @ exxamalte’s excellent sensors
Media used to download from the bottom of this page Press | Flightradar24 Blog.
Make sure you download the png file and copy it into the \yourhomeassistantip\config\www folder.
Code for a static pic without any action and aircraft uploaded for the last 24hours graph
type: entities
entities:
- entity: sensor.fr24_feeder_aircraft_tracked
icon: mdi:airplane-marker
- entity: sensor.fr24_feeder_aircraft_uploaded
icon: mdi:airplane-check
- entity: binary_sensor.fr24_feeder_link_connected
- entity: sensor.fr24_feeder_radar_code
icon: mdi:radar
- entity: binary_sensor.fr24_feeder_receiver_connected
- entity: sensor.fr24_feeder_version
header:
type: picture
image: /local/flightradar24_logo_transparent.png
tap_action:
action: none
hold_action:
action: none
footer:
type: graph
entity: sensor.fr24_feeder_aircraft_uploaded
detail: 2
This is with a clickable pic to your local Fr24 page. Remember to change your homeassistantip to your home assistant IP and Fr24 local server.
also enable color icons based on state.
type: entities
entities:
- entity: sensor.fr24_feeder_aircraft_tracked
icon: mdi:airplane-marker
- entity: sensor.fr24_feeder_aircraft_uploaded
icon: mdi:airplane-check
- entity: binary_sensor.fr24_feeder_link_connected
- entity: sensor.fr24_feeder_radar_code
icon: mdi:radar
- entity: binary_sensor.fr24_feeder_receiver_connected
- entity: sensor.fr24_feeder_version
header:
type: picture
image: /local/flightradar24_logo_transparent.png
tap_action:
action: url
url_path: http://yourhomeassistantip:8123xxxxxx_adsb-multi-portal-feeder/dashboard
hold_action:
action: none
footer:
type: graph
entity: sensor.fr24_feeder_aircraft_uploaded
detail: 2
state_color: true
2 Likes
Just installed this and it is working like a charm.
Thanks for the contribution and work put in to all parties concerned.
1 Like
I came across this thing called PlaneFence.
Planefence will create a log of aircraft heard by your Feeder Station that are within a “fence”, that is, less than a certain distance and lower than a certain altitude from your station.
It’s a docker install, went is without issue, working fine thus far.
Nice… Is there any way to get any kind of info from planefence into HA?
direct link to @ exxamalte post with the sensor code as mentioned in OPs message.
Haven’t figured that out yet.
(Not sure if the link is already here somewhere)
I found a nice card that also works great with the add-on: https://github.com/fratsloos/fr24_card
- platform: rest
name: FR24 Aircraft
resource: http://f1c878cb-adsb-multi-portal-feeder:8080/data/aircraft.json
value_template: "{{ value_json.messages }}"
method: GET
scan_interval: 15
json_attributes:
- now
- aircraft
1 Like
Is there a way to get this to work if I already have a different pi running piaware?
2 Likes
I have a Realtek SDR which works OK with RTL_433 and that Add On is disabled. However, when I run the ADS-B Add On, I get the following in the logs, which suggests it can’t see the SDR dongle. I have my FR24 key configured.
What can I check to get this working?
[fr24feed] 2022-11-15 10:50:27 | [time][i]Synchronizing time via NTP
[fr24feed] 2022-11-15 10:50:27 | [time][i]Time synchronized correctly, offset -0.020 seconds
[fr24feed] 2022-11-15 10:50:27 | [main][i]Feed Network client started
[fr24feed] 2022-11-15 10:50:27 | [feed][i]Downloading configuration
[fr24feed] 2022-11-15 10:50:27 | [feed][d]fetching configuration
[fr24feed] 2022-11-15 10:50:27 | [feed][i]configuring decoder
[fr24feed] 2022-11-15 10:50:27 | [feed][c]Max range AIR: 350.0nm
[fr24feed] 2022-11-15 10:50:27 | [feed][c]Max range GND: 100.0nm
[fr24feed] 2022-11-15 10:50:27 | [feed][i]configuration changed
[fr24feed] 2022-11-15 10:50:27 | [feed][i]defined 3 servers
[fr24feed] 2022-11-15 10:50:27 | [feed][c]Timestamps: optional
[fr24feed] 2022-11-15 10:50:27 | [feed][n][email protected]:8099/UDP
[fr24feed] 2022-11-15 10:50:27 | info | Stopping ReceiverACSender threads for feed
[fr24feed] 2022-11-15 10:50:27 | info | Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.24:8099, feed: EGHH162, send_interval: 5s, max age: 15s, send metadata: true, mode: 1, filtering: true
[fr24feed] 2022-11-15 10:50:27 | [feed][n]connecting
[fr24feed] 2022-11-15 10:50:27 | info | [stats]Stats thread started
[fr24feed] 2022-11-15 10:50:27 | info | Network thread connecting to 185.218.24.22:8099 for feed EGHH162
[fr24feed] 2022-11-15 10:50:27 | [feed][n]connected via UDP (fd 29)
[fr24feed] 2022-11-15 10:50:27 | [feed][i]Feed connected
[fr24feed] 2022-11-15 10:50:27 | [feed][n]working
[fr24feed] 2022-11-15 10:50:30 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
[fr24feed] 2022-11-15 10:50:30 | [reader][e]Could not connect to tcp://127.0.0.1:30005
[fr24feed] 2022-11-15 10:50:35 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
[fr24feed] 2022-11-15 10:50:35 | [reader][e]Could not connect to tcp://127.0.0.1:30005
Hi,
I see the ads-b feeder page in sidebar, is very slow to complete the load.
It needs like 10 - 30 seconds to complete, and sometimes fails to load.
Where, host_machine_ip_address:8080, which I setup as dump1090 status site in the addon configuration, is loaded instantly.
What could be the cause?
[update] I have recently deployed nginx proxy and the above issue is gone.
Thank you.
Thanks for making this add on, I used to run flight aware on an old pi and recently upgraded to a pi4 for running home assistant, it will be fantastic to get it running this again, I think my old adsb stick stopped working is there any recommendations for where to purchase a reliable one from in the UK ?
@MaxW Question for this add-on; I’m sure that this option is possible but I have either not written the configuration correctly or something else along those lines.
Using this add-on in Home Assistant OS; Is there a way to have the add-on pull data in one way/shape/form from the FlightFeeder Orange Box?
With this add-on since it creates an ID for uploading data to FlightAware also, is it possible for it to just be a gui for the data obtained by the flightfeeder?
I have no knowledge about the mentioned box, but if it runs the defautl stuff (tar1090, dump1090…) it should be possible.
I have no usb-stick on my box, it is attached to another RPi outside my house. I simply pull the data from it:
When disabling all the feeder options, i would assume it should be possible to just show data and do nothing else.
Hello, first of all thank you for your add on!
I’ve installed it today and run it successfully, I can see multiple aircraft at all time. However, although I filled in the FR24 sharing key, it doesn’t send anything to FlighRadar24. And when I open the feeder setting, I get following state.
The log says following:
System: Home Assistant OS 9.5 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.2.4
Home Assistant Supervisor: 2023.01.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service confd-layers successfully started
s6-rc: info: service confd-html successfully started
s6-rc: info: service http: starting
s6-rc: info: service conf-planefinder successfully started
s6-rc: info: service planefinder: starting
s6-rc: info: service conf-adsbexchange successfully started
s6-rc: info: service adsbexchange-feed: starting
s6-rc: info: service banner successfully started
s6-rc: info: service fr24feed successfully started
s6-rc: info: service piaware successfully started
s6-rc: info: service http successfully started
s6-rc: info: service planefinder successfully started
s6-rc: info: service planefinder-log: starting
s6-rc: info: service adsbexchange-feed successfully started
s6-rc: info: service adsbexchange-stats: starting
s6-rc: info: service adsbexchange-mlat: starting
s6-rc: info: service adsbexchange-stats successfully started
s6-rc: info: service adsbexchange-mlat successfully started
s6-rc: info: service planefinder-log successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[fr24feed] 2023-02-15 00:10:57 | [e]PacketSenderConfiguration::fetch_config(): Unable to fetch configuration for yoda receiver
[fr24feed] 2023-02-15 00:10:57 | [d]TLSConnection::ctor(): Enable verify_peer in production code!
[fr24feed] 2023-02-15 00:10:57 | [master][i]Starting processing thread
[fr24feed] 2023-02-15 00:10:57 | [reader][i]Initializing reader
[fr24feed] 2023-02-15 00:10:57 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
[fr24feed] 2023-02-15 00:10:57 | [main][i]Reader thread started
[fr24feed] 2023-02-15 00:10:57 | [reader][i]Connected to the receiver, configuring
[fr24feed] 2023-02-15 00:10:57 | [reader][i]Configured, processing messages
[fr24feed] 2023-02-15 00:10:57 | [reader][i]Timestamp source changed from UNKNOWN to SYSTEM-UNCERTAIN
[fr24feed] 2023-02-15 00:13:27 | [time][i]Synchronizing time via NTP
[fr24feed] 2023-02-15 00:15:57 | [time][e]Failed to synchronize time
[fr24feed] 2023-02-15 00:15:57 | [main][w]Failed to synchronize time, waiting 6 seconds
[fr24feed] 2023-02-15 00:18:33 | [time][i]Synchronizing time via NTP
[fr24feed] 2023-02-15 00:21:03 | [time][e]Failed to synchronize time
[fr24feed] 2023-02-15 00:21:03 | [main][w]Failed to synchronize time, waiting 8 seconds
[fr24feed] 2023-02-15 00:23:41 | [time][i]Synchronizing time via NTP
[fr24feed] 2023-02-15 00:26:11 | [time][e]Failed to synchronize time
[fr24feed] 2023-02-15 00:26:11 | [main][w]Failed to synchronize time, waiting 10 seconds
[fr24feed] 2023-02-15 00:28:52 | [time][i]Synchronizing time via NTP
[fr24feed] 2023-02-15 00:31:22 | [time][e]Failed to synchronize time
[fr24feed] 2023-02-15 00:31:22 | [main][w]Failed to synchronize time, waiting 12 seconds
[fr24feed] 2023-02-15 00:34:04 | [time][i]Synchronizing time via NTP
Does anyone encountered similar issue?
Thanks a lot in advance
Might share your configuration - XXX out all keys etc - please?
That ntp time thing looks sus, you have any internet filters? Firewall blocking outgoing ports etc?
Configuration for your Add-on? It’s pretty simple really, as I did the setup yesterday on freshly new flashed Home Assistant OS, I have following:
SERVICE_ENABLE_DUMP1090: true
SERVICE_ENABLE_PIAWARE: false
SERVICE_ENABLE_FR24FEED: true
SERVICE_ENABLE_HTTP: true
PIAWARE_FEEDER_DASH_ID: ""
FR24FEED_FR24KEY: "xxxxxxxxxxxxxxxx"
ADSBEXCHANGE_UUID: ""
PLANEFINDER_SHARECODE: ""
HTML_SITE_LAT: HOMEASSISTANT_LATITUDE
HTML_SITE_LON: HOMEASSISTANT_LONGITUDE
HTML_DEFAULT_TRACKER: Flightradar24
And that’s all. The rest is unused. I don’t have any particular internet filters, I have standard router from provider, and didn’t fiddle with the setting at all. One thing to add is that my RPi is connected to network just via WiFi as I didn’t want to deal with the cables just to try it.