Upgraded Pi, new site id not on stats page



I have just upgraded my PI from a 2 to a 3, so this means that my piaware as a new site ID (MAC address). However, I can’t see the new piaware on my ADS-B stats page. The piaware.out log reports a login as a user that is not me at the very start of the log.

Do I need to do anything to make the new piaware get associated with my account?
I would have thought that I need to enter the location, antenna height etc. of the new piaware - how do I do this?

My old MAC address: b8:27:eb:db:45:d7
My new MAC addess: b8:27:eb:bd:1a:6a

What I know is this:

  1. The dump1090 is working. I can connect to port 8080 and the map and all the aircraft appear correctly.

  2. When I go to the ‘claim your piaware’ web page the system says that I have two units:

Great news! Your account is associated with the following PiAware receivers and you can view your statistics here:

b8:27:eb:bd:1a:6a: PiAware (Debian Package Add-on) 2.1 added Saturday, 23 July 2016 ( /
b8:27:eb:db:45:d7: PiAware (Debian Package Add-on) 2.1 added Thursday, 21 January 2016 ( /
  1. The /tmp/piaware.out shows that I am logged in correctly and information is being sent:

08/04/2016 06:41:04 logged in to FlightAware as user TugBoatRidge
08/04/2016 06:41:13 piaware has successfully sent several msgs to FlightAware!
08/04/2016 06:41:32 22 msgs recv’d from dump1090; 17 msgs sent to FlightAware
08/04/2016 06:46:32 303 msgs recv’d from dump1090 (281 in last 5m); 298 msgs sent to FlightAware
08/04/2016 06:51:32 555 msgs recv’d from dump1090 (252 in last 5m); 550 msgs sent to FlightAware

Now what is strange is this:

A) My stats page does not show the new piaware at all.

B) The stats page is updating, because a warning has appeared for the old piware that it has been offline for a few hours.

C) The /tmp/piaware.out contains this very strange report of a login as ‘suedavis’ at the start:

08/04/2016 05:40:46 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
08/04/2016 05:40:46 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
08/04/2016 05:40:46 Started faup1090 (pid 2482) to connect to dump1090
08/04/2016 05:41:06 279 msgs recv’d from dump1090 (24 in last 17092m); 0 msgs sent to FlightAware
08/04/2016 05:41:50 Connecting to FlightAware adept server at piaware.flightaware.com/1200
08/04/2016 05:41:50 Connection with adept server at piaware.flightaware.com/1200 established
08/04/2016 05:41:51 FlightAware server SSL certificate validated
08/04/2016 05:41:51 encrypted session established with FlightAware
08/04/2016 05:41:51 autoUpdate is not configured in /etc/piaware or by piaware-config
08/04/2016 05:41:51 manualUpdate is not configured in /etc/piaware or by piaware-config
08/04/2016 05:41:51 multilateration support enabled (use piaware-config to disable)
08/04/2016 05:41:52 logged in to FlightAware as user suedavis

what this has to do with my configuration/installation is beyond me…

D) I have received no emails about the new piaware. I thought that perhaps I would receive notification that the new unit was connected and associated with my account.

E) When I look at the track log for a local aircraft that I know would normally be record using my data, there is nothing there. Also my stats page shows no recent aircraft tracked.

F) My mlat capability is not actually starting. I assume that this may be related to the precise location for the new unit not being known. Which brings me back to why can’t I see my own piaware?

Additional information:

  • I powered back up my original Pi and it immediately connected to flightaware.
  • My stats page immediately showed the reconnected unit and the status updated

Has anyone got any ideas what is happening?


Quick workaround: I tried forcing the MAC address of the new Pi to the same value as the old one and everything started working correctly. This is using the original Site ID - which is why everything keeps working.


User suedavis joined FlightAware on 8/4, the date of your post, and a PiAware feeder was active for around 4 hours. Both “suedavis” and your “TugBoatRidge” account are located in New South Wales, so it seems most likely that you accidentally created a second account and associated your new Raspberry Pi with it: