Fixing issues in timestamp MQTT publisher#1
Open
cmos486 wants to merge 1 commit into
Open
Conversation
… (fix 'int too big to convert' and string timestamp parsing)
cmos486
changed the title
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
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 PR introduces
publish_mqtt.py, a script that publishes tracker locations from Google Find My Tools to an MQTT broker, compatible with Home Assistant's device_tracker discovery.✅ Key features:
invalid literal for int() with base 10: '2025-05-18 10:37:46'int too big to convertfrom millisecond values.Tested successfully with multiple Bluetooth and Android trackers.
Let me know if you'd prefer this as an example script or if you'd like further integration.
Thanks for this awesome tool!