I have the app and not changing the fobs in over a year. I really hope not to factory reset.
Would it reset my z wave connection?
I can add fobs ok, haven’t tried removing one
Your lock must be a new revision. I bought mine in 2018 and the motor does not turn the deadbolt that quickly. It sucks, a lot of the time people think it’s unlocked and they jam the lock by trying to pull on the handle, because it’s so slow… It receives the signals from the zwave stick almost as quickly as I press the unlock button on HA but unfortunately it takes several seconds for the motor to detract the deadbolt 
Hi,
I’ve started having an issue with my connection to home assistant, over the past week I’ve noticed that when I lock the door, which HA does see a few seconds later HA reports the door is unlocked.
has anyone come across this?
I have the connexus L1 and dont have any issues
I have the same lock and it’s only being happening over the past few weeks. I’ve upgraded to 116.2 to see if there was a bug in home assistant.
I am also running 116.2, could it be your zwave network, have your tried refreshing it
1 Like
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?