Status of Door Lock

I have a Kwikset 910 zwave door lock and I can open and close the door correctly via Indigo thank to the new support for encrypted communication.
But the status is not completely correct. The following 6 log entries correspond to unlocking and locking the door via Indigo, manually and via keypad respectively:
Z-Wave received "Front Door" status update locked but bolt not fully extended (via controller)
Z-Wave received "Front Door" status update locked (via controller)

Z-Wave received "Front Door" status update unlocked (manually)
Z-Wave received "Front Door" status update locked (manually)

Z-Wave received "Front Door" status update locked but bolt not fully extended (via keypad)
Z-Wave received "Front Door" status update locked (via keypad)
Somehow the status does not show "unlocked" when the door is unlocked via Indigo and via keypad.

Any idea?
-Roland

Fix the striker plate cavity so that the bolt extends all the way properly, and see if it works better. Manual deadbolts don't care if they hit the inside of the cavity. Electronic locks don't like it, since they can't tell if they're almost all the way out, or just barely out. If it doesn't go all the way cleanly, they get confused.

Hm-I would understand if the "locked" status would show abnormalities. But I have problems with the "unlocked" state. How would you explain that?

[matt (support)]

There is only a single "bolt not full extended" error message which doesn't specify if the lock should be considered in the secure (locked) or unsecured (unlocked) state.

That said, I presumed the error would only occur when a lock command was given, not an unlock command (since the error is described as being about the bolt extending not retracting). But based on your description you are getting it when you issue the unlock command?

Yes that is correct Matt. I get the message
Z-Wave received "Front Door" status update locked but bolt not fully extended (via controller)
when I UNLOCK the door. I get the message even if the door is open so there is nothing that could impede the bolt from moving.

[matt (support)]

Can you re-sync the lock and copy/paste the Event Log results into a reply for me?

I know that others have reported those messages are being interpreted correctly by Indigo, so if I change them to work for your lock it will break for other locks. I'm hoping we can find someone that has the same specific model lock you have (including firmware) to see if all versions with that firmware have the same anomaly or not.

[jay (support)]

Yes that is correct Matt. I get the message
Z-Wave received "Front Door" status update locked but bolt not fully extended (via controller)
when I UNLOCK the door. I get the message even if the door is open so there is nothing that could impede the bolt from moving.

Note - I get a similar message when my door is open if I try to lock it. My suspicion is that your lock sometimes (for some reason) doesn't believe it's mounted correctly, which is why you're getting that error. Just a suspicion from my testing. Hopefully the exclude/include will provide more information.

Hi Matt,
this is the log

Z-Wave Syncing - started for "Front Door"
Z-Wave Syncing - retrieved module neighbors list: 2, 4, 7, 10, 14, 15, 26, 29
Z-Wave Syncing - assigning return route to "042 - Front Door"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Kwikset - 0090, SmartCode Lock - 00010001
Z-Wave Syncing - retrieved protocol version 2.78, app version 1.03
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Entry Control : Keypad Door Lock (04 : 40 : 03, base 62)
Z-Wave Syncing - retrieved command classes: 80v1 85v1 86v1 8Bv1 4Cv1 4Ev1 98v1 20v1 62v1 63v1 70v1 71v1 72v1 75v1
Z-Wave Syncing - retrieved encrypt commands: 80 85 86 8B 4C 4E 98 20 62 63 70 71 72 75
Z-Wave Syncing - retrieved capabilities: routing, battery, beaming, security, frequentWaking
Z-Wave Syncing - retrieved group 1 associations: [1]
Z-Wave Syncing - group 1 association to interface already exists (skipping)
Z-Wave Syncing - retrieved battery level of 40%
Z-Wave Syncing - complete
Z-Wave sent "Front Door" status request
Z-Wave received "042 - Front Door" status update battery level 40%

-Roland

[matt (support)]

I've located another Indigo user with that exact same model and same firmware version. Hopefully he can try the same tests and we can compare the results.

Looks like mine, except for version number:

