Hello
After latest update(124), HSM is not synchronizing with my Xfinity keypad, if I set HSM to arm home in Sharptools it will not change the status on the keypad and then you can't disarm HSM on the keypad. If I arm home or disarm directly on the keypad works fine.
Tagging @bravenel @chuck.schwer
Thanks.
Edit, I restored 122 and works fine. Was a new option added to 124?
Is HSM status correct and following what is set in sharptools?
Yes, it was. In some point the keypad was disarmed (green) and beeping like when I arm away for the exit delay but HSM was disarmed too. Very odd.
I can install 124 again to do more test if you want.
124 contained a fix for the new delay options not being applied to the keypads, they would receive and use the arm away delay vs the others.
Let me install 124 again a re test.
Hey Mike,
I just put back 124, I noticed Sharptools is not activating arm home, arm away is fine, but this is the odd thing, to activate arm home inside HSM app I must click arm home button twice. If I click it once it will do nothing, I know I clicked the button once because the page refreshed but nothing was done until I click it a second time and the page refreshes again with the change.
interesting, I'm not seeing the double click arm home issue in HSM, what browser?
Chrome on Android Pie, Chrome and Edge for Win 10 x64.
You are using a Mac I bet, let me try with mine too.
Same on Safari
never (not a fan)... Chrome on win 10
Lol, try clicking arm home, then disarm armed home, then arm home. I see the first try worked but not any other try.
I use my mac with win 10, I just rebooted in macOS
I can give you remote access if you like. I'm at home, but please do not activate arm away 
thanks, too early for that, I'm just collecting "features" at this point...
Ok, thanks
Mike, I found something. I believe is something with the delay armed home by this many seconds setting, I had nothing but adding 10 seconds now works fine in any browser and in Sharptools, no double click needed in the browser.
ok, so it's an issue when this option doesn't contain a value...
noted
There is an additional bug in the HSM sequence... I can reproduce it upon demand.
Hub Platform: 2.0.7.124
Keypad: Iris V2
HSM Settings:
Assuming a DISARMED state...
Device Keypad shows state of * entryDelay : 0
Click the PARTIAL button (Arm Home)
Device Keypad shows Current State Variable of LAST USED value (for the time consider this an unknown)
Countdown/beeps commences, correct HSM state & Keypad button displayed
Disarm
Click the ON button (Arm Away)
Device Keypad shows Current State Variable of * entryDelay : 15 [Notice: This is Armed Home value!!]
Countdown/beeps commences, correct HSM state & Keypad button displayed
Disarm
Click the PARTIAL button (Arm Home)
Device Keypad shows Current State Variable of * entryDelay : 30 [Notice: This is Armed Away value!!]
Countdown/beeps commences, correct HSM state & Keypad button displayed
Disarm
In essence what is happening is that whichever button on the keypad is pressed for an arming event after a disarm, the DELAY of the PREVIOUS arming event is used. Of course, should the same arming event be executed twice in succession, the 2nd arming event will use the correct delay value. If you use the same delay for both arming events you will never notice it.
Hope this makes sense, and as mentioned, it is reproducible upon demand.
Update 1 : When arming, both Away & Home from the Hubitat web interface, the correct delays are used all the time. Interestingly though, when doing an Arm Away, there is a line in red displayed showing the delay value. There is NO such display when doing the Arm Home.
Update 2: The Sharptools web interface is also behaving properly re delays when using it to arm.
Thanks
J
This is a known issue with the release of the additional arm delay settings, this will not be fixed until the release of 2.0.8.
For now if you intend to arm from keypads,( and what's the point of having them if you dont), then all three delay settings need to be the same value.
Thanks Mike.
Download the Hubitat app
