Okay, that’s too bad if that’s the case 
haven’t got any issues with my other z-wave devices and a bit unsure how to proceed with the troubleshooting.
I have however ordered a keypad v1, so I will give that a try just to see if it’s a problem with the v2.
Thanks
I’ll try this tomorrow and report back 
I am having the same problem as Johan. I got the ring keypad to work a few times but then i stops working. I have tried restarting both apps and homey.
I am having the same problem as Johan. I got the ring keypad to work a few times but then i stops working. I have tried restarting both apps and homey
Hi Klaus,
I’m afraid I can not help you with this. Homey takes care of the Z-Wave communication, that part is totally outside the control of any app. Only after the app receives information from Homey the app can do something.
Every time I add the keypad it reacts quickly on arm/disarm from the app for a long period, but as soon as I enter a code on the keypad it stops losses the connection to the homey.
Ok, so let’s focus on sending of a code.
You say it stops working, does it also start working again after a while?
I’d like to receive a Diagnostics Report:
Can you stop and start the app, wait a few seconds, enter a pin and press the Armed (or Armed Away) key. Next wait some 30 seconds and send a Diagnostics Report from the app.
I have used 6 characters. Now I have changed it to only 4 characters and now it works 
That’s good news!
It does surprise me a bit because I’m also always using 6 digits, but I’m not complaining 
Well maybe I was to quick. Now it is locked again. I entered something wrong. I will experiment a little bit more
Just wanted to update you on my situation.
I received the keypad v1 and that’s working without any issues. So it’s weird it’s only with the v2 version that I get this issues
I have removed all Z-wave devices. Reset Homeys Z-wave network. Uninstalled Heimdal and Ring app. Check in developer that all Z-wave devices is removed. Re-installed heimdal and Ring and only installed ring keypad V2 as the only Z-wave device. Added a user with 4 character code in heimdal.
When I change the surveillance state in homey the keypad also Annonce the state change.
When I enter a user code on keypad it goes into a lock-state and does not response any more. It does not change state on the keypad and it stops reacting on the change state from surveillance device/homey.
If I press shortly on the reset switch on the back of keypad, the keypad again reacts on change state from surveillance device/homey. But if I enter a correct code it stops reacting again.
After some time (1-2 hours) it starts reacting on changing states from surveillance device/homey again.
The firmware version in the keypad is 2.
I still have Zigbee devices and Philips Hue connected and Apple HomeKit.
Can you stop and start the Ring Security app and after a little wait enter a code to arm. Next send a diagnostics report from the app and let me know the number.
Btw, what is the exact firmware version, including the sub version number. (I haven’t seen 2.x before)
4c5be3e8-ced7-4a1c-bb40-1ae91b43312d
I also notice different behavior from the keypad. Sometimes when I approach the keypad all keys light up white - including arm/disarm. Other times it shows the state when I approach the keypad.
I will have look at it.
The behaviour what happens when you approach the keypad is all internally in the Keypad, I’m beginning to wonder if the keypad itself isn’t at fault (or this new firmware)
I tried to disable the proximity feature and I think that has remove my problem. It seems to be working now where I use 4 characters code. I will continue to test and keep you posted. Thanks for the patient support.
Try to disable the proximity sensor feature. It seems to have solved the problem for me on V2 keypad.
Keypad V2 still working after two days with disabling the proximity sensor disabled.
That’s great! Thanks for letting us know.
New version published
Version: 0.2.10 Beta
- Set Use Proximity Detection default to No for Ring Keypad V2
Several users have reported that setting Use Proximity Detection to No solves their problem of the Ring Keypad V2 freezing so from now on the default setting is No.
This new setting will only be applied when adding the Ring Keypad V2. Current users of the device should change this setting themselves when experiencing these freezes. In a future version this setting may be forced to No for all users and the ability to change it will be removed.
