Door lock shows wrong status

[bwainscott]

If I manually lock or unlock the door (via either the inside knob or a code from outside), the status does not change on the A+ (Yale YRD240).  Similarly, if I manually turn on/off my binary power switch (Aeon Labs DSC24-ZWUS) the A+ doesn't seem to know about it.  But my door sensors and thermostat status change in the Web UI just fine (after a refresh, of course!)

MAYBE the power switch does not actively report changes to the A+, but I'd be willing to bet the door lock does.

[Oendaril]

I checked with my kwikset 910 locks and see a similar behavior, I think they already know about some of it:

Connect.Securifi.com: always states unlocked; can control locks and get status to locked/unlocked but if refreshed reverts back to unlocked.
local webui/router/app: Statuses match each other, but only updates triggered by these sources will cause the status to refresh. Locking or unlocking the door is not updating status.

[Schwartz]

For what it is worth I have a SmartThings hub and a Wink hub and both of them had trouble always showing correct lock status when my Kwikset and Schlage locks were paired to them. Wherever the fault lies none of the others were consistent either.

[sorphin]

For what it is worth I have a SmartThings hub and a Wink hub and both of them had trouble always showing correct lock status when my Kwikset and Schlage locks were paired to them. Wherever the fault lies none of the others were consistent either.

Possibly lack of a clean connection to the hub(s)? (aka low signal level due to line of sight)

[Oendaril]

I don't think that's why right now, as one of my locks is ~7 feet from the hub. My other z-wave controller (lynx 5100) successfully detected unlocks within 5 seconds about 95% of the time because it would auto disarm the alarm system when it detected a code unlocking the door.

[LGNilsson]

This is clearly an issue on our side.
We're still working on improving the lock stuff and we've contacted both Schlage and Kwikset to see if they're willing to help us out, but I'm afraid that the guy at Yale wasn't interested in talking to me at CES, so we don't have anyone to contact there. That said, we'll get this fixed and it's a high priority as we know how important locks are and that they can't be having issues like this.