I did a new install to a new sd card of piaware, copying over my old id number.
SkyView worked perfectly showing my site and distance to each plane tracked, but I was only able to see my site working once when I logged into FlightAware.
I removed my id from the new install hoping to have it detected as a new site, but it still shows up as the old one but not working still in flightAware!
You should now be able to claim the feeder again.
As i said this is only a solution if you are currently having the problem that 2 receivers have the same feeder-id. Won’t solve other problems.
I have found what the problem is but so far have been unable to fix it, when I did the reinstall to my Pi3 I changed over to wifi and Skyview worked perfectly, even showing my site, but still not showing in Feeder Statistics - FlightAware page.
If I plug the cable back in all is well, so it’s my config file or a FlightAware problem?
This is my config
This file configures the Piaware sdcard image
configuration. Whenever the system boots, this
file is read and its contents are used to
configure the system.
Lines beginning with a ‘#’ are comment lines
and are ignored. Blank lines are also ignored.
All other lines specify configuration settings.
For simplicity, this file only shows the most common options.
Apart from that i don’t see any problems.
If you connect to this WiFi of yours do you normally need to type in a password on a website or something (captive portal)?
Also with 3 backticks you can inhibit # making things bold
` ` ` (without the spaces)
the config for example
` ` ` (again without spaces to end the "code" block)
The 3 backticks was meant for the formatting on the forum.
I’m not sure where
static-network yes
comes from.
But it’s not in the options as far as i see.
It may be a legacy option from previous versions creating problems.
That’s why i asked you to remove that line.
Also did you restart after changing the options? (I don’t know if you remove the sd-card for changing the options)
This also makes no sense considering your ip address is 192.168.0.28
so broadcast should end in 0.255 instead of 1.255
(not sure if it matters as the netmask is set, probably doesn’t matter)