Well done. You both got things fixed quickly.
Looking at the stats for the original site that had all feeders, you can see that one of you was the traffic 200+ nm SE (Pensacola, FL), and the other was the traffic 200+ nm W (Sacramento, CA).
It looks like within the past 24 hours there is at least one other person with a new station that is going to discover they have the same exact problem. A new group of traffic has shown up 200+ nm NNE, which means another one.
Great job,
-Dan
Did you receive any reply from FA so far?
Maybe @obj can help as member of staff.
Yes. The person that emailed me from FlightAware said re-flashing the SD card would take care of the issue. Apparently its pretty common with the kits they sale I guess. Basically reflashing the SD gives you a new Site ID that you can then claim.
After re-flashing twice I was able to claim the feeder and tie it to my account. Thank you all for the help and suggestions.
Hi all,
Thank you @khotaar14 for bringing this to our attention! This was due to a configuration error that caused a very small batch of FlightFeeder Pros to be shipped with a pre-set feeder id (as @foxhunter correctly predicted) which then prevented those hosts from being able to claim the FlightFeeder Pro to their own account.
We have now mitigated the problem on our side so any FlightFeeder Pros that have already shipped with that misconfiguration will work as expected without requiring flashing the sdcard. We have also made changes to our build process to prevent this type of issue from happening again in the future.
Sorry for the inconvenience. If anyone has any questions or issues going forward, please contact support at adsbsupport@flightaware.com.
Thanks!