Skip to content
This repository has been archived by the owner on Aug 10, 2023. It is now read-only.

Been playing, and noticed some differences #30

Open
psyciknz opened this issue May 12, 2018 · 1 comment
Open

Been playing, and noticed some differences #30

psyciknz opened this issue May 12, 2018 · 1 comment

Comments

@psyciknz
Copy link
Contributor

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

@psyciknz
Copy link
Contributor Author

Another thing I've never found, but is useful on the service.
Every 10 seconds or so it receives a status of the partition:

2018-05-12 07:23:24,673 [1] INFO Paradox - MonitoringStatus: 1 Item: Area:1 Status: Ready,Armed,Sleep Armed
2018-05-12 07:23:32,845 [1] INFO Paradox - MonitoringStatus: 1 Item: Area:1 Status: Ready,Armed,Sleep Armed
2018-05-12 07:25:12,892 [1] INFO Paradox - MonitoringStatus: 1 Item: Area:1 Status: Ready
2018-05-12 07:25:22,142 [1] INFO Paradox - MonitoringStatus: 1 Item: Area:1 Status: Ready
2018-05-12 07:36:58,456 [1] INFO Paradox - MonitoringStatus: 1 Item: Area:1 Status: Ready
2018-05-12 07:37:07,675 [1] INFO Paradox - MonitoringStatus: 1 Item: Area:1 Status: Ready

Anyone ever found that event?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant