GoogleFindMyTools for Raspberry#4
Open
xHecktor wants to merge 43 commits into
Open
Conversation
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
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi
I have edited your fork a bit.
I use GoogleFindMyTools on a Raspberry and send Mqqt messages to Home Assistant.
Unfortunately, I can't log in correctly in the Chrome browser on the Raspberry os. Therefore I have to do the login on a Windows PC and then copy the secrets.json to the Raspberry.
I have also taken into account that Google sometimes semantically sends “home” instead of coordinates. If that happens, “home” is converted to coordinates that Home Assistant understands.
The home zone (coordinates + radius) are necessary because Home Assistant always needs a status to transmit the attributes (coordinates). Previously, publisch_mqtt.py always sent unkown as the status and the coordinates as attributes. The consequence was that home assistant set the tracker to unkown with every location update and then read out the attributes in order to set “home” as status again. With this change, the correct status is sent directly to home assistant.
The trigger for determining the location comes from Home Assistant via mqtt