Code: Select all

   Z-Wave                          Syncing - started for "Garage Entry Door Lock"
   Z-Wave                          Syncing - retrieved module neighbors list: 2, 3, 5
   Z-Wave                          Syncing - assigning return route to "010 - Garage Entry Door Lock"
   Z-Wave                          Syncing - assigned return route
   Z-Wave                          Syncing - retrieved manufacture and model names: Kwikset - 0090, SmartCode Lock - 00010001
   Z-Wave                          Syncing - retrieved protocol version 3.67, app version 3.37
   Z-Wave                          Syncing - retrieved class hierarchy: Routing Slave : Entry Control : Keypad Door Lock (04 : 40 : 03, base 62)
   Z-Wave                          Syncing - retrieved command classes: 80v1 85v1 86v1 8Bv1 4Cv1 4Ev1 98v1 5Dv1 20v1 62v1 63v1 70v1 71v1 72v1 75v1
   Z-Wave                          Syncing - retrieved encrypt commands: 80 85 86 8B 4C 4E 98 5D 20 62 63 70 71 72 75
   Z-Wave                          Syncing - retrieved capabilities: routing, battery, beaming, security, frequentWaking
   Z-Wave                          Syncing - retrieved group 1 associations: [1]
   Z-Wave                          Syncing - group 1 association to interface already exists (skipping)
   Z-Wave                          Syncing - retrieved battery level of 40%
   Z-Wave                          Syncing - complete
   Z-Wave                          sent "Garage Entry Door Lock" status request


