I didn’t think about that my door is the only Z wave device I have. I’ll give it a try
What add-on/software are you using for your Z-Wave network?
I kept having an issue with my L1 lock which is my only Z-Wave component until I moved to the OpenZWave add-on - https://www.home-assistant.io/integrations/ozw
It has been really stable since I moved 
I created an automation that sends me a notification when the door is locked and unlocked to check everything was working fine and it has never falsely reported a lock or unlock
1 Like
Thank you that’s really good advice. I had to reinstall my lock as I noticed it was loose, since then I’ve not had the issue.
Thanks to everyone for all the help in this thread - I’ve been able to seamlessly get my Yale Keyless Connected wired up and talking to my network brilliantly!
I’ve been able to (just about) establish that .alarm_level appears to be the code used to unlock the door - 19 appears to be the master code, whilst 144 seems to be either the tag or the keycard (not yet worked out why this isn’t differentiating!)
HOWEVER! What I’d like to know is about configuration using the ZWave Management interface.
I’m seeing the below images - Slot 1& 2 have a user already in place (one is fob, one is keycard), and slot 6 is empty - I’m struggling to work out how to both a) Read what the code is? and b) Set a new code in each slot?
Any chance anyone was able to help out at all? Thanks!
Did you work out anymore on the codes meanings?
This is my first Z Wave device so its a bit new to me. I am also using the brand new Z Wave JS so unsure if all the info is coming in? I have 6 entities created in total
- Battery Level
- Current Lock Mode
- Alarm Level
- Alarm Type
- Low Battery Level
- Current Status of Door
AlarmType seems to return 6 different codes that I can stumble across;
144 - Opened by Card/Fob
16 - Opened by Bluetooth
22 - Opened by the knob
9 - Error locking
21 - Locked manually
27 - Locked automatically after being left open
I havent had a 19 code returned that I can see yet and cant work out what AlarmLevel is for, or how to identify who has unlocked the door?
Anyone have any pointers please
UPDATE: Sometimes when you write things out, they just become so obvious! The AlarmLevel corresponds to the fob/card that was used to unlock the door! Quite why its called an “AlarmLevel” i dont know!
Have a look here, it has my automation for the Yale lock
1 Like
Thank you so much. Thats exactly what I was looking for so saved me writing it up and also has some new error codes I wasnt aware of.
If that helps
0: "No Status Reported",
9: "Lock Jammed",
17: "Keypad Lock Jammed",
21: "Manual Lock",
22: "Manual Unlock",
23: "RF Lock Jammed",
24: "RF Lock",
25: "RF Unlock",
26: "Auto Lock Jammed",
27: "Auto Lock",
32: "All Codes Deleted",
161: "Bad Code Entered",
167: "Battery Low",
168: "Battery Critical",
169: "Battery Too Low To Operate Lock",
16: "Keypad Unlock",
18: "Keypad Lock",
19: "Keypad Unlock",
162: "Lock Code Attempt Outside of Schedule",
33: "Code Deleted",
112: "Code Changed",
113: "Duplicate Code",
3 Likes
Thank you for sharing.
1 Like
On the old ozw 1.4 the lock would take 6-7 seconds for the status to update when it was unlocked or locked remotely.
Now on zwavejs2mqtt on my first go it was instant but I had to replace the batteries now with new batteries it take 3-4 seconds for the status to update.
So weird and annoying it updates status instantly if you manually unlock by thumb knob.
Hi guys,
have any more people moved over to the new ZwaveJS how is it going, has there been any issue, are you seeing any improvement?
I moved to ZwaveJS and have had no issues with the Yale Conexis L1 with Zwave module
1 Like
Have you noticed any speed improvement?
No, not that I have noticed but it always was pretty instant response
1 Like
I created an automation to see who had unlocked the door by using Holdestmade’s code, but it doesn’t matter which tag I use to unlock the door with, it always comes up as AlarmType 21 - Manually Locked.
Any ideas why?
I am running the latest version of HA Core 2021.3.3, Supervisor 2021.3.4, HassOS 5.12 and Z-Wave JS to MQTT 0.6.2
Have you seen my post
I know who and when
Hey, are you able to tell which user unlocked the door. As my above post shows I use that a lot. Yet just moved over to Zwave us and can’t find it
Yes working fine now.
The entities didn’t appear for me at first but one day they just appeared !
Not sure if it was after an update or just a restart
They are named something else though and I think they were disabled
1 Like
I had issues the lock jammed, so I had to rebuild the lock and then I lost the Zwave connection.
I’ve reverted back to the old Zwave for now.
It currently reports the nfc tags like this “Unlocked by NFC Tag or Card by user 3”
Been lurking on this thread for a while.
I installed the lock about 3 weeks ago and the zwave module 2 weeks ago. Installed zwavejs-2-mqqt on a standalone Raspberry Pi so it is near the lock and thanks to all on here it is working quite well. Really happy with it.
I have noticed in 2 weeks (bear in mind to begin with I was using it a lot to test), the battery is reporting a 15% loss, does that sound right? I think it is ok, but just want to see others mileage.
I use Node Red for all my automations and have used the list from @lolouk44 for lock reason and it works a treat.
I can’t seem to get the tags working though by name - is this possible?
Thanks for all on here BTW - I was thinking about the lock for ages and you pushed me to it 
I do though still carry my back door key incase as I trust it 99.9%
One last question - I go to the GUI for zwave probably every day to refresh status to get the battery - can this be done automatically, say once a day?