Brand new PiAware feeders (from new hardware that has never been seen previously by FlightAware) are now being identified by a unique feeder ID stored by PiAware, rather than by hardware MAC addresses.
If you have an existing site this does not affect you
- existing sites will continue to be identified by MAC address at the moment.
For new sites (running PiAware 3.3.0 or newer), a feeder ID will be assigned when the feeder first connects, and will be stored by PiAware on the sdcard. Subsequent connections will use that feeder ID to identify the site. The main consequence of this is that if you re-image the sdcard or otherwise remove the feeder ID, then subsequently the feeder will look like a brand new feeder and will create a new site.
If you want to retain the same feeder-to-site association when re-imaging, so that the existing site continues to be used, then you can explicitly configure the feeder ID to use. This is a somewhat manual process at the moment:
- Find the feeder ID that you want to use. You can find this either as the "Site identifier" on the site page at https://flightaware.com/adsb/stats/user/yourusername, or from the PiAware logs in /var/log/piaware.log on your existing install. The identifier looks like a series of dash-separated hex digits: 12345678-1234-1234-1234-123456789abc.
- Configure the feeder ID on the new system: piaware-config feeder-id 12345678-1234-1234-1234-123456789abc
- Restart piaware: sudo systemctl restart piaware
This also works when replacing hardware (if it is just a Pi replacement, you can just move the existing sdcard over and the feeder ID will be retained)
Existing sites can't be moved like this - yet. We plan to migrate existing sites to the new scheme in the future, but that's not quite there yet.