Status of Door Lock

I did factory reset my lock and then included in it again. The weird behavior did not change. Am still getting "bolt not fully extended" when I unlock the door:

Z-Wave Syncing - started for "043 - Keypad Door Lock"
Z-Wave Syncing - retrieved module neighbors list: 2, 4, 7, 10, 14, 15, 26, 29
Z-Wave Syncing - assigning return route to "043 - Keypad 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 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 20 62 63 85 86 8B 4C 4E 70 71 72 75 98
Z-Wave Syncing - retrieved capabilities: routing, battery, beaming, security, frequentWaking
Z-Wave Syncing - retrieved group 1 associations: []
Z-Wave Syncing - added group 1 association to interface
Z-Wave Syncing - retrieved battery level of 50%
SQL Logger creating table device_history_738152955 for "043 - SmartCode Lock"
Z-Wave Syncing - created device "043 - SmartCode Lock"
SQL Logger adding column "batterylevel" to table device_history_738152955 ("043 - SmartCode Lock")
Z-Wave Syncing - complete
SQL Logger adding column "batterylevel_ui" to table device_history_738152955 ("043 - SmartCode Lock")
Z-Wave sent "043 - SmartCode Lock" status request
Z-Wave received "043 - SmartCode Lock" status update battery level 50%
Z-Wave received "Washer Switch" power load to 0.105 W
Z-Wave sent "043 - SmartCode Lock" lock
SQL Logger adding column "onoffstate_ui" to table device_history_738152955 ("043 - SmartCode Lock")
Z-Wave received "043 - SmartCode Lock" status update locked (via controller)
Z-Wave sent "043 - SmartCode Lock" unlock
Z-Wave received "043 - SmartCode Lock" status update locked but bolt not fully extended (via controller)
Z-Wave sent "043 - SmartCode Lock" lock
Z-Wave received "043 - SmartCode Lock" status update locked (via controller)

Is this a new installation? If so, did you correctly follow steps 2, 6, and 10 in the installation guide
http://s7d5.scene7.com/is/content/BDHHI/50268860 (US version)?

As I said, when I first installed mine, I had to repeat step 10 a couple of days after I first installed the lock; the messages on Vera were differently worded but had to do with bolt not correctly positioned... However, after that, it's been perfect (except for battery replacement after 8 months) for just over a year now.

I am having the same issue.

A Kwikset 910, I re-synched. I can see the variable change form false to true, but never the reverse, from true to false.

The indigo page correctly shows unlocked below the battery level, but the variable I created will not update.

How can I tap into the lock control status with python as a workaround to update the variable ?

Thanks!

[matt (support)]

Copy/paste what you are seeing in the Event Log (and describe what you are doing along with the log results).

Matt,

Sure - I have included two PNG files ... showing the device control indicating the garage door is locked, and it reflects the actual lock state.

I created a test trigger to change the variable I created called Var_GarageDoorLocked, to ensure that when the door lock changes state, that variable also updates(I wanted to use the variable stain in a python script to check multiple doors)

Asked a different way " How can I hook into the value I see on the door lock control inside Indigo?" that seems to be correct / reliable , but the on/off state available in indigo for the door lock is not updating.

Thanks,

Brian

[matt (support)]

How is the Trigger defined that executes the action to copy the device state to the variable value? Doesn't the problem seem to be that the trigger isn't firing?

Matt,

Correct, the trigger is not firing. I can trigger it manually...

See Pictures, attached.

Why is the trigger not firing if the lock control panel shows correctly ?

It seems as though part of the system knows the clock is closed, but other systems are not in synch.

Oh, and the reason I tried this trigger, is because DEVICE STATECHANGED did not work. When I unlock the door, it does not work, if I manually execute action now, on that trigger, it flips the flag to false when unlocked.

I have a similar setup on GARAGE DOOR LOCK, if the bolt is moved, the device will not change status, BUT.....Why does the lock control panel in indigo correctly show the status? Is this a function of the plugin, and how can I grab that status ?

Thanks

That's same screenshot twice - did you intend this?


Sent from my iPhone using Tapatalk

[matt (support)]

I'm still not following exactly what is occurring.

Can you please unlock and lock the door a couple of times, then open the Event Log window and copy/paste its contents (as text, not a screen shot) into a forum reply?

