Feeder ids are allocated even when the site is using Mac address as the primary identifier so that we can move the existing site to use feeder id without losing the existing site association when the time comes
Regret doing an update! My Mac address changed (thought spoofing would work but someone didnāt check the forum 
) and now I have two feeds. 
flightaware.com/adsb/stats/user/ ā¦ tats-57171 is the one I want gone!
I upgraded the hardware of my site and canāt configure is to my old feeder-id. Itās an older site recognized by itās Mac adres. I did find a feeder ID in the old piaware logfiles and tried to configure that. Didnāt work.
Is there anyway I can get my old feeder stats back or is it really history, which would be a bit disappointing.
I added a test-site but this whole configuration exercise left me with 4 feeder sites.
Please see thread Bake a Pi
If you have installed Piaware 3.5.0 image (SD card), go to OPTION-1, item ā(5) (c) If you are replacing old Pi by a new oneā
If you have installed Raspbian + Piaware 3.5.0 (package install), go to OPTION-2, item ā(9) If you are replacing old Pi by a new oneā.
After steps mentioned above, you will have to delete file feeder_id before reboot
sudo rm /var/cache/piaware/feeder_id
sudo reboot
.
I had almost the same situation here. Spoofing the MAC-Address but new feeder was generated.
The very, very dirty way to solve this is described hereā¦ post207088.html#p207088
But please just read also the following post from objā¦ Anyway my new Orange Pi will do the same job as the old one before 
I just upgraded the software (apt-get update && apt-get upgrade) I then rebooted and it moved to the new feederid system.
Can you please help re-point to my old one? I donāt want to loose my streak if I donāt have to over a simple reboot.
Old/Correct site: 33214 New site: 58999
Thanks!
If you want to restore your old site, take following steps:
(1) Note down the mac address from your Flightaware stats page of the old site
(2) Delete the new 128 bit feeder id (xxxxxxx-xxxx-xxxx-xxxxxxxxxxxx) from following places
-
pi@piaware:~$ sudo rm /var/cache/piaware/feeder_id
-
pi@piaware:~$ sudo nano /boot/piaware-config.txt
#scroll down to bottom of file and see if you can find a line āfeeder-id xxxxxxx-xxxx-xxxx-xxxxxxxxxxxx # updated by fa_piaware_configā. If the line is there, delete this line, and save file. If you dont find this line, close the nano editor. -
pi@piaware:~$ sudo nano /etc/piaware.conf
#scroll down and see if you can find a line āfeeder-id xxxxxxx-xxxx-xxxx-xxxxxxxxxxxx # updated by fa_piaware_configā. If the line is there, delete this line, and save file. If you dont find this line, close the nano editor.
(3) Spoof mac address as follows:
pi@piaware:~$ sudo nano /boot/cmdline.txt
#this file has all text in one line. At the end of this line, add one space and add āsmsc95xx.macaddr=xx:xx:xx:xx:xx:xxā (without quotes " "), where xx:xx:xx:xx:xx:xx is the mac address you noted from old siteās stat page.
Make sure that there is no line break between existing text and āsmsc95xx.macaddr=xx:xx:xx:xx:xx:xxā, else the spoof will not work.
(4) Now reboot the pi for spoof to take effect.
Check your Flightaware stats page.
If you started from a piaware 3.3 sdcard image then upgrading the system packages has left your system in a broken state (see the announcement post in this forum); I suggest reimaging with 3.5.0, which should return you to the correct MAC address & site association.
It was already on 3.5.0.
This worked perfectly! Thanks!
What was the original sdcard image that you wrote?
I re-imaged a new card with the 3.5 Piaware image. I used a spare Pi, perhaps one not seen by FA before, and was assigned a feeder ID. When I got everything set up, I moved this card over to my the Piaware with the rooftop antenna. Letās call it the production Pi. While it worked, it is seen as the test box and hence a brand new set of stats. Thatās not the end of the world of course, but I thought Iād try to correct this. Note that the MAC spoofing in cmdline.txt did not work. i was doing that already since this production Pi isnāt the same one I started with years ago.
I took the feeder ID from the old production system. It has one, even though it was being identified by MAC address at FA. And put that feeder-ID into piaware-config. No love. It failed to sign on to FA. There was an error about invalid feeder ID and user/password. I donāt specify a user/password. I was spoofing the MAC address in cmdline.txt though.
The solution was to add force-macaddress into piaware-config as well as feeder-id. I was able to remove the MAC address spoofing from cmdline.txt. Now it all works and the stats continue under the old systemās identifier at FA.
Note this problem only arises if you use a different Pi to build your setup than you do to normally run it in production.
Hope this helps others who have a similar problem.
@Jranderson777
Since your microSD card was re-imaged with Piaware 3.5.0 image, and finally used in old production Pi, there was no need to spoof or force MAC address.
All you needed to do after sliping-in re-imaged microSD card in old production Pi and powering up, was to delete the feeder_id file in cache, and reboot.
pi@piaware:~$ sudo rm /var/cache/piaware/feeder_id
pi@piaware:~$ sudo reboot
NOTE:
For fresh installs (i. e. re-imaging to Piaware 3.5.0), the mac address spoof / force mac address is not needed for an old Pi already registered with Flight aware.
The MAC address spoof or force mac address may be required for upgrades from Piaware 3.3 (or older) to Piaware 3.5.0.
The Mac address spoof is also needed if you are replacing old Pi with a new Pi and want to retain old station number and itās stats.
Top post updated. Everything is using feeder IDs now. It shouldnāt be necessary to mess with the MAC address any longer.
From the top post:
āand you can migrate to new hardware and keep the site so long as you also upgrade PiAware at the same time and configure the feeder ID.ā
So in the install of 3.5 itās going to prompt me for the feeder ID or just my FA credentials? Both?
Jim
(great news by the wayā¦ canāt wait to get off 2.xā¦ lol)
After installing 3.5 you can configure the feeder id as described in the top post via piaware-config, using the feeder id of your current site. You never need to configure FA credentials and those config options are going away soon.
Great news! Time to finally upgrade my Pi 1 that run 100% CPU 16h a dayā¦ Thank you!
Is there anyway to get it to quit changing feeder_idās after every reboot? /boot/piaware-config.txt has the feeder-id listed there properly. Iāve tried to remove/change/lock, etc /var/cache/piaware/feeder_id and no matter what, I have to reset the feeder_id every time I reboot. Iāve gone so far as to create a completely new SD card and still have the same problem. All works great, until I need to reboot. This only became a problem after I updated to the last few versions of 3.5.x and Iām currently on 3.5.3. This only happens on reboots. If I simply restart piaware, then all remains fine. Thanks for any help on this.
Chief