search

MaxWinterstein / homeassistant-addons

GNU General Public License v3.0
132 stars 39 forks source link

ADS-B FlightAware Unique Identifier changes after HA restart / upgrade #111

Open pstoian opened 1 year ago

pstoian commented 1 year ago

After the Home Assistant upgrade or reboot - the ADS-B Addon is stop connecting with FlightAware servers. I have to re-claim it via FlightAware web site - and appears as a different device hence new Unique Identifier. In the last week after HA OS or HA supervisor upgrade - I have to reclaim it several times and in each instance a new ID was showing.

MaxWinterstein commented 1 year ago

Can't really confirm that. Do you have a PIAWARE_FEEDER_DASH_ID in your config?

Might share your config (redacted of course)?

pstoian commented 1 year ago

Yes - the PIAWARE_FEEDER_DASH_ID is all good and has been set. But only when I am rebooting the add one or the HA hardware host - I am loosing the connectivity to FlightAware and I noticed that I have to reclaim it and I have a different Unique Identifier.

SERVICE_ENABLE_DUMP1090: true SERVICE_ENABLE_PIAWARE: true SERVICE_ENABLE_FR24FEED: true SERVICE_ENABLE_HTTP: true PIAWARE_FEEDER_DASH_ID: < MY FEDER ID> FR24FEED_FR24KEY: ADSBEXCHANGE_UUID: "" PLANEFINDER_SHARECODE: "" HTML_SITE_LAT: "my LAT" HTML_SITE_LON: "my LON" HTML_DEFAULT_TRACKER: FlightAware HTML_SITE_NAME:

MaxWinterstein commented 1 year ago

tried to reproduce it, but can't find an issue here.

I am not running HA OS, so it might be related to something. As I was going to switch toward HA OS I will have a look again then.

But for the moment, I am clueless.