So far, so good! Automations are fast inspite of me having a few apps and automations set up. One thing I particularly like is that HSM's arming and disarming can be separate from the hub's mode. With smartthings arming and disarming meant changing the hubs mode. The big difference is I can have mode changes based on time of day with hubitat and automations based on that irrespective of if I have armed the system with the keypad. I love that. I also love how rule machine makes it easy to have 1 rule that runs differently based on the different modes.
One observation though which I prefer from webcore is that when an automation has a timer and is triggered, the countdown is shown in webcore. So if a light is to turn off 3 minutes after motion stops, in webcore I can see the 3 minutes counting down beside the piston. It's handy especially when testing automations. I doubt many people would find that useful though.
All in all, I am very impressed with the system and when 2.0.6 fixes the keypad issue I have, it will basically be set it and forget it for me which I know the wife will love lol.
Yeah, I used to use that a lot in webcore. Closest to that now is to go into the rule, click the gear in the upper right, scroll to bottom and see when the next action is scheduled.
Updated to 2.0.6 and removed and reset the iris keypad and added it back. Still having the same issue where the lights stay on when arming and disarming.
It can't be, because it didn't do this with the smartthings device handler. It also stays on when disarming which also doesn't happen with ST device handler.
Please post a link to the driver you mention. I'm not saying there isn't a workaround software wise, but I've not found it yet, a newer version of the same v2 keypad does not do this.
Does this happen with the xfinity keypad? I'd rather not have to spend any money if it can be fixed but I also know in the grand scheme of things this isn't a massive deal and more important things are there to be done...
Sorry, but yes, it happens to the Xfinity centralite keypad, my wife leaves every morning the light in the keypad turned on after disarming stay mode. Waving the hand will turn on all the lights then all turn off.
Just because being an engineer can at times give us fat heads, I published the driver you posted to my ST account, fired up my hub, and my sniffer and attempted to join the device, the join never completed as far as the keypad was concerned, nor did ST ever present a default device, or any device for that matter.
It received its 16 bit address, and the transport key but never completed the IAS cluster sequence...
So I don't know how this keypad can work perfectly on ST since I was unable to even get it joined, much less test the functionality of the reference driver that was posted.
Unfortunately I've removed everything I can from ST and reset the hub (put it up for sale). Didn't mean any offense by posting the link, just wondered if doing things the way they specified allowed the device to join and work properly.
I'm curious why no manufacturer has tried to make a readily available and compatible zigbee or z-wave keypad as I think they would sell quite well on the various smart home systems.