Closed brijvs closed 1 week ago
Yikes. Yes, that's been tested and certainly did work.
I've only just had a chance to re-test this and I was unable to reproduce the issue. Alarm was triggered and successfully ran a HomeKit automation I have set up.
I tested Homebridge 1.4.0 on Node 16.14.0.
I downgraded my version of node as that was causing other issues with the plugin. But now am running on 1.4.0 and node 16.13.2, will test again and let you know. Might be an issue with Node 17? 🤷🏽
Can confirm there is a problem with the alarm status not updating. Mine's been stuck on armed for a few weeks. Will investigate.
This will be fixed on the armdisarm branch as the alarm status logic is being rewritten there.
Looking at the logs, this is what showed up:
[homebridge-texecom] This plugin generated a warning from the characteristic 'Security System Target State': characteristic was supplied illegal value: number 4 exceeded maximum of 3. See https://git.io/JtMGR for more info.
I'm pretty sure it used to work before.
Using home bridge v1.3.8 on node 17.0.1