Ugh. My old PiAware died and in swapping it out I accidentally deleted my old feeder. Is that something an admin can fix? I feel so dumb, pilot sad.
On the stats page you should be able to find the old feeder id or the unique identifier.
You can add that on the new feeder.
sudo piaware-config feeder-id XXXXXXXXXXXXXX
is the command, youâd have to ssh into the pi before.
Or modify the piaware-config file, which should be in the visible boot partition. Hope that is still accurate.
Following this link via brother in your network is another way to find the id, all id should be listed there.
1 Like
Thanks so much. I did last time for forgot this time.. and âcleaned out â the old station. This is the source of the dumb feeling. Is the site ID the feeder ID (and not the unique ID)? Iâm not finding the old feeder ID, but I do have the site number.
The feeder ID is the long âUnique Identifierâ shown under âSite Informationâ if you go here while logged in: https://www.flightaware.com/adsb/stats/user/FerventGeek. But I only see one active site, which was only created recently; how long was the old site down for?
If you have the old site ID thatâs easy for us to look up (Iâm just not in front of a db client right now)
(later): I re-enabled site 32488 for you, which I think is the one you were after. You should see that on your stats page now, you can copy the feeder ID from there.
3 Likes
Thanks so much obj, Iâm all set. I love this community! 
2 Likes
Well shoot.. now i have two stations with the same feeder ID, and the Station edit form isnât showing the delete link- perhaps because if the duplicate feeder ID?. Site 266929 is the one I accidentally created and donât need, 32488 is my forever site to keep.
Is there a way for me to fix that? Can create a 3rd Station with a new id, then maybe delete the two stations that I shouldnât have, then re-register the feeder with the old stationâs feeder ID?
Thank you again for help unwinding my goof.
You are now feeding only one site (32488),
The feed to other site (266929) has stopped as soon as you started feeding your old site.
It will show after your feed to new station remains stopped for few days. check again tomorrow and after tomorrow.
2 Likes
Well.. hmm still all red for the status. MLAT is itâs own thing. Iâve reset the location several times and rebooted, but still no love. Iâm hoping thereâs a ghost of the accidentally created account in the DB somewhere of a duplicate feeder ID.
How many site âshouldâ you have?
I can only see one: Site 32488, This was created 10 years ago.
Any site the never saw data, or have been off-line for a month donât display.
Thanks geckoVN,
Iâd accidentally created a second feeder last month when my 10yo Pi died- yes I missed the feeder ID update step. That feeder has been removed and the correct feeder ID has been re-associated with my Pi. From the feed heat-map itâs clearly sending data (minus MLAT but that feels secondary). But why PiAware and FlightAware are showing red status is the mystery.
Logs:
[2026-03-17 10:42 CDT] mlat-client(xx): Receiver status: connected
[2026-03-17 10:42 CDT] mlat-client(xx): Server: 0.0 kB/s from server 0.0kB/s TCP to server 2.0kB/s UDP to server
[2026-03-17 10:42 CDT] mlat-client(xx): Receiver: 387.0 msg/s received 185.6 msg/s processed (48%)
[2026-03-17 10:42 CDT] mlat-client(xx): Results: 13.6 positions/minute
[2026-03-17 10:42 CDT] mlat-client(xx): Server status: synchronized with 474 nearby receivers
[2026-03-17 10:42 CDT] 300764 msgs recvâd from dump1090-fa (2621 in last 5m); 300764 msgs sent to FlightAware
[2026-03-17 10:47 CDT] 303431 msgs recvâd from dump1090-fa (2667 in last 5m); 303431 msgs sent to FlightAware
Maybe a stupid question, are you looking at the same IP address as where the Pi is located ?
Are you looking at the status of the buttons on the Feeder page or maybe via Piawareweb that is on a different IP address ?
The screenshot at the top of this thread from Feb 6th.
Two days ago, you wrote:
Hence my surprise when I took a look at your Stats Page and it seemed to be working very well.
Even your MLAT looks fine from the outside
Looks like my db surgery was incomplete. I tweaked it a bit more, check again now?
(it was mostly cosmetic, data was still being processed etc, there was just one missing link that broke the status indicators)
1 Like
Thank you, obj. All green status now. Appreciate you help.
Lesson: First rule of dead Pi replacement club: note and set the feeder ID first.
2 Likes