Mode change sent to keypad multiple times

[arnb]

Using 2.08 and Iris V2 Keypad Device as a virtual.

I've noticed when changing the mode or armstate from a dashboard the 'disarmed' command is sent 3 times, armedNight sent 2 times. Have not tested armHome or armAway.

Is this working as designed?
It likely won't do any harm, but does add substantial system overhead.

Device log follows for disarm.
tagging @mike.maxwell

dev:1952019-03-31 15:39:43.389 infoVirtual Iris Keypad was disarmed [digital]

dev:1952019-03-31 15:39:43.193 tracesendArmResponse- sucess, bin:1, armMode:00 -> armRequest:00, exitDelay:0, isInitiator:false, lcData:[isValid:true, isInitiator:false, code:0000, name:not required, codeNumber:-1]

dev:1952019-03-31 15:39:43.136 infoVirtual Iris Keypad was disarmed [digital]

dev:1952019-03-31 15:39:42.942 tracesendArmResponse- sucess, bin:1, armMode:00 -> armRequest:00, exitDelay:0, isInitiator:false, lcData:[isValid:true, isInitiator:false, code:0000, name:not required, codeNumber:-1]

dev:1952019-03-31 15:39:42.897 infoVirtual Iris Keypad was disarmed [digital]

dev:1952019-03-31 15:39:42.697 tracesendArmResponse- sucess, bin:1, armMode:01 -> armRequest:00, exitDelay:0, isInitiator:false, lcData:[isValid:true, isInitiator:false, code:0000, name:not required, codeNumber:-1]

[njanda]

There are issues mentioned at the bottom of the release notes of the 2.0.9 update relating to arming / disarming v2 keypads. Pretty sure 2.08 had the same.

[arnb]

I just updated to 2.08.109 today. No mention of 2.09 on the settings page.

I'm aware there are some keypad operation issues in 2.08, but it does not mention excessive overhead. That is why I'm bringing this to the developers attention.

[Ryan780]

There's 3 or 4 threads going about the different issues with the Iris keypads presently.

Iris v2 keypad

I can not get keypad to arm/disarm. Under keypad device page I can press button to arm, the keypad will beep and show on, the current states “security keypad” in device page says armed but hsm will state disarmed. Same happens if I use the keypad, using pin to arm or disarm 1. I have removed and re-paired. 2 I have keypad set up as a siren for intrusions and it works. 3 I do have keypad selected to arm and disarm. 4 I have arm-away when mode becomes away, arm- night when mode become…

Iris Keypad v3

Anyone else get the Iris Keypad v3 to work with HSM? I am getting the strangest behavior. First of all, there is no Exit Delay notification when you "arm away" from something else, like a dashboard, unlike the V2. And that is the primary reason that I bought it. In addition, when you arm-away from this keypad, you do not get the delayed armed action from HSM or an exit delay beep from the keypad. Instead, the keypad does it's own, silent, 30 second countdown and then HSM immediately goes to A…

[Solved] Can't arm away after hotfix 2.0.8.109

Just installed the hotfix 109 and all of a sudden arm away is gone. I removed my keypads and re-added them to set the option for partial but now Away is gone. [image] I can arm away from a keypad or from a dashboard. Just not from HSM itself.

Iris v2 Keypad w/ 2.0.7, 2.0.8, 2.0.9 or 2.1.0 - No Tones after Arming

Hi there, I decided to try 2.0.7.126 again after having issues with my keypads, etc., and rolling back, now that I have a little more time to troubleshoot. I have my keypads working again to arm/disarm with code. However, I am running into a weird issue with the volume on the keypads themselves. If I hit "partial" to armHome, the keypad flashes and goes to partial. However, I didn't hear the normal arming tones. However, I DO hear the quick beep sequence on the other keypad. Now, if I star…

If you're trying to get their attention, tag mike.maxwell. He's been the one leading work on the keypad issues.