Correct, works almost perfect!
Thank you,
When you say it works almost perfectly what doesn’t work? For anyone else reading this is it more beneficial to use Z-Wave MQTT? I switched over to Zigbee2MQTT last year and have been thinking about switching my Z-Wave as well. The only thing that makes me a little nervous is that I have 3 Schlage Z-Wave Plus locks setup and running the excellent Keymaster add on. Would I have to reconfigure my Z-Wave devices?
I have to disable the built in motion sensor in the Ring keypad (for the keys to light up when you are near) because otherwise I sometimes get disconnections between keypad and zwave USB stick. My 2 keypads are installed in well lit rooms, so I don’t need it anyway… Very happy with it!
1 Like
This is OT here, but Zigbee2MQTT and Z-Wave JS UI (formerly Z-WaveJS2MQTT) have got nothing in common other than the (former) name. MQTT is strictly optional with Z-Wave JS UI and the only difference from the Z-Wave JS add-on with regard to HA is that there’s an additional management UI. Both add-ons use the Z-Wave JS integration.
I’m having issues pairing the keypad with the zwave stick. Can anyone guide me through how to do it?
I put together some tips here: Using the Ring Alarm Keypad with Home Assistant - #156 by ImSorryButWho . Luckily, things are a lot easier now that Smart Start works.
Thanks for making the blueprint! I get a “No matching devices found“ error when trying to select the Keypad Device.
Any ideas why?
The keypad is paired using Zwave JS UI, I believe formerly known as Zwave2MQTT.
I have confirmed that HA is receiving messages from the keypad.
Any tips most appreciated!
It shows Ring
Keypad v2 (4AK1SZ)
by Ring
Firmware: 1.18.0
Is this screen shot from Zwave JS or Zwave JS UI?
It makes no difference from the HA side. The blueprint is just looking for a device with a manufacturer of Ring, so… I’m a bit stumped as to what might be going wrong.
Perhaps the manufacturer info is not passed through to the core mosquitto Mqtt broker?
Oh, you’re using MQTT? Yeah, that’s untested and probably the problem. ZWaveJS UI (nee ZwaveJS2MQTT) fully supports the normal Home Assistant websocket integration method, and I’d strongly suggest going that way. AFAIK you can still use the MQTT connection as well if you want to integrate with something third party, but going direct to HA is the expected and supported configuration.
Thanks a lot. Will reconfigure. I have a satellite raspberry PI with ZWaveJS UI in a separate house and wanted to collect all devices through MQTT for convenience.
Anyone else getting this warning recently?
## Ring Keypad Automations uses an unknown service
The automation "Ring Keypad Automations" (`automation.ring_keypad_automations`) has an action that calls an unknown service: `zwave_js.set_value`.
No, it’s working normally for me on 2023.4.6. Did the ZwaveJS integration get disabled or removed from your system?
This one?
Z-Wave JS UI
Current version: 1.11.2
That’s the add-on. Remember that you need both an add-on (ZwaveJS UI or ZwaveJS Server), which talks to the hardware, and the ZwaveJS integration which is configured on the Integrations page and is responsible for actually creating the device entries and services in Home Assistant. It sounds like you’re missing the latter.
That’ll be my problem then 
Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Name does not resolve]