I have sent several emails to support@hubitat.com about this issue and have not received any response, so I guess I need to post it here.
Several times now I've run into an issue where I disarm a keypad but HSM doesn't get disarmed. Hubitat shows the keypad disarm in the logs, but HSM doesn't disarm itself. Here's my HSM logs this morning:
[app:97](http://192.168.0.55/logs/past#app97)2019-02-13 08:55:08.744 am [info](http://192.168.0.55/installedapp/configure/97)Disarmed
[app:97](http://192.168.0.55/logs/past#app97)2019-02-13 08:54:31.806 am [warn](http://192.168.0.55/installedapp/configure/97)Alert Intrusion-Home pending Garage Entry Door open
Here are the logs from my first keypad:
[dev:257](http://192.168.0.55/logs/past#dev257)2019-02-13 08:54:39.834 am [info](http://192.168.0.55/device/edit/257)Garage Hall Keypad is inactive
[dev:257](http://192.168.0.55/logs/past#dev257)2019-02-13 08:54:38.679 am [debug](http://192.168.0.55/device/edit/257)getMotionResult: active
[dev:257](http://192.168.0.55/logs/past#dev257)2019-02-13 08:54:38.677 am [debug](http://192.168.0.55/device/edit/257)descMap: [raw:catchall: 0104 0501 01 01 0040 00 8A53 01 00 0000 07 00 , profileId:0104, clusterId:0501, clusterInt:1281, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:8A53, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:00, data:[]]
[dev:257](http://192.168.0.55/logs/past#dev257)2019-02-13 08:54:12.644 am [info](http://192.168.0.55/device/edit/257)Garage Hall Keypad was disarmed [physical]
[dev:257](http://192.168.0.55/logs/past#dev257)2019-02-13 08:54:12.637 am [debug](http://192.168.0.55/device/edit/257)armMode:01, armRequest:00, lockCode: [1:[name:Jeremy Akers, code:****]], armChanged:true
[dev:257](http://192.168.0.55/logs/past#dev257)2019-02-13 08:54:12.626 am [debug](http://192.168.0.55/device/edit/257)descMap: [raw:catchall: 0104 0501 01 01 0040 00 8A53 01 00 0000 00 00 00043132323400, profileId:0104, clusterId:0501, clusterInt:1281, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:8A53, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 04, 31, 32, 32, 34, 00]]
[dev:257](http://192.168.0.55/logs/past#dev257)2019-02-13 08:54:09.892 am [info](http://192.168.0.55/device/edit/257)Garage Hall Keypad is active
[dev:257](http://192.168.0.55/logs/past#dev257)2019-02-13 08:54:09.804 am [debug](http://192.168.0.55/device/edit/257)getMotionResult: active
[dev:257](http://192.168.0.55/logs/past#dev257)2019-02-13 08:54:09.795 am [debug](http://192.168.0.55/device/edit/257)descMap: [raw:catchall: 0104 0501 01 01 0040 00 8A53 01 00 0000 07 00 , profileId:0104, clusterId:0501, clusterInt:1281, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:8A53, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:00, data:[]]
[dev:257](http://192.168.0.55/logs/past#dev257)2019-02-13 08:54:09.368 am [debug](http://192.168.0.55/device/edit/257)descMap: [raw:catchall: 0104 0020 01 01 0040 00 8A53 01 00 0000 00 01 , profileId:0104, clusterId:0020, clusterInt:32, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:8A53, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:01, data:[]]
So at 8:54:12 I entered my code and I received a Pushover notification that the keypad was disarmed.
At 8:54:31... almost 20 seconds later... I open the door to my garage. I hear the other keypads start to go off. So I run to another keypad and enter my code again:
[dev:353](http://192.168.0.55/logs/past#dev353)2019-02-13 08:54:54.327 am [info](http://192.168.0.55/device/edit/353)Living Room Keypad was disarmed [physical]
[dev:353](http://192.168.0.55/logs/past#dev353)2019-02-13 08:54:54.321 am [debug](http://192.168.0.55/device/edit/353)armMode:01, armRequest:00, lockCode: [1:[name:Jeremy Akers, code:****]], armChanged:true
The remaining keypads are still beeping. So I run to another keypad:
[dev:738](http://192.168.0.55/logs/past#dev738)2019-02-13 08:55:08.617 am [info](http://192.168.0.55/device/edit/738)Front Door Keypad was disarmed [physical]
[dev:738](http://192.168.0.55/logs/past#dev738)2019-02-13 08:55:08.598 am [debug](http://192.168.0.55/device/edit/738)armMode:01, armRequest:00, lockCode: [1:[name:Jeremy Akers, code:****]], armChanged:true
Finally, this time worked, and HSM was disarmed at 8:55:08 after entering my code successfully on three different keypads.
This seems like a very serious issue. Clearly Hubitat is getting the message that these keypads are being disarmed because the disarm message is: 1) Showing up in the HE logs and 2) HE is triggering the Pushover notifications letting me know that the keypad was successfully disarmed. But even though the keypad is disarmed HSM is not disarming itself.
This issue is sporadic. Most of the time HSM disarms properly. Twice now I've had it not disarm after entering the code on one keypad, and this mornign was the first time I've seen it affect multiple keypads.
-Jeremy