Also describe if the Event Log results are showing what you expect or not based on the unlock/lock sequence you performed.

I am not seeing that problem, perhaps because I am using the Z-wave lock manager plugin? Here's a log snippet from my side door Kwikset 910 a few minutes ago with the door open:

Jan 11, 2017, 4:56:25 AM
Z-Wave received "Side Door" status update locked (manually)
Trigger Side Door Lock copy<--- trigger which sends "Side Door Changed" to log when Side Door Device on.off state has any change.
Z-Wave Lock Manager Status: Door locked manually [Node: 20]
Action Collection Side Door Changed

Jan 11, 2017, 4:56:45 AM
Z-Wave received "Side Door" status update unlocked (manually)
Trigger Side Door Lock copy
Z-Wave Lock Manager Status: Door unlocked manually [Node: 20]
Action Collection Side Door Changed

Jan 11, 2017, 4:57:01 AM
Z-Wave received "Side Door" status update locked (manually)
Trigger Side Door Lock copy
Z-Wave Lock Manager Status: Door locked manually [Node: 20]
Action Collection Side Door Changed

Jan 11, 2017, 4:57:23 AM
Z-Wave received "Side Door" status update unlocked by user 002 (via keypad)
Trigger Side Door Lock copy
Z-Wave Lock Manager Status: User 2 unlocked door [Node: 20]
Action Collection Side Door Changed

Jan 11, 2017, 4:57:40 AM
Z-Wave received "Side Door" status update locked (via keypad)
Trigger Side Door Lock copy
Z-Wave Lock Manager Status: User 0 locked door [Node: 20]
Action Collection Side Door Changed

Jan 11, 2017, 4:58:21 AM
Z-Wave sent "Side Door" unlock
Trigger Side Door Lock copy
Action Collection Side Door Changed
Z-Wave received "Side Door" status update unlocked (via controller)
Z-Wave Lock Manager Status: Door unlocked by Indigo [Node: 20]
Z-Wave sent "Side Door" lock
Trigger Side Door Lock copy
Action Collection Side Door Changed
Z-Wave received "Side Door" status update locked (via controller)
Z-Wave Lock Manager Status: Door locked by Indigo [Node: 20]
Trigger SideDoor Changed
Z-Wave received "Side Door" status update unlocked (manually)
Trigger Side Door Lock copy

I added the temporary trigger to make the log entries and ran the test with the door open because all my standard triggers for the doors have a condition of "door closed" from a magnetic switch in the doorjamb and do a lot of security things. But as best as I can tell, every state change is logged unless the logic in the Is OFF or Is ON variants is messed up. And if that logic IS hosed, a temporary workaround would be to set up two triggers both by has any change with a condition "On" for one and "Off" for the other.

After a long time I looked again into this issue. After going through the entire factor-reset procedure I am still getting the same behavior.
Unlocking via zwave and via keypad shows
Z-Wave sent "043 - SmartCode Lock" unlock
Z-Wave received "043 - SmartCode Lock" status update locked but bolt not fully extended (via controller)
But then when I request a "Send Status Update" I get the correct:
Z-Wave sent "043 - SmartCode Lock" status request
Z-Wave received "043 - SmartCode Lock" status update is unlocked

Is there a way to set up a trigger to automatically request a status update (once) after a status change was received without causing an endless loop?

Thanks

To be doubly sure what's happening, can you either turn on Zwave debugging (interfaces > Zwave) or install Zwave lock manager plugin and turn that plugins debug on (plugins > Zwave lock manager > configure)

The former will add tonnes of logs to your log so the second might be easier.

Paste back the raw Zwave commands you're receiving when you unlock the door, and when you send a status update.

To answer your question, add a 'disable trigger' action and 'enable trigger' action to your existing trigger, with time delay.

