Closed robvolgers closed 1 year ago
Oh and could you PR to the dev branch?
Also, just had the Actions run, and apparently the test where not adapted!
Hi @robvolgers I finally got around to doing some work on this package, I have added support for the device timezone in the account (in the dev branch), have done that based on pytz timezones, with a default on UTC. Please have a look. I will look at the binary stuff as well.
Just created a release with these features, 3.1.0b1, check it out @robvolgers
This alarm system has two specific quirks which pysiaalarm has to be aware of to work properly: it needs to support messages where the CRC is in binary instead of hexadecimal, and it needs to support devices which have timestamps in local time instead of UTC.
I've seen the "binary CRC" thing mentioned online for some other alarm systems, so it doesn't seem to be unique to this specific brand. I'm not sure if other systems exist that also use non-UTC time.
The commit messages should be pretty self-explanatory. Please check the message for the binary CRC commit to see some comments about why a server setting is necessary, and how it could possibly be avoided with some changes to error handling.
The binary CRC commit also has an unrelated correctness fix for responses, as noted in the commit message.