The title pretty much says it. I have noticed since switching to ZwaveJS my Ring Keypad G2 device is not really working.
It responds to HSM when i set the alarm but can not be used to manage it. I have tried both a community driver as well as the built in driver and both seem to act the same.
@bobbyD and @bcopeland do we have a updated of Ring Keypad G2 drivers to fix the issue with them working?
Probably the same issue that I reported during beta with the Ring Gen 1 Keypad.
@bcopeland Hopefully both drivers will get some much needed "TLC" soon.
@bcopeland I was going to try and update the community driver but looking in the docs the entry control command class is not in there. Z-Wave Classes | Hubitat Documentation
Can we get the info on it please?
Or maybe @bertabcd1234 can update the docs?
Entry Control Command Class
COMMAND_CLASS_ENTRY_CONTROL
0x6F
Check now. 
After waiting and my CPU fan sounding like its going to blast off, the page has loaded and yes it is there now. Thanks! Now the work can begin later today hopefully.
That page is a beast, it almost needs to be split up into sections or something.
Here it is: Hubitat-by-Mavrrick/Ring/rkg2_driver.groovy at rkg2_update · jtp10181/Hubitat-by-Mavrrick · GitHub
I got rid of the manual parsing for entry control. It may work correctly...
There is still something going on with a motion event being manually parsed, I will look at that next along with whatever feedback I get here.
@Brandon is there a preferred community Gen1 driver I could update?
Currently not. @bcopeland made the ring Version 2 Keypad available for another Community Developer, but at this time the Ring Gen 1 Keypad is a Hubitat built in driver.
Same link as above: Hubitat-by-Mavrrick/Ring/rkg2_driver.groovy at rkg2_update · jtp10181/Hubitat-by-Mavrrick · GitHub
Further fixes and also hopefully fixed the motion events for firmware >= 1.18 (needs testing).
You may get errors in the log, reported here: [2.4.1.157] ZWJS Indicator command class parse error with {status=2} . Nothing I can do about it, it is a bug in the built in parse function. Device should work fine despite the error.
I know it has been a while, but wanted to post that this update has made the driver functional. I have been using ut since you published the last update and it has worked well.
Agreed, this driver seems functional. My issues seem to revolve around the Ring Keypad hardware and firmware versions. I'll create a new post to describe my current dilemma (unable to include or exclude device due to SmartStart bug). Link to post Ring Keypad Stuck in limbo due to SmartStart ghost
Note one minor driver error is that the siren volume level ('volSiren') is suppose to be within the range of 0->10 but is instead shown as 75. Works fine if left alone, but trying to change it fails.
I also enabled 'validCode' assignment, which is commented out in your version. Not sure if it helped resolve my code validation issue since the workaround was to set CodeName identical to the PIN code number. Not very secure, but it works for a while at least, until it doesn't.
Thanks @jtp10181 for the update since it's more feature rich than the default.
Try it now. I fixed the motion parsing which resulted in that debug log being attempted, and also fixed the debug logging lines.
Hubitat-by-Mavrrick/Ring/rkg2_driver.groovy at rkg2_update · jtp10181/Hubitat-by-Mavrrick · GitHub
That one appears to be a platform bug, it was mentioned up above.
So the motion events are working now for you?
I am using the https://raw.githubusercontent.com/jtp10181/Hubitat-by-Mavrrick/refs/heads/rkg2_update/Ring/rkg2_driver.groovy driver and although I'm not using ZwaveJS I came her to find out why my keypads stopped working (using the 3 year old version of the driver). Anyway, in that version I had to disable the proximity sensor or the keypad would "crash" (not respond to anything until reset). In this version I re-enabled the proximity sensor and everything seems to be working. The older driver worked fine (no sensor) but I presume platform updates caused my rules for the fire/medical/police triggers to stop working. This version fixes all of that.
By the way, can we add the import URL in the metadata string so it will be easier to update?
Thank you!!
Once everything seems to be working good on my version I was planning to do a PR and merge it back into @mavrrick58 's repo. I could add the import url for his repo right before merging it.
yes motion appears to be working correctly now. Thanks for the help!
I was playing around with this driver on mine. Somehow the proximity sensor got enabled. It works ok, but I want to disable that function. I turned on the disable, but it never disables it.
Sounds good. I will make sure I merge it as soon as you put in the PR.
With debug logging on, if you save prefs you should get a log message "Turning the Proximity Sensor OFF". It is setting parameter 15 to value of 0 when you see that.
You can use the Basic Zwave tool to query Param 15 to verify it is set to 0
You can also use the "Device" driver and click Get Info, which will send the fingerprint to the logs. Verify it matches the one this driver was made for: fingerprint mfr:"0346", prod:"0101", deviceId:"0301" . Post it if different, because the settings may not be the same.
Download the Hubitat app