I had a similar problem last year with my 910 a couple of days after I initially installed it on the Vera; the lock had somehow gotten out of calibration (or hadn't gotten the initial calibration right ITFP) and had to be factory reset and put through the self calibrate sequence again. But since then' it's been rock solid on both the Vera lite and I7.

I've located another Indigo user with that exact same model and same firmware version. Hopefully he can try the same tests and we can compare the results.

Matt,

Here is the log file for my Kwikset 910 lock that you requested. If you need anything else, let me know. I'd be glad to help. The one thing I did notice is that you don't always get a log entry when the door is unlocked manually via the inside deadbolt. For everything else, I always get a log entry.

Code: Select all

Dec 5, 2016, 11:52:45 AM
***Locked Door via keypad***
   Z-Wave Debug                    RCVD nonceFetch: node 029
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 1D 0A 98 80 4E C1 BF 17 DB 89 9B 74 25 69 24
   Z-Wave Debug                    RCVD encryptedPacket: 00 71 05 12 00 (decrypted)
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0A 00 04 00 1D 04 71 05 12 00 FF
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 029, endpoint None, cmdClass 71, type 18, value 0, classSubKey 711200
   Z-Wave                          received "Door - Front Lock" status update locked (via keypad)
   Z-Wave Lock Manager             Status: User 0 locked door [Node: 29]

Dec 5, 2016, 11:53:34 AM
***Unlocked Door via keypad (user #2)***
   Z-Wave Debug                    RCVD nonceFetch: node 029
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 1D 0A 98 80 38 17 1C BA EA 41 90 8C 25 6A 83
   Z-Wave Debug                    RCVD encryptedPacket: 00 71 05 13 02 (decrypted)
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0A 00 04 00 1D 04 71 05 13 02 FF
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 029, endpoint None, cmdClass 71, type 19, value 2, classSubKey 711302
   Z-Wave                          received "Door - Front Lock" status update unlocked by user 002 (via keypad)
   Z-Wave Lock Manager             Status: User 2 unlocked door [Node: 29]

***Locked Door via keypad***
   Z-Wave Debug                    RCVD nonceFetch: node 029
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 1D 0A 98 80 56 92 26 33 C7 39 03 B8 25 6B 28
   Z-Wave Debug                    RCVD encryptedPacket: 00 71 05 12 00 (decrypted)
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0A 00 04 00 1D 04 71 05 12 00 FF
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 029, endpoint None, cmdClass 71, type 18, value 0, classSubKey 711200
   Z-Wave                          received "Door - Front Lock" status update locked (via keypad)
   Z-Wave Lock Manager             Status: User 0 locked door [Node: 29]

Dec 5, 2016, 11:54:21 AM
***Unlocked Door via keypad (user #1)***
   Z-Wave Debug                    RCVD nonceFetch: node 029
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 1D 0A 98 80 C7 9F 6D 9E 64 B9 5F 0A 25 6C 98
   Z-Wave Debug                    RCVD encryptedPacket: 00 71 05 13 01 (decrypted)
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0A 00 04 00 1D 04 71 05 13 01 FF
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 029, endpoint None, cmdClass 71, type 19, value 1, classSubKey 711301
   Z-Wave                          received "Door - Front Lock" status update unlocked by user 001 (via keypad)
   Z-Wave Lock Manager             Status: User 1 unlocked door [Node: 29]

***Locked Door Manually - inside deadbolt***
   Z-Wave Debug                    RCVD nonceFetch: node 029
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 1D 0A 98 80 FB C6 77 84 D6 B3 3B 76 25 6D 5C
   Z-Wave Debug                    RCVD encryptedPacket: 00 71 05 15 01 (decrypted)
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0A 00 04 00 1D 04 71 05 15 01 FF
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 029, endpoint None, cmdClass 71, type 21, value 1, classSubKey 711501
   Z-Wave                          received "Door - Front Lock" status update locked (manually)
   Z-Wave Lock Manager             Status: Door locked manually [Node: 29]

Dec 5, 2016, 11:55:53 AM
***Unlocked Door via Indigo controller button***
   Z-Wave Debug                    SENT nonceRequest: 01 09 00 13 1D 02 98 40 25 6E 69
   Z-Wave Debug                    RCVD nonceReport: node 029, nonce AB 42 64 09 AA DC 21 02
   Z-Wave Debug                    SENT setLockValue: 62 01 00 (encrypted)
   Z-Wave                          sent "Door - Front Lock" unlock
   Z-Wave Debug                    RCVD nonceFetch: node 029
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 1D 0A 98 80 CC AD 8E 6F D4 1E 2E 3A 25 70 F9
   Z-Wave Debug                    RCVD nonceFetch: node 029
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 1D 0A 98 80 CC AD 8E 6F D4 1E 2E 3A 25 71 F8
   Z-Wave Debug                    . .  nonceReport: requeuing 1 unsolicited packets
   Z-Wave Debug                    RCVD encryptedPacket: 00 71 05 19 01 (decrypted)
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0A 00 04 00 1D 04 71 05 19 01 FF
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 029, endpoint None, cmdClass 71, type 25, value 1, classSubKey 711901
   Z-Wave                          received "Door - Front Lock" status update unlocked (via controller)
   Z-Wave Lock Manager             Status: Door unlocked by Indigo [Node: 29]
   Z-Wave Debug                    reusing outgoing nonce CC AD 8E 6F D4 1E 2E 3A
   Z-Wave Debug                    RCVD encryptedPacket: 00 71 05 19 01 (decrypted)
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0A 00 04 00 1D 04 71 05 19 01 FF
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 029, endpoint None, cmdClass 71, type 25, value 1, classSubKey 711901
   Z-Wave                          received "Door - Front Lock" status update unlocked (via controller)
   Z-Wave Lock Manager             Status: Door unlocked by Indigo [Node: 29]

***Locked Door via Indigo controller button***
   Z-Wave Debug                    SENT nonceRequest: 01 09 00 13 1D 02 98 40 25 72 75
   Z-Wave Debug                    RCVD nonceReport: node 029, nonce E5 07 97 1D 86 E2 1E D6
   Z-Wave Debug                    SENT setLockValue: 62 01 FF (encrypted)
   Z-Wave                          sent "Door - Front Lock" lock
   Z-Wave Debug                    RCVD nonceFetch: node 029
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 1D 0A 98 80 D3 6C 1D 00 48 C8 DC 54 25 74 09
   Z-Wave Debug                    RCVD encryptedPacket: 00 71 05 18 01 (decrypted)
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0A 00 04 00 1D 04 71 05 18 01 FF
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 029, endpoint None, cmdClass 71, type 24, value 1, classSubKey 711801
   Z-Wave                          received "Door - Front Lock" status update locked (via controller)
   Z-Wave Lock Manager             Status: Door locked by Indigo [Node: 29]

Dec 5, 2016, 12:17:15 PM
***Unlocked Door via  inside deadbolt***
   Z-Wave Debug                    RCVD nonceFetch: node 029
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 1D 0A 98 80 C3 A7 F3 88 BC 04 B6 E5 25 77 54
   Z-Wave Debug                    RCVD encryptedPacket: 00 71 05 16 01 (decrypted)
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0A 00 04 00 1D 04 71 05 16 01 FF
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 029, endpoint None, cmdClass 71, type 22, value 1, classSubKey 711601
   Z-Wave                          received "Door - Front Lock" status update unlocked (manually)
   Z-Wave Lock Manager             Status: Door unlocked manually [Node: 29]

[jay (support)]

I have the identical lock as you - same firmware version, etc. and mine's working fine. I believe johnpolasek is correct - you probably need to factory reset the lock and then perform the calibration again. Seems to me I had to do that when I switched it from the Vera to Indigo.

I've not read and interpreted everything in this thread, so I'll just observe for now, but I noticed the ID Lock (Norwegian) reports the locked/unlocked state as essentially a Boolean via the door lock command class, then the actual action report or status update of the lock is reported by the alarm notification class.

Does Indigo combine such as these when displaying the state of the door? (ID lock isn't supported yet, but it roughly seemed to match what's being discussed here)


Sent from my iPhone using Tapatalk

[matt (support)]

Indigo catches both lock/entry specific report/set commands (0x76 0x03 and 0x76 0x01) as well as the alarm notification class. Indigo doesn't try to update the state if it isn't changing to avoid duplicate work, but it'll catch and act on either command types.