You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 10, 2023. It is now read-only.
I've been away fro a while using a windows service based on their SDK, and have looked at coming back to the script as I'm using an odroid C2 now.
I'll reforked my fork (I think), but notice that you use client.publish_with_timestamp now. Any reason for that? How to I pull out just the state and ignore the timestamp.
I also got used to, in the windows service having an alarm heartbeat....so I'll implement that, with an mqtt last will and testament which will show if the connection is alive.
The last thing I got used to on the service was, it would detect my PGM1 being fired via the remote (garage door). Not sure I can get that event, but I did manage to add something for that button being hit message[7] = 9
The text was updated successfully, but these errors were encountered:
I've been away fro a while using a windows service based on their SDK, and have looked at coming back to the script as I'm using an odroid C2 now.
I'll reforked my fork (I think), but notice that you use
client.publish_with_timestamp
now. Any reason for that? How to I pull out just the state and ignore the timestamp.I also got used to, in the windows service having an alarm heartbeat....so I'll implement that, with an mqtt last will and testament which will show if the connection is alive.
The last thing I got used to on the service was, it would detect my PGM1 being fired via the remote (garage door). Not sure I can get that event, but I did manage to add something for that button being hit message[7] = 9
The text was updated successfully, but these errors were encountered: