Thank you - another new thing I learn today!
I've just upgraded to 2.2.5.124 and Ring Keypad gen 1 is still having issues.
I can now use the keypad to disarm if the state was originally set to "Armed Away" or "Armed Home" using HSM.
However, I can't use the keypad to arm (either away or home). Looking at the logs,
When I try to set the exitDelay/entryDelay to any number through the device settings, I get the following errors
I'm guessing if I could manage to set the exitDelay/entryDelay, the problem will be solved. Am I missing something?
Seems that my problem with the Ring keypad G2 is similar to what I am experiencing: Ring G2 Keypad - Cannot Set property
I have my Ring Keypad G2 setup in HSM.
Keypad is registered with HSM and works ok with 2.2.4 (all interactions between keypad and HSM were ok apart from "arm home")
Under 2.2.5 I can use keypad to disarm but not to arm.
These are the steps I follow to reproduce the issue:
In HSM I have set all delays to 5s.
First I use the dashboard to arm away. After 5s, both dashboard and keypad (light+audio) show "armed away".
Then I use the keypad to disarm. Success! Both dashboard and keypad (light+audio) show "disarmed".
Now I attempt to arm away using the keypad. Nothing happens.
I attach the log below
(Maybe I was getting the same errors in log with 2.2.4 but at least keypad was arming/disarming ok. If needed, I could downgrade and get the new logs for the same operation)
It seems to me that the process fails because it can't get a valid "exitDelay" value and unfortunately when I go to the device settings I can't set a numerical value using the "Set Entry/Exit Delay" function.
I see that the issue that affects Ring Keypad Gen 1 has been reported in the following thread too:
1 Like
Yes, I didn't see your post. When I searched the post with issue for 2nd gen came up, and I just replied to that.
I have rolled back to 2.2.4 until a fix for 1st gen have been released. I have no problems arming with 2.2.4.
For reference there must be something specific in your environment or specific config settings causing issues. I have a g1 keypad and it is functioning without issue.
Can someone having this issue on the current hub software please enable debug logging and try this action, as I am not able to reproduce this problem.
Ok.. Can you also screenshot the HSM config where you have the keypad programmed?
If I go to the ring keypad settings, am I supposed to be able to set a persistent numerical value for entry/exit if I press the buttons below?
Because at the moment I can't
I'm having the same problem with the Gen 1 Keypad on 2.2.5.124. I'll check my logs and see if they are the same as @christos
I am having the same problem with a Ring Keypad G2:
Setting the delay in the Ring Keypad device throws an error:
The value 10 won't save.
I have a C7 on 2.2.5.126.
Ok.. I see the issue here.. and why it is affecting some and not others..
This might be an easy fix.. Can someone getting the error post a screenshot of the "State Variables" section of the device page? For both G1 and G2
For G1:
1 Like
Ok.. Try this:
metadata {
definition (name: "Ring Keypad Fix", namespace: "hubitat", author: "Bryan Copeland") {
command "fixKeypad"
}
}
void fixKeypad() {
state.initialized=false
}
Drop this in driver code as a new driver.. Switch to "Ring Keypad Fix" and click "fixKeypad" button. Then switch back to the normal driver and click "configure".
Somewhere along the line either it didn't get setup all the way, or it lost a state.
This should fix G1 and G2
2 Likes
