Yale Conexis L1

Configuration Z-Wave
1

Is anyone else experiencing issues with the Yale Conexis L1? I get all the lock and unlock data states, but HA can no longer activate the lock, i.e. lock or unlock it.

I have it set up in secure mode, and it was working before the update to 2021.7. I’ve just updated to 2021.7.4 and it’s still not working as expected.

This is the error I get when I click to unlock:

2021-07-27T13:48:53.256Z CNTRLR   [Node 005] Timed out while waiting for a response from the node

This is the log from trying to add the node again, after I had just removed it:

2021-07-27T13:14:24.761Z CNTRLR » [Node 005] Assigning SUC return route...
2021-07-27T13:14:24.770Z CNTRLR   the inclusion process was stopped
2021-07-27T13:14:25.732Z CNTRLR   [Node 005] Cannot configure Z-Wave+ Lifeline association: Node does not suppor
                                  t associations...
2021-07-27T13:14:25.736Z CNTRLR   [Node 005] Beginning interview - last completed stage: None
2021-07-27T13:14:25.737Z CNTRLR   [Node 005] new node, doing a full interview...
2021-07-27T13:14:25.738Z CNTRLR » [Node 005] querying protocol info...
2021-07-27T13:14:25.770Z CNTRLR « [Node 005] received response for protocol info:
                                  basic device class:    Routing Slave
                                  generic device class:  Entry Control
                                  specific device class: Secure Keypad Door Lock
                                  node type:             Routing End Node
                                  is always listening:   false
                                  is frequent listening: 1000ms
                                  can route messages:    true
                                  supports security:     false
                                  supports beaming:      true
                                  maximum data rate:     100000 kbps
                                  protocol version:      3
2021-07-27T13:14:25.778Z CNTRLR   [Node 005] Interview stage completed: ProtocolInfo
2021-07-27T13:14:25.779Z CNTRLR » [Node 005] querying node info...
2021-07-27T13:14:25.863Z CNTRLR « [Node 005] node info received
                                  supported CCs:
                                  · Z-Wave Plus Info
                                  · Transport Service
                                  · Security
                                  · Security 2
                                  controlled CCs:
2021-07-27T13:14:25.865Z CNTRLR   [Node 005] Interview stage completed: NodeInfo
2021-07-27T13:14:25.867Z CNTRLR » [Node 005] querying securely supported commands...
2021-07-27T13:14:35.937Z CNTRLR   [Node 005] Timed out while waiting for a response from the node
2021-07-27T13:14:35.938Z CNTRLR   [Node 005] The node is not included securely. Continuing interview non-securel
                                  y.
2021-07-27T13:14:35.945Z CNTRLR   [Node 005] Interviewing Manufacturer Specific...
2021-07-27T13:14:35.946Z CNTRLR » [Node 005] querying manufacturer information...
2021-07-27T13:14:47.228Z CNTRLR   [Node 005] Timed out while waiting for a response from the node
2021-07-27T13:14:47.234Z CNTRLR   [Node 005] Interviewing Version...
2021-07-27T13:14:47.235Z CNTRLR » [Node 005]   querying the CC version for Version...
2021-07-27T13:14:58.510Z CNTRLR   [Node 005] Timed out while waiting for a response from the node
2021-07-27T13:14:58.511Z CNTRLR   [Node 005] CC version query for Version timed out - assuming the node supports
                                   version 1...
2021-07-27T13:14:58.512Z CNTRLR » [Node 005] querying node versions...
2021-07-27T13:15:09.828Z CNTRLR   [Node 005] Timed out while waiting for a response from the node
2021-07-27T13:15:09.829Z CNTRLR » [Node 005] querying CC versions...
2021-07-27T13:15:09.830Z CNTRLR » [Node 005]   querying the CC version for Basic...
2021-07-27T13:15:21.132Z CNTRLR   [Node 005] Timed out while waiting for a response from the node
2021-07-27T13:15:21.133Z CNTRLR   [Node 005] CC version query for Basic timed out - assuming the node supports v
                                  ersion 1...
2021-07-27T13:15:21.135Z CNTRLR » [Node 005]   querying the CC version for Door Lock...
2021-07-27T13:15:32.430Z CNTRLR   [Node 005] Timed out while waiting for a response from the node
2021-07-27T13:15:32.431Z CNTRLR   [Node 005] CC version query for Door Lock timed out - assuming the node suppor
                                  ts version 1...
