I’ve not noticed this either with my Conexis L1
I catch any unmapped event to a Unknown value, which I don’t see on my lock.
Maybe your lock works slightly differently than ours?
Apologies to reach out direct — finally took the leap to Z-Wave JS this morning and all seems well, except for updating the status of the lock using RFID. Everything else seems to update it, just not RFID (no event fired).
Is this the same issue you were seeing? I’ve took the plunge straight into 7.9.0.
(Also — I never see any changes on Alarm Type; it’s always “1”. Worth noting, this is the first generation Z-Wave module…)
Hi Jamie,
I remember using the original z-Wave module and experience similar problems, you will need to upgrade to the newer module (blue) to enable secure events.
Once your Lock is reinstalled using the secure add device, things should show up. GL!
Thanks — I’ll take a look if they’re still not a fortune for the module 
Just reverted back to a previous snapshot for the deprecated version and it’s the same behaviour. How did I not notice the RFID tags didn’t update status for lock/unlock in 3 years… 
So after discovering that the first generation module doesn’t fire unlock events for RFID tags — it clawed away at me, and I ended up picking up two (front/back door) 2nd generation modules and swapping them out. Had to wipe my network, but luckily, this consists of just these locks…
Also witnessing the missing code “25” for Z-Wave unlock, but there is a workaround.
It seems that the alarmLevel and alarmType values are not updated on RF Unlock, whereas they are for everything else. That said, they are issued as events. Unfortunately, Home Assistant doesn’t natively expose these (they don’t come through as any zwave_js prefixed events), but are available on the zwave/_EVENTS/ZWAVE_GATEWAY-zwave/node/node_value_updated topic if using zwavejs2mqtt.
This can be filtered into a trigger template sensor to custom write the alarm_level and alarm_type sensors accordingly. 
If you create a Bug Report at the node-zwave-js project, they should be able to update the device configuration to map the alarm values into proper notifications. After that, HA would trigger zwave_js_notification events. Until then, there should be two disabled sensor entities for alarm_level and alarm_type, which would do the same thing as the template sensor.
I believe they already are — you can get zwave_js_notification events for all methods of lock/unlock, apart from RF unlock. The same is said if you follow the values output on MQTT or in the zwavejs2mqtt web ui; the alarmLevel / alarmType values do not update (hence the custom template-driven sensors).
Sorry, I’m not clear on everything. Let me ask a few more questions if you don’t mind? For this case there shouldn’t be any reason to need MQTT. That’s the part I’m trying to understand (maybe there’s a bug somewhere we can fix).
Are you saying that you have already enabled the alarm_level and alarm_type sensors in HA, and they are not updating? What do you mean by “the alarmLevel / alarmType values do not update”. Are those the values in shown in the zwavejs2mqtt UI, or in HA?
What exactly is the functionality of your MQTT template? If it is watching for alarm_level/type, my suggestion was to submit a bug report for this alarm value if it isn’t translated into a notification. Maybe that was missed for your model of lock. If it’s an RF unlock, it can be mapped to the real RF Unlock notification.
The “value updated” event from node-zwave-js is what both the zwave_js integration and zwavejs2mqtt listen for. In the case of the former, it translates to entity states, and for the latter it is displayed as a value in the control panel, or used in an MQTT sensor topic. It doesn’t make any sense that the event topic you’re watching would show the events, but nothing else does. There’s something off there.
Yeah… ignore me…
On further inspection, this too doesn’t fire all the time. There is definitely some intermittent confirmation of “Unlocked by RF” from the Conexis with the 2nd generation model.
Just got too keen thinking that I’d found a workaround 
Hey
I’ve queried this before when I switched to the new zwavejs I noticed it wouldn’t pick up if the same RF tag kept unlocking the door.
So I switched back
On the deprecated zwave I get a notification everytime the door is unlocked from any RF tag regardless if it’s the same one over and over again.
This is using the gen 2 module.
Been reading this thread and having issues getting the z-wave module to pick up home assist correctly. For some reason its coming back with undefined node, and when testing its coming back with unknown device.
I’ve not got other z-wave devices in the house and this is the first device in my network.
I’m using the Aeotec USB Z wave and I followed the online video how to add it.
I think I’ve done it correctly and generated private key and scanned my network its not coming back with device info.
Im pushing the R button on the lock 3 times as instructed but I’m not sure its working or ‘paired up’ but as you can see on my device list on the Web-UI of Z-Wave to MQTT it sees something. When I look into the entities it gives me some resemblance of ‘locks’ and etc so its not like there are other unknown Z-wave devices my house.
I’ve tried to uninstall the integration and reinstall but not sure what else to do to troubleshoot it.
Any ideas?
EDIT: I’ve moved the Pi and the USB dongle into the hallway so its got a clear line of sight to see the device.
Have you tried using secure inclusion in Z-Wave JS/zwavejs2mqtt? From the screenshot you provided it looks like it wasn’t included in secure mode.
Are reading and doing more research I think its down to my network key which is not being transferred or used when communicating to the yale module z wave. I’m still learning and try to find out if or what I’m doing is correct. I have tried to search for device in secure mode but it doesn’t pick up any changes.
I can’t have a faulty module as this was brand new from Amazon. Its just a bit annoying I dont have other z-wave devices to check against.
Anyone know any good videos I can reference to make sure I’ve set up the usb z-wave correctly?
You need to generate a network key. You can click on the “settings” tab in ZWaveJS2MQTT and under “Zwave > Network Key” you can auto-generate a Network Key by clicking on the “refresh” icon. Restart your ZWaveJS2MQTT add-on, and try adding your lock with secure inclusion again.
I’ve tried uninstalling and installing the ZWaveJS2MQTT several times and must have generated several keys but not sure if any of them are sticking.
I’ve tried adding the lock with secure inclusion, push the R button 3 times quickly and it finds no changes or picks up no changes.
I’ve tried to follow the instructions directly such as disconnect the batteries, put the module in, put the batteries in and straight away push the R button 3 times within (1,5 secs) the lock makes the noise but ZWaveJS2MQTT says no new changes picked up.
Sorry I haven’t been of much help - just to check, have you tried excluding the lock first, before trying secure inclusion again?
In any event, since you asked for a video to reference, you can take a look at Walk through of zwavejs2mqtt along with Z-Wave JS in Home Assistant - YouTube
You are helpful, your helping me troubleshoot what we can and cannot do. When you say excluding the lock? is that the same as removing it? If so then yeah I have tried to remove it on ‘exclusion’ mode, let it scan and push the r button 3 times but again no changes are made.
The only way I know to remove it, is to physically remove the module out of the door lock and scan it and it removes from the entries list…
I’m currently watching Chris’s video to see what else I can find out about triaging it. I have a feeling its that ‘secure inclusion’ which seems to fail to communicate to the z-wave.
Yes, when I say “excluding” I mean removing the device on “exclusion” mode.
It does appear that your issue is with “secure inclusion”. How far is your Aeotec Z-Stick from the lock? In secure inclusion mode, the Yale zwave module has a decreased range for security purposes. You may need to move your entire Home Assistant device (whether it’s an RPi or PC) closer to the lock. Unfortunately, you can’t remove the Z-Stick and use the manual push button inclusion method for secure inclusion (see here: Z-Stick Gen5 and security (S0 and S2 Framework) : Aeotec Help Desk)
If you run zwavejsmqtt on a separate raspberry pi, you can move it around to the locks to pair them, though the documentation explicitly says not to do that.
One thing I have found works is that the zwave modules in the yale locks are interchangeable. I have one lock that is very close to the Zwave stick, and I can swap modules from more distant locks for the pairing process, and then put them back in their final configuration and reinterview them so the parameters are set properly.
If you do this a lot it may be worth getting a broken yale lock off ebay that is compatible with the modules you use, and keep it as a dummy to power up the module near the zwave stick.
As an aside, I have concluded that zwave is a PITA, and it’s far better to use zigbee if possible. zigbee lock support isn’t quite as good yet, but getting there, and Yale does make zigbee lock modules as well.
So much easier to do pairing and none of this BS about needing to be close to the lock to pair.
I joined a livestream with Chris @ Mostlychris and managed to get my question in about asking for some help, he gave me some information and I managed to get it all working.
I don’t know what exactly that made it work but one hint he advised like @Eoura and @fresnoboy mentioned, I moved my Pi4 and the USB Z-Wave stick like 2 feet from the door lock. Did local reset on the door as I think it might had hold my previous network key but did a combination of removing the node and reset and it eventually worked.
I think it was the distance thing that got it talking to each other securely.
Thanks to @Eoura for the advise today, thank you.
1 Like