So, I’ve already got an alarm system set up in HA using Alarmo, with sensors provided by a Konnected module reading the sensors from the old alarm system that was in our house when we bought it.
There was no easy way to convert the old alarm keypad to work with HA, so I wall-mounted a Kindle Fire tablet. But it’s pretty flaky - crashes occasionally, and often doesn’t register touch inputs properly, which is bad when someone’s trying to disarm the alarm.
My goal is just to replace it with something that looks and acts more like a normal alarm keypad, and boost the WAF. This seems like the cleanest solution I’ve found so far.
Been trying the blueprint, the keypad will pick-up the state when set from HA-Alarmo, but will not work the other way. For example, when arming from the keypad, does not transfer to HA-Alarmo. Any ideas? Trouble shooting?
Interesting. What behavior do you see when you hit the Arm Home button, for example? If you look at the automation trace, did it run? If so, which path did it take?
@ImSorryButWho Turns out had to exclude then re-add the keypad for some reason. What is not happening, however (using blueprint) is any signals, voice, or change to the Ring keypad when setting alarm either at the keypad or within HA. The state is definitely changing when arming from the keypad, however no countdown, no lighting of state on the keypad etc. Figure may be an issue with zwave_js.set_value?
Here is the error on Trace: Indeed seems unable to set the value on the keypad…
Stopped because an error was encountered at November 21, 2021, 9:19:39 AM (runtime: 0.43 seconds)
Value 43-135-0-2-1 not found on node Node(node_id=43)
That means that ZWaveJS doesn’t think the keypad has the Indicator command class. Try re-interviewing the node (under the advanced button in the ZwaveJS2MQTT UI), and watching the debug log for errors.
Interviewing a node can be pretty bandwidth intensive, so it might help to move it closer to your controller when you interview it, then run a heal when it’s working and you’ve put it back in it’s normal spot.
Try bringing the keypad close to the controller when you’re doing the interview. This device has the longest interview of any ZWave device I’ve ever used, and it sounds like you’re dropping some packets. A better signal from proximity might help.
The rest hole is on the back, just below the channel for the power cord, on the same side as the label.
Apparently, a newer firmware version does expose it. Presumably the official ring base station knows how to download a new firmware image, but I don’t have one to test with. They don’t seem to make it freely available, and I haven’t tried asking their tech support. I tend to doubt that they’d just send it over, but it might be worth a try if it’s a feature that you want.
