Ring Keypad G2 with ZwaveJS not working

🛎️ Get Help Devices
1

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?

2

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.

2 Likes
4

@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

1 Like
5

Check now. :slight_smile:

6

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.

7

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?

1 Like
8

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.

9

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.

Please let me know if Working / Not working

2 Likes
10

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.

2 Likes
11

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.

12

I wish I could say the same...
My logs are full of errors. No one else is seeing this issue?

image
image1623×388 109 KB

13

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