I'm still going through testing for my driver. I got some feature feedback from my family and I did the following to the driver :
- fixed the double delay
- I also added a fix to disregard when HSM rapid fires multiple of the same command (ie. disarm, armedAway, etc) at the keypad (I messaged Hubitat about this already), but adding a timed blocker after the 1st.
- added ability to enter exit delay for partial/away modes while still in partial states. This makes it so you don't have to disarm first
- Adds chime capability (so you can not only play them, but call the keypad as a chime in rules)
- made proximity sensor disabled by default & ran that on install
- edited how the volumes are added (more intuitive & stops out-of-range inputs)
- fixed an issue that didn't allow armedNight to work properly
- made the keypad driven by HSM instead of driving its own state upon key presses
- added functionality to re-sync with HSM in the case of malfunction
- fixed an issue with disarmAll, enabling it even if HSM isn't set for it
- removed commands that shouldn't be used
- commented out code that isn't used
- stopped auto-off for Debug Logging
My own criteria is no issues reported between myself and my 2 family members (3 units) being used every day for at least 2-3 weeks before posting it online. I just made edits to it today, so it'll be at least a few weeks until "release".
If you want a preview of the Driver Code, I can send it to you in a message! The more input I get, the better it can be.
For what it's worth, I've done quite a bit of digging to figure out :
- how HSM & Keypad drivers talk
** I made the following thread : HSM and Custom Keypad Device Drivers -Developers - Hubitat
- The technical specifications of Z-Wave :
** download link : https://sdomembers.z-wavealliance.org/document/dl/917 - The technical details of the Ring Keypad itself :
** products.z-wavealliance.org/products/3870