Installed piaware on my Raspi, but Flyaware dont receive my ADS-B data

FlightAware ADS-B Flight Tracking
1

Hi. im Oliver an absolute new to Flightaware. But one of my Raspis share ADS-B data to Flightradar24 since years absolute stable.

Now i want to share my ADS-B data also to Flightaware and installed piaware on my raspi running the fr24feed service and the dump1090-mutability service.

At first everything seemed running perfectly. The raspi connected also to Fligtaware. I got a message from flightaware that my raspi is connected. An in my flightaware dahboard i can see the logs and some more information like my internal and externel ip and something more.

But Flightaware doesnt receive my ADS-B data. No airplane data appears in the statistics.
On FR24, everything work find. They receive all the necessary data.

When i open http://my.local.IP/dump1090/gmap.html i also can see the map with the receives aircrafts.
All services on my raspi are running, no errors. And the Raspi is not behind a firewall or filter (at the moment :slight_smile: )
But when i click the “show live-data” in my flightaware dashboard, chrome opens a new tab with http://my.local.IP:8080/ but there i get the message that the wensite is not reachable.

Has anybody a hint for me what im doing wrong? Or can tell me what to do that flyaaware also gets my ads-b data

Thanks in advance and greetings from sunny bavaria,

Oli.

And here is a snipped of my log. Maybe it helps resolving the problem.

