No Location. Multiple Errors

[NeoDuder]

I've been at this for hours now with no joy. Help.

[NeoDuder]

[NeoDuder]

I think I've fixed the above issues. However, updating seems very hit or miss and location is shown as unknown most of the time. My version is showing as 1.7.0-3 and I can't seem to upgrade this. Is there a special way of updating that I'm missing? I've downloaded 1.7.0-4 multiple times via HACS, but it never seems to update.

[DominicWindisch]

How did you fix them? Got the same issues. The apparent 1.7.0-3 is just showing because the manifest wasn't updated in the last release. So the release is called -4 (that's what its showing in HACS) but the manifest still says "version 1.7.0-3" so that's what its showing after installation.

[NeoDuder]

Mmmm, seems like I didn't. It worked briefly, but now back to "Unknown" for location. I've been at this for weeks now, trying to get a decent tracker that I can integrate with HA. I've tried Tiles, Airtags, and thought I was on to a winner when I found this. Unfortunately, no banana, lol.

[jleinenbach]

Please use the built-in diagnosis. This is the entity of the integration device. I suspect your secrets have expired. I myself use the Moto tags and never have such problems, but I don't think it's because of the Moto Tsgs. Unfortunately, your information is not enough, Please use the built-in diagnosis. There is an integration device with lots of hints. I suspect your application has expired. I myself use the Moto tags and never have such problems, but I don't think it's because of the Moto tags. Unfortunately, your information is not enough to make the problem more comprehensible.

[DominicWindisch]

I was using an age old version for quite some time and that worked fine until apparently something changed on googles end :( I have restart HA a couple of times yesterday to get some debug statements in and it now miraculously works just fine. I guess a race condition during initialization or some connection/token/supervisor refresh 🤷

[NeoDuder]

Ok. I'll add what information I can. I'm using Chipolo Pop tags. The initial setup was quite frustrating, especially the section requiring use of the Python script to get the keys via Chrome. No matter what I tried with this, it wouldn't recognise Chrome, despite having the latest version installed. I eventually got this working by using this specific version, and even then I had to use a Beta version of Chrome...

https://github.com/moons-14/GoogleFindMyTools/tree/cert_sha1

Diag attached below. Any help would be very much appreciated.

config_entry-googlefindmy-01KJJ36MMSR0XB0NWTXPX9GH5T.json

[NeoDuder]

Ok, I've wiped and reinstalled it all again, and it appears to be working. Just a few questions...

'Current Location' and 'Last Location' both show as 'Home'. The current location will eventually go to "Unknown", which I assume is because the tracker hasn't moved. I'm trying to decide if assigning 'Last Location' or 'Current Location' will be better when assigning to a person. Will 'Last Location' always show as 'Home' until the tracker is seen at another location outside the 'Home' zone? I guess what I'm asking is does 'Last Location' just latch the current value of Current Location whenever it changes? Or does it show the previous location? i.e. 2 "Seens" ago. Not sure if I'm making sense, lol.

My main purpose of this is to use a Tracker for my Dad, who has dementia, to be able to automate alerts via NodeRed if he decides to go wandering.

[jleinenbach]

Correct. Current location is always up-to-date or unknown. Last Location keeps the last seen location, even if the tracker wasn't seen for a long time.

[NeoDuder]

Ok, cool. I'll assign 'Last Location' in that case. Thanks for your help, and all your work on this. :)

[Dahaniel]

Looks exactly like the issues I am having. How did you fix it?

I purged and reinstalled the integration, I also regenerated the keys. It always works a single time after reinstalling, then my devices go silent.

I have 1 phone and 2 pebblebee trackers, none work

[jleinenbach]

There's a race condition, but the issue should be fixed if you reboot.