2021-07-27T13:15:32.432Z CNTRLR » [Node 005]   querying the CC version for User Code...
2021-07-27T13:15:43.724Z CNTRLR   [Node 005] Timed out while waiting for a response from the node
2021-07-27T13:15:43.725Z CNTRLR   [Node 005] CC version query for User Code timed out - assuming the node suppor
                                  ts version 1...
2021-07-27T13:15:43.726Z CNTRLR » [Node 005]   querying the CC version for Manufacturer Specific...
2021-07-27T13:15:55.015Z CNTRLR   [Node 005] Timed out while waiting for a response from the node
2021-07-27T13:15:55.017Z CNTRLR   [Node 005] CC version query for Manufacturer Specific timed out - assuming the
                                   node supports version 1...
2021-07-27T13:15:55.018Z CNTRLR   [Node 005]   skipping query for Security (0x98) because max implemented versio
                                  n is 1
2021-07-27T13:15:55.019Z CNTRLR » [Node 005]   querying the CC version for Z-Wave Plus Info...
2021-07-27T13:16:06.348Z CNTRLR   [Node 005] Timed out while waiting for a response from the node
2021-07-27T13:16:06.349Z CNTRLR   [Node 005] CC version query for Z-Wave Plus Info timed out - assuming the node
                                   supports version 1...
2021-07-27T13:16:06.350Z CNTRLR » [Node 005]   querying the CC version for Transport Service...
2021-07-27T13:16:17.617Z CNTRLR   [Node 005] Timed out while waiting for a response from the node
2021-07-27T13:16:17.618Z CNTRLR   [Node 005] CC version query for Transport Service timed out - assuming the nod
                                  e supports version 1...
2021-07-27T13:16:17.619Z CNTRLR   [Node 005]   skipping query for Security 2 (0x9f) because max implemented vers
                                  ion is 0
2021-07-27T13:16:17.628Z CNTRLR   [Node 005] Interviewing Z-Wave Plus Info...
2021-07-27T13:16:17.629Z CNTRLR » [Node 005] querying Z-Wave+ information...
2021-07-27T13:16:18.933Z CNTRLR « [Node 005] received response for Z-Wave+ information:
                                  Z-Wave+ version: 1
                                  role type:       SleepingListeningSlave
                                  node type:       Node
                                  installer icon:  0x0300
                                  user icon:       0x0300
2021-07-27T13:16:18.941Z CNTRLR   [Node 005] Interviewing Door Lock...
2021-07-27T13:16:18.941Z CNTRLR » [Node 005] requesting lock configuration...
2021-07-27T13:16:28.994Z CNTRLR   [Node 005] Timed out while waiting for a response from the node
2021-07-27T13:16:28.996Z CNTRLR » [Node 005] requesting current lock status...
2021-07-27T13:16:40.301Z CNTRLR   [Node 005] Timed out while waiting for a response from the node
2021-07-27T13:16:40.310Z CNTRLR   [Node 005] Interviewing User Code...
2021-07-27T13:16:40.311Z CNTRLR » [Node 005] querying number of user codes...
2021-07-27T13:16:51.659Z CNTRLR   [Node 005] Timed out while waiting for a response from the node
2021-07-27T13:16:51.660Z CNTRLR   [Node 005] Querying number of user codes timed out, skipping interview...
2021-07-27T13:16:51.666Z CNTRLR   [Node 005] Interview stage completed: CommandClasses
2021-07-27T13:16:51.667Z CNTRLR   [Node 005] Interview stage completed: OverwriteConfig
2021-07-27T13:16:51.668Z CNTRLR   [Node 005] Interview completed
2

Locks must be includes securely into the network. Inclusion must be performed after a fresh factory reset of the lock. The inclusion process must complete within 15 seconds. Many times it needs a strong signal from the controller to accomplish that.

3

Does it have to be a factory reset? As I am pretty sure this loses all your virtual keys, so I’d have to pay Yale to get more.

4

My understanding from a developer who wrote the integration for a different product who studied the standard, yes it need to be a factory reset. He sells his product commercially too.

5

Cheers for the information.

I managed to get it to work by first excluding the lock from the network, then removing the batteries and Z-Wave modules, replacing batteries and allowing the lock to boot, removing the batteries and replacing the Z-Wave module, then boot the lock, start the secure inclusion and re-add the lock.

