I do have delay set but the keypad doesn’t seem to sound the beeps. It only says away and armed after the exit delay timeout… is the keypad faulty? I purchased it from ebay but was brand new in packaging
I’ve had the same issue, it worked perfectly for a year, but after the latest
Z-Wave JS Update 0.20.0 update, it’s broken, i restored the update to 0.16.0 again and its working again.
Error while executing automation automation.ring_keypad_v2: Node(node_id=2) - NotFoundError: Value 2-135-0-18-7 not found on node Node(node_id=2)
Thanks very much to @jsnallen on Github for finding the issue: ZWaveJS changed the way they handle the Indicator CC in version 15.10, which broke the entry/exit delay. You should be able to re-install this blueprint to get the correct behavior back.
Anyone else having this issue with when using Blueprint where the Ring Keypad v2 (4AK1SZ) seems to disconnection or lose connection often unless you manually disable the motion sensor (the proximity sensor that is buit-into these Ring keypads)?
“There seems to be some mixup between hexadecimal and decimal in the automations. The gist correctly mentions that property 10 (hex 0x0a ) is armed stay, but the automation sends 16 (hex 0x10 ). Not sure if the automation converts strings to hex somehow? The property key sent to zwave-js should be the number 10.”
He also mentioned that “This should probably use a property_key of 2 (binary/boolean value) instead.”
Has anyone found a other workaroud ofr this other than just disabling the motion sensor?
These days, it should be exposed as an entity on the device. Go to Settings > Devices & services > Z-Wave, and pick the device for your keypad. Under the configuration pane on the device page there should be an entity labelled “Announcement Audio Volume” (it may be cut off). It’ll be named internally something like number.ring_keypad_announcement_audio_volume. Adjusting that should change the volume: 0 for mute, 7 for the default volume, up to 10 for the max volume. Sorry, it doesn’t go to 11.
Let me know if that doesn’t work - it’s possible that I’ve screwed up something in the blueprint to override the default volume. I don’t think I did, but it’s been a while since I read that part of the code.
It should beep angrily when the alarm is triggered, yes. It’s possible that got broken with the Z-Wave JS update as well. I’m sorry, I’m on vacation but I’ll test when I get home in a week and a half.