#Suggestion - Verify if new or existing identifier exists for a Companion App in HA Core?

1 messages ยท Page 1 of 1 (latest)

carmine sage
#

I switch phones quite frequently, and do Android 2 Android data transfers in a lot of situations. This is now the third time where I have been lost as to why my home automations that track my phone are going haywire - and it's because when you do the Android 2 Android transfer, it basically copies the setup from HA over from the existing phone to the new phone.

However, what happens if that phone is left on and at home. What happens is that the geographic or enter or exit zone setups will go haywire.

Maybe this is a combination of my automations being done in an inefficient way (but it works for a single person), is that an automation will start, then stop - 6 times a day.

When a A2A android app is initiated, and the companion app starts up, would it be possible to record the "old device ID" of the device, and then verify that on startup, if the device ID is the same for the same token?

That way you don't end up with a device reporting Pixel 8 and then Pixel 9 for the same device back and forth quite often?

#

Suggestion - Verify if new or existing identifier exists for a Companion App in HA Core?

west current
#

There is actually some logic in the Android app that is supposed to stop these migrations because of the single registered device = two real devices issue. I guess that may not be working correctly here.

carmine sage
#

๐Ÿ‘ Can do

carmine sage
#

Sorry for the ping @west current , for the log situation - how would you want me to obtain a log for the Home Assistant app on the "new" device that isn't configured, but still reporting in. ๐Ÿ˜…

west current
#

No log, so fine to leave it empty ๐Ÿ™‚