2 Likes
6

For anyone else facing this issue (i had same timeouts in log) for ZWave JS i managed to add the connexis LS lock by using legacy secure inclusion method

7

I’m experiencing an oddity, where the unlock function works fine, however once the Conexis is unlocked, it becomes unresponsive, only recovering once the auto-lock relocks, or the door is manually relocked.
Therefore it’s never possible to lock the Conexis via z-wave.

Has anyone else experienced this? TIA!

2021-11-29_17-06-54

8

I have been struggling with add my Conexis L1 today. These are the steps to complete the secure pairing. All the information is in this thread and assumes you have Z-Wave JS integration already setup.

This is using Home Assistant 2021.12.4 and Z-Wave JS 0.1.50.

If the device Conexis L1 is already pair in a non-secure way it needs to be removed.

  1. In HA: Configuration → Devices and Services (integrations) → Z-Wave JS → CONFIGURE → REMOVE DEVICE
  2. On the lock remove the cover to expose the Z-Wave module. Press the ‘R’ button three times with 1.5 seconds.
  3. In HA: Press START EXCLUSION. The device should now be removed.

The device now need to be securely added.

  1. In HA: Configuration → Devices and Services (integrations) → Z-Wave JS → CONFIGURE → ADD DEVICE
  2. On the lock remove the cover to expose the Z-Wave module. Press the ‘R’ button three times with 1.5 seconds.
  3. When the device is discovered a 5-digit pin number will be requested. The 5-digit pin number are the first five digits on the z-wave module. These are underlined.
  4. Enter the 5-digit pin number and let the secure pairing complete. This takes some time so the dialog can be closed.

Hope this helps someone as the information is out there but all over the place.

4 Likes
9

Hey,
how are you getting on with the Yale L1 Conexis on zwavejs i’m currently on the Z-Wave (deprecated) version as I’ve read a while ago it won’t show you who unlocked the door last unless it was done with a different key.

currently my HA updates with who and when the door was unlocked regardless if it’s the same key.

10

All setup but I do have the issue you mention. I cannot find the ID of key used to unlock the door. That said, I haven’t looked into detail yet to address this. I appreciate that this is an issue but I would expect a solution can be found… just haven’t found it yet.

Perhaps someone else on this thread knows how to get the ID of the key used.

11

@GeoffAtHome
I keep seeing people accessing more data from the z wave logs.

I stumbled on the below and asked if anyone used it with L1 yet didn’t get a response.

I’ve been really hesitant in switching over and digging around myself as I use the key ID very heavily and don’t want to be stuck unable to switch back.

If you could, I would really appreciate if you can confirm its possible. :smiley:

12
13

User ID maybe found here:

14

@phairplay tracking users is fine. Straight forward to setup once you know you have to look on the event bus for information.

1 Like
15

So is it stored in the z wave notification?
Does it update everytime the door is unlocked even with the same key?

16

Trigger on lock/unlock and detect who unlocked the door. Filter out manual lock/unlock from indoors.

1 Like
17

Thank you for helping confirm this information I really appreciate it.

where is the information found, have you crested a sensor?

18

I have a Connexis L1 which has been excellent for over a year, however in the last 2 weeks has gone through a set of battery’s. Anyone else noticed an increase in battery usage? Reading online it seems to be common with certain ZWave controllers.

19

I have 3 Conexis L1 locks installed, the battery life on them (with rechargeable AA batteries in them) is 3-6 months depending on frequency of use, I did have an issue with the front door once, where the lock went through a set of batteries in a couple of weeks. I found out that in my case it was caused as the lock bolt and keeper weren’t perfectly aligned. I was told that the lock usually runs the motor driving the bolt in a low power mode, but if it has difficulty locking the bolt then it tries in a high power mode, which drains the batteries a lot faster. Once it has been successful in high power mode it stays in high power mode.

I fixed my issue by adjusting the lock keeper, and then power cycling the lock (removing and replacing the batteries), and have had good battery life (for rechargeable batteries) ever since.

1 Like
20

Interesting. Weirdly, now you say it, my lock has an entity which shows as “Lock Jammed” and is displaying “Problem”. Even power cycling the lock doesn’t get rid of it. The lock works fine, not sure what it’s referring to, as it’s clearly not jammed.