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.
Download the Hubitat app
