You probably don’t want to run this script as it probably exists on your Home Assistant instance, but instead run it on another machine on your network and point it at an MQTT broker that Home Assistant is reading from.
If this reads like greek to you, it might be best to wait for a proper integration to show up at some point, which is probably what I’m going to do.
This may be more of a Google question but do any of you know why a lot of my devices often only send a semantic location and not coordinates? My pixel watch 3 and pixel 9 pro phone always send coordinates but my pixel buds 2 pro and Chipolo trackers more often only send ‘semantic location: home’ which foes not publish to mqtt.
They do sometimes send coordinates but i cannot figure out under what circumstances they choose one over the other.
Same problem here for Two days no problem, Always received coordinates.
From today evening only semantic location “home” for my tracker android find my
I’m having a problem with the device tracker, it appears fine on a map, but the state of the device tracker stays always as unknown. Even if the device tracker is inside of a zone. Is this normal?
Edit: I also realized that I keep getting “semantic location: home” and that home assistant displays it as “unknown” in the GPS coords.
The only difference between the two scripts is that endeavour includes MQTT, and at the end of the instructions you start publish_mqtt.py instead of main.py
Thks for this “how to”, could you please help on how to get Chrome loading and allow me to authenticate please ?
I’m under Linux (Ubuntu 25.04) and nothing happened here :
(venv) lolomin@hydra:~/GoogleFindMyTools$ python3 main.py
Loading...
[AuthFlow] This script will now open Google Chrome on your device to login to your Google account.
> Please make sure that Chrome is installed on your system.
> For macOS users only: Make that you allow Python (or PyCharm) to control Chrome if prompted.
[AuthFlow] Press Enter to continue...
[AuthFlow] Installing ChromeDriver...
[ChromeDriver] ChromeDriver gestartet.
[AuthFlow] Waiting for 'oauth_token' cookie to be set...
Got this and it seems Chrome never starts/open a new tab so I’m stuck ?
All python requirements are filled, I have also tried without a venv but same thing happened
first of all, I’m afraid I have to tell you that I have also familiarized myself with ChatGPT and therefore only know my way around to a limited extent. I just wrote down the steps of what I did in the hope of helping others.
However, I had a similar problem under windows. I could help myself by starting Chrome in debug mode and slightly modifying the C:\WINDOWS\system32\GoogleFindMyTools\chrome_driver.py. Have a look at my instructions for Windows.
Two things are changed there:
The chrome driver was missing in Windows. Here I have adjusted the path manually
@xHecktor seems like you are hardcoding the gps location for “home” and passing it through in that case? That seems overly complex.
As far as I am aware you can just pass a state home and that should still work in Home Assistant? the GPS coordinates are not actually required.
No unfortunately not. The koordinates are in the attributes. For every message to home assistant it need a state. But Google delivers the semantic value “home” for example only if you are home. Otherwise it would be unknown as state in every message. You can do that. But than home Assistant would take unknown in state and one secound later it would realize that your koordinates in the attributes are the home koordinates. So it would set home as status again. So in one sentence it switches between unknown and home every single update trigger. If that is what you mean.
The other thing is if I don’t send koordinates in the attributes, home assistant would override the status from home to unknown.
But what you see for example “kitchen” is what I added extra. So if it is in kitchens als semantic value. The status is set as kitchen with home koordinates. That means HA change it from kitchen to home and in the attributes you can see the semantic value kitchen all the time. I thought it could be useful for logging. Because status is logged in history but not the attributes.
Yes, the way the script is currently working, it publishes “unknown” as the state, plus the GPS coordinates, and Home Assistant then updates the state based on the GPS coordinates.
I managed to workaround the “Semantic Location” issue and I will open a PR on that repo today (i like the docker and overall neat approach).