Glad to kow you succeeded 
Yes thats very satisfying. Seems I accidentally claimed a new second feeder ID in the process though. Can they be merged or should I just delete one?
You cannot merge.
To stop your Pi from feeding NEW (accidentally claimed) site, and to start it to feed OLD site, do following:
(1) Open your My ADS-B page, on it select the old site, then copy it’s unique Identifier.
(2) Issue following command using Unique Identifier you have copied from My ADS-B Site
sudo piaware-config feeder-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
(Replace xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx by the actual feeder-id(Unique Identifier) you have copied from old site’s My ADS-B page
(3) Restart piaware
sudo systemctl restart piaware
(4) Wait for 5minutes, then go to My ADS-B page to check which station is now showing receiving feed.
The un-fed station will automatically be deleted after 30 days of stoppage of feed. You dont have to do anything.
It worked. Thanks again!
1 Like
Ubuntu 20 amd64 - Package install of ver 7.0 piaware, dump1090-fa, piaware-web, dump978-fa
Debian 11 amd64 - Package install of ver 7.0 piaware, dump1090-fa, piaware-web, dump978-fa
Raspberry Pi OS Bullseye 32-bit (armhf) and 64-bit (arm64 / aarch64) - Package install of ver 7.0 piaware, dump1090-fa, piaware-web, dump978-fa
I finally got it all working correctly on the WIFI extension network, then changed physical location of the pi to another room to get better reception, and so then changed the wifi that the pi was on to the main network which is closer to the new location… it seemed like a minor change to make but for some reason when I then went to the IP that usually shows my FlightAware status page it said “This site cant be reached”. When I change back to the WIFI extension network it works again. Any ideas what’s going on?
Does the Pi have the same IP adress on both Wi-fi networks ?
If so did you flush the DNS record for the old wi-fi network so that the network doesn’t look for the Pi on the “old” Wi-Fi network ?
Normally you have a TTL (Time to live) entry in your system that informs the router how long a ip address should be reserved for a certain mac address.
Probably this is preventing your Pi to be discoverd on the “new” Wi-Fi network.
Thanks, yes same IP on both. How do I flush the DNS record?
Is there somewhere in the piaware/boot files that I need to specify the Wifi (or that’s only on the SD image, not the package I’ve installed over Raspberry OS)? if yes how do I run the config again?
Does restarting the wifi router flush the DNS record?
Yes the restart of the Wifi router will fix this issue, all Ip’s will be handed out again after the reboot. old records are then discarded
wifi has only to be specified on the SD image
Ok that worked for a minute but now nothing works, and going to the IP address of the pi shows all red buttons. I think I broke it
I checked the router admin and the IP had changed, so all is seemingly working again… how do I set a static IP?
I found this in the router admin but am not sure what to put in each field:
Add Static Route
Destination
Mask
Gateway
Interface (HSI autoselected as only option)
Metric
Does anyone here know what I put in each field?
Also how do I choose the static IP, do I just make it up?
Are you able to make a DHCP reservation in your router ?
That would be the most simple way to get the Pi back to the same IP adress again and again.
Look up the current IP address and the MAC address associated with it.
A static route as you showed is from the internet to a device within your network and that is not what you are looking for
What is the type of router you have ? Then I can look up the steps in the manual for it.
Thankyou so much! Its a Model FG824CD.
I found this in the router admin so seems yet I can make a DHCP reservation:
Static DHCP - Home Network
Device nameMAC AddressIP
New device
My Router (AVM brand) is having an option to assign always the same IP to a device, independent if it’s inside or outside the DHCP range. This is handled via MAC-Adress of the device.
Even if I rebuild one of the devices with whatever OS, it always get the same IP
Start with creating a new device
Put in the ip address of the Pi. This can be found on your flightaware statistics page once you have logged in.
Underneath the unique identifier key you will see the MAC address and the site local ip adress. Use the local IP address and the MAC address to create a DHCP reservation.
After saving that you will have set the reservation, this will enable the Pi to reclaim the same IP address after each reboot of either the Pi or the router
You don’t need to use the internet IP address
Excellent. I’ve done that now. Thanks so much again!
When I moved the feeder I was able to update FA and FR24 with new lat, long and alt settings but can’t work out how to change it on ADSBexchange… should I just run the install again? adsb-config.txt doesnt seem to exist anywhere on my pi so sudo nano /boot/adsb-config.txt doesnt work. Any ideas?
If you run the script installer, the config file is located at /etc/default/adsbexchange
In this file you will find the location settings you’ve done during setup.
You can simply change it there
After the change don’t forget to restart both services
sudo systemctl restart adsbexchange-feed
sudo systemctl restart adsbexchange-mlat
1 Like