Hi Kai,
That’s unfortunate, but judging on the information you provide it looks like a communication problem as both devices show the same behaviour. These devices communicate with you Homey over z-wave so I suggest you look into that. The app only commes into play after signals are released over z-wave and passed through to the app, Homey handles all communication.
A starting point can be the Developer Tools where you can look into (some) z-wave information: Homey Developer Tools
I have now deleted the unknown nodes in the developer tools and performed a Z-Wave reset. Subsequently, I re-added the Ring Keypad. It is now displayed as working, and a test also runs through successfully. But doesn´t work…
EDIT : I think, i found the Problem… I connect one of the Keypads to my other Homey Pro (early 2023). And here it works… So it looks like the Homey Pro 2019 is causing the problems…
I have the exact same problem as @Kai102. My Ring Keypad V2 stopped working about a week ago. Whenever I press any key on the Ring Keypad the red wireless signal indicator turns on. But if I change the alarm state via the homey app, the Ring Keypad notifies that. I have removed the Keypad from Home and reinstalled it, and re-added it to Heimdall with no effect. I’m hoping that more information can help. I will also check the Dev Tools.
EDIT: Just re-read Kai’s reply. Will look into that. Running on a pre 2019 model.
oh, okay, and I thought it was a hardware problem with the “old” Homey, but based on @NiclasSwe report it could be more of a software problem. Have there been any updates during that time?
There was an update for the Homey device (not sure when it was published) that I just installed. It didn’t solve the issue…
It’s the same here: V2 keypad suddenly no longer working (only receiving messages, not sending). Also, it has been working properly for a long time, and all of a sudden it is giving the red LED. And it is for both the keypads we have! Any clues whatsoever?
Here too: running on a 2019 version of the Homey. That seems to be a hint. Has there been a software update of the Homey that killed this on older hardware? According to the Ring Security page the app itself did not change for a year.
@DaneedeKruyff Any dependencies with the Homey OS that could result in such behavior?
There have been updates to Z-Wave, the communication protocol the Ring Security devices use under the hood, and seeing the approximate release date of 13.2.0 and the reports here about the connection issues I suspect it’s related.
Everybody having issues; please report them at Athom
https://support.homey.app/hc/en-us/articles/360015784034-Submit-a-support-request
Done! Hope this helps.
Athom has replied to my report swiftly, and after some back and forth communication there is no solution yet, but their response seems promising: “I just received word from our development team that they are working on a possible fix. This may take some time, but they have possible culprit they are investigating now.” I’ll keep you all posted.
Great!
Thanks for reporting back!
Even better, although no solution yet, today I received the following message: “I have learned today that, even though this is a community app, we are ordering the RIng Keypad ourselves to test this issue with. It should arrive soon. This means it may still take some time to find and test the issue and possible solution, but as you can see, it has our full attention.”
It should be fixed in v13.2.2-rc1. You need to enable Experimental Updates in the developer tools.
I can confirm that the keypad v2 works again with 13.2.2-rc.1.