So when trigger runs, it disables itself (so it doesn't run when status received) then it requests status, then it enables itself again a few seconds later.


Sent from my iPhone using Tapatalk

Sure - thanks - here is the log of the sequence lock->unlock->status request.
The door was open during this test to make sure it did not encounter any obstacle


Z-Wave sent "043 - SmartCode Lock" lock
Z-Wave received "043 - SmartCode Lock" status update locked (via controller)
Z-Wave Lock Manager Debug Checking if node 43 is a Lock...
Z-Wave Lock Manager Debug Node 43 added to list of lockIDs
Z-Wave Lock Manager Debug Node ID 43 found in lockIDs
Z-Wave Lock Manager Debug Node ID 43 found in lockIDs
Z-Wave Lock Manager Debug Raw: 01 0A 00 04 00 2B 04 71 05 18 01 FF
Z-Wave Lock Manager Status: Door locked by Indigo [Node: 43]
Z-Wave Lock Manager Debug -----
Z-Wave Lock Manager Debug Node ID 43 found in lockIDs
Z-Wave sent "043 - SmartCode Lock" unlock
Z-Wave received "043 - SmartCode Lock" status update locked but bolt not fully extended (via controller)
Z-Wave Lock Manager Debug Node ID 43 found in lockIDs
Z-Wave Lock Manager Debug Node ID 43 found in lockIDs
Z-Wave Lock Manager Debug Raw: 01 0A 00 04 00 2B 04 71 05 17 01 FF
Z-Wave Lock Manager Status: Door locked but bolt not fully extended [Node: 43]
Z-Wave Lock Manager Debug triggerEvent called
Z-Wave Lock Manager Debug -----
Z-Wave Lock Manager Debug Node ID 43 found in lockIDs
Z-Wave sent "043 - SmartCode Lock" status request
Z-Wave received "043 - SmartCode Lock" status update is unlocked
Z-Wave Lock Manager Debug Node ID 43 found in lockIDs
Z-Wave Lock Manager Debug Door: 01 0D 00 04 00 2B 07 62 03 00 00 02 FE FE FF
Z-Wave Lock Manager Debug
Z-Wave Lock Manager Debug Node: 43
Z-Wave Lock Manager Debug Type: 0
Z-Wave Lock Manager Debug User: 0
Z-Wave Lock Manager Status: Door is unlocked [Node: 43]
Z-Wave Lock Manager Latch open, Bolt unlocked, Door open [Node: 43]
Z-Wave Lock Manager Debug Node ID 43 found in lockIDs
Z-Wave Lock Manager Debug Node ID 43 found in lockIDs
Z-Wave received "043 - SmartCode Lock" status update battery level 30%
Z-Wave Lock Manager Debug Node ID 43 found in lockIDs
Z-Wave Lock Manager Debug Node ID 43 found in lockIDs

Ok, so 71 05 in the first two commands are ALARM commands.

The value 18 is defined in Kwikset manual (and others) as "Lock Secured by controller - successful"

The value 17 is defined in Kwikset manual (and others) as "Lock Secured by controller - Bolt Jammed".

So when sent the Unlock command, your lock is unlocking, but reporting value 17 to Indigo "I'm locked but jammed". Thus Indigo is showing wrong state, because that's what it is told.

Now the 62 03 in the status request is a DOOR LOCK command, not an ALARM command.

The 00 00 02 is not explicitly defined in the Kwikset manual but it does comply with Zwave spec which says "I'm unlocked, my latch is open, my bolt is unlocked and the door is open".

So when you send a status request, the lock correctly sends a DOOR LOCK report with the correct states, and Indigo thus displays correct state.

Matt/Jay/Anyone: What are your thoughts?

Is the lock faulty, is the firmware buggy (doubt it given others use same firmware), does it need hitting with a very large hammer?

If this was happening for everyone with this firmware/model, Matt/Jay could add an immediate status request whenever receiving mis-matched statuses. (Oi, you - unlock yourself.... Ok, I'm locked) but that's not the right way to fix this.


Sent from my iPhone using Tapatalk

Nothing helpful to add to this thread but wanted to say that my two Kwikset locks seem to function fine.

I have a 914 which is a door knob set and thus doesn't have a deadbolt that extends/retracts. The lock/unlock action on this set is basically the knob doesn't turn the mechanism when locked. This all works fine in Indigo.

I also have a 916 on a different door. This does have the deadbolt that extends/retracts so its probably most like the 910. When I installed it to replace the existing Kwikset manual/key deadbolt I found I needed to replace the actual bolt in the door with the one that came with the set. Before I did that the lock wouldn't properly extend/retract. (I had tried to short cut the installation by using the same bolt. Silly me.) Once I replaced it, the lock worked just fine and, perhaps due to it being a pretty new house, the bolt and striker plate align properly and I've never had a "bolt jammed" problem.

Afraid this info isn't much help for the OP though. Just a point of interest.