Problems claiming Piaware


#1

Just built a piaware device and manually configured the login and password. After waiting for several hours and not being able to claim my device, I ran sudo piaware-status and received the following:

dump1090 is running.

faup1090 is running.

piaware is running.

dump1090 is listening for connections on port 30005.

faup1090 is connected to port 30005.

piaware is connected to FlightAware.

dump1090 is producing data on port 30005.

Additionally, I ran sudo piaware -debug:

pi@piaware ~ $ sudo piaware -debug
01/10/2016 18:21:28 ****************************************************
01/10/2016 18:21:28 piaware version 2.1-5 is running, process ID 6236
01/10/2016 18:21:28 your system info is: Linux piaware 4.1.13-v7+ #826 SMP PREEMPT Fri Nov 13 20:19:03 GMT 2015
armv7l GNU/Linux
01/10/2016 18:21:29 Connecting to FlightAware adept server at piaware.flightaware.com/1200
01/10/2016 18:21:29 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
01/10/2016 18:21:29 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
01/10/2016 18:21:29 Started faup1090 (pid 6248) to connect to dump1090
01/10/2016 18:21:29 Connection with adept server at piaware.flightaware.com/1200 established
01/10/2016 18:21:29 FlightAware server SSL certificate validated
01/10/2016 18:21:29 encrypted session established with FlightAware
01/10/2016 18:21:29 autoUpdate is not set in adept config, looking further…
01/10/2016 18:21:29 autoUpdate in /etc/piaware is enabled, allowing update
01/10/2016 18:21:29 manualUpdate is not set in adept config, looking further…
01/10/2016 18:21:29 manualUpdate in /etc/piaware is enabled, allowing update
01/10/2016 18:21:29 multilateration support enabled (use piaware-config to disable)
01/10/2016 18:21:30 logged in to FlightAware as user chris12381
01/10/2016 18:21:32 piaware received a message from dump1090!
01/10/2016 18:21:59 6 msgs recv’d from dump1090; 6 msgs sent to FlightAware
01/10/2016 18:22:02 piaware has successfully sent several msgs to FlightAware!

I can see aircraft on the local dump1090 map. So, based on the above output(s) piaware is communicating and sending data to flightaware successfully under my flightaware account.

However, when I try and claim the device, I’m told “Unfortunately, FlightAware hasn’t found a new, unclaimed PiAware connection yet from your IP (xxxxxxxxxxxxxxxxxxxxxxxxxx). Either your device has not yet connected (it takes a few minutes to start) or you are on a different IP address.”

Oddly, right below this message, flightaware says, "Linked PiAware Receivers (chris12381)

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

b8:27:eb:2e:a1:f0: PiAware (SD Card) 2.1 added Wednesday, 6 January 2016 (XXX.XXX.XXX.XXX / 10.0.0.15)"

However, when I click the link for stats, I’m told “No Active FlightAware ADS-B Sites For This User (chris12381)”

Can anyone assist me with this?

Thanks,

Chris


#2

I think you just need to wait a couple hours for the user stats page to catch up.


#3

Yeah it’s been running since Friday. Can’t imagine it takes that long?

Chris


#4

That MAC is associated with a different user account. Where did you get the Pi from, was it second-hand?

(manually configuring the login/password doesn’t override the existing MAC/user association, which is where the confusion comes from)


#5

I purchased all of the parts from Amazon and built it myself

Flightaware says:

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

b8:27:eb:2e:a1:f0: PiAware (SD Card) 2.1 added Wednesday, 6 January 2016 (XXX.XXX.XXX.XXX / 10.0.0.15)" **

But on the same page says:

**Unfortunately, FlightAware hasn’t found a new, unclaimed PiAware connection yet from your IP (redacted). Either your device has not yet connected (it takes a few minutes to start) or you are on a different IP address.

FlightAware searches for PiAware connections on the same global IP (redacted) as your connection. If you are on the same LAN as the PiAware device, then we should be able to find the receiver and claim it for you. You should wait a few minutes after plugging in your PiAware device before expecting it to be connected to FlightAware. Try checking cable connections, waiting a few moments, and trying again."**

These two statements are in conflict with each other, no?

Chris


#6

It’s saying your account is already associated with one receiver and it didn’t find a new one to add.

However the data is a bit denormalized and I think that page is looking at a different place to where stats looks, which is why it thinks you’re associated but then no stats show up.


#7

I think I see where the problem is coming from now. I’ve disabled the wrong association for now so it should start associating with your account properly, and raised an issue to fix things so it doesn’t happen again.

(basically the problem was that before you claimed the receiver, FA associated the data with a different user based on IP address, and the stats system then created a new ADS-B site associated with that user. When you later claimed the receiver, stats didn’t notice and continued to use the old site rather than disabling it and creating a new site associated with your user)


#8

Thanks! Working just fine now.

Chris


#9

I am having the same problem. I just upgraded my piaware from a raspberry pi 1 to a Pi2. the new Pi shows as unclaimed.


#10

I am having the same problem. I rebuild my raspberry pi running piaware. Can someone help me get the new one registered properly?


#11

FlightAware Support here.

Is everything OK now? I can see an active PiAware feed on you account.


#12

same here:
should be phg2k but seems to be “2018-03-24 15:00:15Z logged in to FlightAware as user yzyjim”.
For whatever reason… did a reinstall using adbsreceiver.net - image.
Thanks!