Problems Claiming PiAware Station

FlightAware ADS-B Flight Tracking
1

I requested that Flight Aware provide me a 1090 Receiver set up, and they agreed to do so. I imagine I will receive it within a few weeks. The problem is that I have built my own 978 UAT receiving station based upon purchasing the FlightFeeder basic, and I don’t know how to “claim” it on the FlightAware web page. When I go to the webpage to claim it, the FlightAware web site thinks that I am attempting to claim the receiver THEY Sent me for 1090 Mhz–which I don’t have yet.

So how do I accomplish this?

2

Try the method given here:

You can get the feeder ID by following command:

cat /var/cache/piaware/feeder_id
1 Like
3

Thank you for the prompt response. I am still confused.

I understand the what I have to do once I get the feeder ID, but how to get the feeder ID is hazy.

Where do I input the “cat/var/cache/piaware/feeder_id?” command? In some DOS window? In my browser? Please explain

Thanks,

HUGO

From “abcd567” <notifications@flightaware.discoursemail.com>
To dahugo@me.com
Date 6/24/2026 7:03:39 PM
Subject FlightAware Discussions: Problems Claiming PiAware Station

4

The ID is generated when a new station goes live.
You then go to the Claim Page and associate the ID with your account
(hint: the station and the device you are claiming the ID from, must be on the same network)

5

If you have installed PuTTY on Windows, then using PuTTY, SSH to Pi and issue the command:
cat /var/cache/piaware/feeder_id

Alternatively you can use following method:

STEP-1:
On Windows Computer, Press Windows Key + R. This will open Run Dialog.
Type cmd in the box, and hit Enter. Please see screenshot below.

windows-command-prompt
windows-command-prompt447×276 45.5 KB

STEP-2:
The STEP-1 will open Windows Command Prompt.
In the command prompt , type:

ssh pi@192.168.12.24
(Replace 192.168.12.24 by actual Local IP of your RPi).

You will be prompted to
(1) accept ssh key fingerprint
(2) enter Pi’s password.

After you type password & press Enter Key, the Pi will be accessable.
Now type (or better copy-paste) following command and press Enter Key.

cat /var/cache/piaware/feeder_id

Please see screenshot below;

piaware-feeder-ID
piaware-feeder-ID763×573 24.5 KB

6

abcd567–Thank you for taking baby steps with me, but this brings up another question. I am to input the IP of my RPi. Where do I get that information?

From “abcd567” <notifications@flightaware.discoursemail.com>
To dahugo@me.com
Date 6/24/2026 9:43:47 PM
Subject FlightAware Discussions: Problems Claiming PiAware Station

7

Option-1:
Find it from your internet router

Option-2:
You can ssh without knowing your RPi’s Local IP address by typing following command in PuTTY or Windows Command Terminal

ssh pi@raspberrypi.local

Note:
Replace pi with your actual configured username, and raspberrypi with your actual configured host name, if you changed these during setup.

For example I changed hostname from raspberrypi to rpios-trixie, so instead of command ssh pi@rapberrypi.local, I used command ssh pi@rpios-trixie.local, as shown in screenshot attached below.

 

ssh-pi@-raspberrypi.local
ssh-pi@-raspberrypi.local789×598 58.6 KB

8

If you have a Piaware SD Card Image

 
While logged-in to your Flightaware account, do following:

(1) Open browser
(2) In address bar of browser, type following address, and hit Enter Key

piaware.local

(3) The step (2) above will open piaware-web page (see screenshot below)
At bottom of this page there is a link to claim your RPi.
Click the link. It will take you to Claims page.
Follow instructions on Claims page.

 

claim-piaware-sd-card
claim-piaware-sd-card754×636 37.5 KB

 

2 Likes
9

When trying to connect to an os like armbian or dietpi using hostname.local returns “cannot connect, address not found”, then most likely mDNS is not working. To fix mDNS, install package avahi-daemon and then try again.

Please see the last line of avahi-daemon’s log posted below:

abcd@debian-14:~$ sudo journalctl -u avahi-daemon -n5 

Jun 26 11:59:56 debian-14 avahi-daemon[18358]: Registering new address record for fe80::a00:27ff:fe65:134c on enp0s3.*.
Jun 26 11:59:56 debian-14 avahi-daemon[18358]: Registering new address record for 192.168.12.40 on enp0s3.IPv4.
Jun 26 11:59:56 debian-14 avahi-daemon[18358]: Registering new address record for ::1 on lo.*.
Jun 26 11:59:56 debian-14 avahi-daemon[18358]: Registering new address record for 127.0.0.1 on lo.IPv4.
Jun 26 11:59:57 debian-14 avahi-daemon[18358]: Server startup complete. Host name is debian-14.local. Local service cookie is 3909558484.
abcd@debian-14:~$