Has anybody managed to get this device to connect successfully, and if so is there an app/DH for it so you can see who is entering/unlocking the door with the key fobs.
Cheers Pete
There is a built-in DH for the Conexis L1 in the latest HE update. Does not tell you who is going I/out though.
1 Like
Just got one of these and it's working good so far.
I have a couple of questions regard HE device driver, so thought i would put it here rather starting new post.
I have the zwave v2 module and it paired without fault.
I tried changing the auto re-lock time but it doesn't appear to work. tried a few times. I have seen in the logs a reference to autotimeout mins/sec which the last one say it was set to 254 mins and 254 secs i don't think that's right.
Also i can lock and unlock from HE but it will also let me try and lock it when the dead bolts are not engaged, ie handle has not been set in up position. This causes the motor to come on and strain for a few moments then times out. The motor is not meant to operate until deadbolts are engaged.
Don't know if you could look into these @mike.maxwell
Thanks
I'm not sure the driver can do anything about this, is there a status in the driver for the deadbolt?
Yeah i think there is @mike.maxwell , maybe handlestatus from what i remember seeing in HE log after setting it up.
I don't have one of these locks, it was loaned to me for driver development.
So if there's any chance of fixing this without the lock in hand you'll need to post the live logs with debug logging enabled and identify the conditions under which the lock command should be ignored...
Ok got some log info for you @mike.maxwell
I can't tell what info tells us that it's unlocked but handle has not been operated. If i operate handle down after unlocking from HE it does not send event when i pull handle down only when it's locked handle up.
The config parameters i don't think are right for auto re-lock as i can't get it to re-lock if handle is not used after 30 seconds or maybe something else but it did work in factory state until i changed configure.
dev:11222020-04-30 14:30:47.799 infoFront Door Lock was unlocked via command [digital]
dev:11222020-04-30 14:30:47.767 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:25, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:0, zwaveAlarmStatus:0, zwaveAlarmType:0)
dev:11222020-04-30 14:30:47.680 debugparse: zw device: 0C, command: 9881, payload: 00 71 05 19 01 , isMulticast: false
dev:11222020-04-30 14:30:46.807 debugDoorLockOperationReport: DoorLockOperationReport(doorCondition:2, doorLockMode:0, insideDoorHandlesMode:0, lockTimeoutMinutes:254, lockTimeoutSeconds:254, outsideDoorHandlesMode:1)
dev:11222020-04-30 14:30:46.700 debugparse: zw device: 0C, command: 9881, payload: 00 62 03 00 10 02 FE FE , isMulticast: false
dev:11222020-04-30 14:29:51.227 infoFront Door Lock battery is 100%
dev:11222020-04-30 14:29:51.212 debugBatteryReport: BatteryReport(batteryLevel:100)
dev:11222020-04-30 14:29:51.107 debugparse: zw device: 0C, command: 9881, payload: 00 80 03 64 , isMulticast: false
dev:11222020-04-30 14:29:46.844 warndescription logging is: true
dev:11222020-04-30 14:29:46.831 warndebug logging is: true
dev:11222020-04-30 14:29:46.829 infoupdated...
dev:11222020-04-30 14:09:20.242 infoFront Door Lock was locked via thumbturn [physical]
dev:11222020-04-30 14:09:20.237 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:21, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:0, zwaveAlarmStatus:0, zwaveAlarmType:0)
dev:11222020-04-30 14:09:20.227 debugparse: zw device: 0C, command: 9881, payload: 00 71 05 15 01 , isMulticast: false
dev:11222020-04-30 14:09:19.230 debugDoorLockOperationReport: DoorLockOperationReport(doorCondition:1, doorLockMode:255, insideDoorHandlesMode:0, lockTimeoutMinutes:0, lockTimeoutSeconds:0, outsideDoorHandlesMode:0)
dev:11222020-04-30 14:09:19.224 debugparse: zw device: 0C, command: 9881, payload: 00 62 03 FF 00 01 00 00 , isMulticast: false
dev:11222020-04-30 14:09:08.976 infoFront Door Lock was unlocked via thumbturn [physical]
dev:11222020-04-30 14:09:08.972 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:22, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:0, zwaveAlarmStatus:0, zwaveAlarmType:0)
dev:11222020-04-30 14:09:08.954 debugparse: zw device: 0C, command: 9881, payload: 00 71 05 16 01 , isMulticast: false
dev:11222020-04-30 14:09:07.965 debugDoorLockOperationReport: DoorLockOperationReport(doorCondition:2, doorLockMode:0, insideDoorHandlesMode:0, lockTimeoutMinutes:254, lockTimeoutSeconds:254, outsideDoorHandlesMode:1)
dev:11222020-04-30 14:09:07.960 debugparse: zw device: 0C, command: 9881, payload: 00 62 03 00 10 02 FE FE , isMulticast: false
dev:11222020-04-30 14:09:06.333 infoFront Door Lock was locked via thumbturn [physical]
dev:11222020-04-30 14:09:06.328 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:21, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:0, zwaveAlarmStatus:0, zwaveAlarmType:0)
dev:11222020-04-30 14:09:06.304 debugparse: zw device: 0C, command: 9881, payload: 00 71 05 15 01 , isMulticast: false
dev:11222020-04-30 14:09:05.339 debugDoorLockOperationReport: DoorLockOperationReport(doorCondition:1, doorLockMode:255, insideDoorHandlesMode:0, lockTimeoutMinutes:0, lockTimeoutSeconds:0, outsideDoorHandlesMode:0)
dev:11222020-04-30 14:09:05.327 debugparse: zw device: 0C, command: 9881, payload: 00 62 03 FF 00 01 00 00 , isMulticast: false
dev:11222020-04-30 14:07:07.792 infoFront Door Lock was unlocked via command [digital]
dev:11222020-04-30 14:07:07.787 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:25, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:0, zwaveAlarmStatus:0, zwaveAlarmType:0)
dev:11222020-04-30 14:07:07.681 debugparse: zw device: 0C, command: 9881, payload: 00 71 05 19 01 , isMulticast: false
dev:11222020-04-30 14:07:06.793 debugDoorLockOperationReport: DoorLockOperationReport(doorCondition:2, doorLockMode:0, insideDoorHandlesMode:0, lockTimeoutMinutes:254, lockTimeoutSeconds:254, outsideDoorHandlesMode:1)
dev:11222020-04-30 14:07:06.696 debugparse: zw device: 0C, command: 9881, payload: 00 62 03 00 10 02 FE FE , isMulticast: false
--- Live Log Started, waiting for events ---Is it possible to add pin to unlock @mike.maxwell ? If i add it to dashboard there is no option to pin protect so anyone can just unlock it.
Hi. This might be off topic, however I need some help pairing my conexis L1.
I have a Hubitat C7 and also a "refurbished" Conexis L1 lock with Z-Wave module.
When I am following the guide to pair them, I am instructed to press the button three times within 1.5 seconds. However the lock does not understand this command. It reacts to the first press right away with a beep, and a "reverse" beep to the second press.
It kinda randomly appears on hubitat's found device list, but never goes out of "initializing" state and there seems to be no reaction from the lock.
Any ideas?
Also, does this lock work with "automatic" type of doors, where you can lock the door without lifting the handle?
I believe there are two types of z wave module, you need the type 2 which is blue, The lock will not engage if you don’t lift up the handle.
Thank you.
Yes, mine is blue.
So just to confirm, no one is familiar with this behavior of the lock, when it immediatelly reacts to the first press of a button? Is it in some kind of mode, where it does not expect the triple press?
Yes sounds like you have a problem either with the module or the lock,
