GoogleFindMyTools for raspberry over Mqqt to HA #63
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…n MQTT topic discoverable by home assistant
Chromedriver kann nicht direkt in raspberry verwendet werden. Daher wird die secrets.json von einem anderen Gerät kopiert
Home zone wird festgelegt in Koordinaten falls Google Tag nur semantisch "zuhause" ausgibt Home Zone wird in der Mqtt Nachricht von Home Assistant an Raspberry bestimmt Trigger zum ausführen kommt von Home Assistent
Raspberry kann den chromedriver nicht benutzen. Daher kommt selenium zum einsatz und die secrets.json muss nachträglich von einem anderen Gerät kopiert werden
Mqqt Service restart
Eingabe aufforderung verursacht fehler bei der automatisierten Mqtt abfragee. Daher einfach alle abfragen
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fork of GoogleFindMyTools is intended for operation on Raspberry OS, as there are otherwise problems with Chromeium and the login in Chrome. Communication takes place via Mqqt to Home Assistant (Mqqt Brocker), which runs on a different device.
Since Google Find my Device requires either a location in coordinate form or a string “home”, the publish_mqqt.py was adapted. If google now sends the string home, the Raspbbery replaces it with coordinates for the home zone. The call to update the location is made via Home Assisant via mqtt. This contains the coordinates for the home zone (coordinates + radius).
The home zone (coordinates + radius) are necessary because Home Assistant always requires a status to transmit the attributes (coordinates). Previously, publisch_mqtt.py always sent unkown as status and the coordinates as attributes. The consequence was that home assistant set the tracker to unkown with every location update and then read the attributes in order to set “home” as status again. With this change, the correct status is sent directly to home assistant.
As the Chrome browser on the Raspberry reports “requstest url was not found on this server”, you cannot log in there. You therefore have to install GoogleFindMyTools on a Windows PC, log in and copy the secrets.json with the access data from the PC to the Raspberry. The instructions are therefore divided into three steps: Installation on the Windows PC, installation on the Raspberry OS and then the Mqqt connection to Home Assistant.
In my experience, the update service tends to hang up. The watchdog checks whether the update process has finished within 400 seconds. If not, it kills everything and restarts it. I set 400s because Home Assistant sends a trigger every 5 minutes. If Home Assistant sends the triggers less frequently, the watchdog should also be adjusted. Unfortunately, this is only a temporary solution.
Perhaps someone will find the error