[2026-08-09 13:55 CEST] no ADS-B data program seen listening on port 30005 for 3 seconds, next check in 60s
[2026-08-09 13:55 CEST] site statistics URL: xxxxxxxxxxxxxxxx
[2026-08-09 13:55 CEST] my feeder ID is xxxxxxxxxxxxxxxx
[2026-08-09 13:55 CEST] multilateration data requested
[2026-08-09 13:55 CEST] UAT support disabled by local configuration setting: uat-receiver-type
[2026-08-09 13:55 CEST] adept reported location: 48.40600, 12.82290, 1427ft AMSL
[2026-08-09 13:55 CEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2026-08-09 13:55 CEST] logged in to FlightAware as user xxxxxxxxxxx
[2026-08-09 13:56 CEST] 0 msgs recv’d from dump1090; 0 msgs sent to FlightAware
[2026-08-09 13:56 CEST] no ADS-B data program seen listening on port 30005 for 63 seconds, next check in 60s
[2026-08-09 13:56 CEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2026-08-09 13:56 CEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2026-08-09 13:56 CEST] logged in to FlightAware as user xxxxxxxxxxx
[2026-08-09 13:56 CEST] my feeder ID is xxxxxxxxxxx
[2026-08-09 13:57 CEST] no ADS-B data program seen listening on port 30005 for 123 seconds, next check in 60s
[2026-08-09 13:57 CEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2026-08-09 13:58 CEST] no ADS-B data program seen listening on port 30005 for 184 seconds, next check in 60s
[2026-08-09 13:58 CEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2026-08-09 13:59 CEST] no ADS-B data program seen listening on port 30005 for 244 seconds, next check in 60s
[2026-08-09 13:59 CEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2026-08-09 14:00 CEST] no ADS-B data program seen listening on port 30005 for 304 seconds, next check in 60s
[2026-08-09 14:00 CEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2026-08-09 14:00 CEST] 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
[2026-08-09 14:01 CEST] can’t start dump1090, no services that look like dump1090 found
[2026-08-09 14:01 CEST] no ADS-B data program seen listening on port 30005 for 364 seconds, trying to start it…
[2026-08-09 14:01 CEST] attempting to start dump1090..
[2026-08-09 14:01 CEST] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
[2026-08-09 14:01 CEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2026-08-09 14:02 CEST] no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
[2026-08-09 14:02 CEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2026-08-09 14:03 CEST] no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
[2026-08-09 14:03 CEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2026-08-09 14:04 CEST] no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
[2026-08-09 14:04 CEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2026-08-09 14:05 CEST] no ADS-B data program seen listening on port 30005 for 250 seconds, next check in 60s
[2026-08-09 14:05 CEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2026-08-09 14:05 CEST] 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
[2026-08-09 14:06 CEST] no ADS-B data program seen listening on port 30005 for 310 seconds, next check in 60s
[2026-08-09 14:06 CEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2026-08-09 14:06 CEST] multilateration data no longer required, disabling mlat client
[2026-08-09 14:06 CEST] piaware (process 695) is exiting…
[2026-08-09 14:06 CEST] piaware (process 695) is shutting down because it received a shutdown signal (SIGTERM) from the system…
[2026-08-09 14:08 CEST] no ADS-B data program seen listening on port 30005 for 4 seconds, next check in 60s
[2026-08-09 14:08 CEST] my feeder ID is xxxxxxxxxxx
[2026-08-09 14:08 CEST] UAT support disabled by local configuration setting: uat-receiver-type
[2026-08-09 14:08 CEST] site statistics URL: xxxxxxxxxxxxxxxxxxx
[2026-08-09 14:08 CEST] adept reported location: 48.40600, 12.82290, 1427ft AMSL
[2026-08-09 14:08 CEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2026-08-09 14:08 CEST] multilateration data requested
[2026-08-09 14:08 CEST] logged in to FlightAware as user xxxxxxxxxxx
[2026-08-09 14:09 CEST] 0 msgs recv’d from dump1090; 0 msgs sent to FlightAware
[2026-08-09 14:09 CEST] no ADS-B data program seen listening on port 30005 for 64 seconds, next check in 60s
[2026-08-09 14:09 CEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2026-08-09 14:09 CEST] multilateration data requested
[2026-08-09 14:09 CEST] logged in to FlightAware as user Nockenfell
[2026-08-09 14:09 CEST] my feeder ID is xxxxxxxxxxx
[2026-08-09 14:09 CEST] site statistics URL: xxxxxxxxxxx
[2026-08-09 14:10 CEST] no ADS-B data program seen listening on port 30005 for 124 seconds, next check in 60s
[2026-08-09 14:10 CEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet

2

The culprit are your following settings:
receiver="dvb-t".
START_DUMP1090="no"

These setting block dump1090-mutability from outputting data on port 30005. As a result piaware does not get data on this port.

To correct this situation, do following:

STEP 1 of 3
Open config file to edit by following command:
sudo nano /etc/fr24feed.ini.

In this file, delete these two lines

receiver="dvb-t"
path="/usr/lib/fr24/dump1090

Add following two lines

receiver="avr-tcp"
host="127.0.0.1:30002"

Save (Ctrl+O) & Close (Ctrl+x) the file

STEP-2 of 3 :
Open file /etc/default/dump1090-mutability by following command:
sudo nano /etc/default/dump1090-mutability

Scroll down to following line

START_DUMP1090="no"

Change “no” to “yes”, so the line becomes

START_DUMP1090="yes"

Save (Ctrl+O) and Close (Ctrl+x) the file

STEP-3 of 3 :
Reboot RPi to implement changes above
Few minutes after reboot, check status / logs of Piaware

Modifications in fr24feed.ini
Modifications in fr24feed.ini553×285 13.3 KB

Modifications in etc-default-dump1090-mutability
Modifications in etc-default-dump1090-mutability551×250 12.3 KB

. 
5 Likes
3

Wow, what a fast and perfect answer. I did everything as you discribed and now everything works perfect. Only the line path… didnt exist in my config, so i didnt had to delete it.

One more question, only for understanding: The dashboard link “show live data” which opens http://my.local.IP:8080/ still doesnt work. Thats not really neccessary for me. But i want to understand why. Is it possible that this only works in a native piaware installation instead of a fr24 installation with piaware on top?

At least. Aou really made my day. Im so happy that it now works fine. Thank you very mouch!. And should you ever be near my house, ring the doorbell, and you get at least two beer on my terrace :wink:

1 Like
4

The map at http://your-local-IP:8080/ opens “skyaware map”, which shows aircraft, and is provided by dump1090-fa. Since you do not have dump1090-fa, you dont see it.

Your FR24 install uses dump1090-mutability, you can see it’s aircraft map.on the link;

http://your-local-IP/dump1090/gmap.html

If you want to install dump1090-fa, then first uninstall dump1090-mutability.

CAUTION:
Do NOT install dump1090-fa while you have dump1090-mutability installed. Only one of these two can run on same Pi. Installing both will mess your system.

3 Likes
5

Many, many thanks for your help. So i learned something new.

There is no need for me to change from dump1090-mutability to dump1090-fa. I was only interested to know why the link wont work.
I get a nice map from the local link http://1my.local.IP/dump1090/gmap.html Thats already more than i need. So everything is just fine. So, all my questions are answered. I think the case can be closed. THANK YOU !!!

1 Like