Door lock status not 100% reliable

[bwainscott]

Occasionally, and I don't really know when or why, the A+ reports the wrong status for the lock on my front door (Yale YRD240).  MOST of the time it is correct.  All my other sensors (including the door sensor on the same door) seem to report reliably.  The door is not far from the A+ -- about 40 feet and around one corner, with my zwave thermostat at the corner almost exactly in the middle (as if a relay was needed for such a short distance).

Anyway, just thought you might want to know, and am hoping this improves with future firmware updates.

In general, I'm very pleased with the A+ and looking forward to what is coming!

[Thirstymate]

I am having the same issue with the Yale YRD220ZW, except it never really reports the correct status.  Even when I look at the LCD interface on the Almond+, it always shows as "Unlocked", even when locked.  The cloud based services and Android app also report the status as unlocked always when able to connect to the router.  Other times, the app reports the router offline or says it can't connect to the sensor.  I've tried removing and re adding the sensor but still get the same issues.

[LGNilsson]

Are you both on firmware R066? These issues should be fixed in that firmware.

[bwainscott]

I am on 66. I THINK the problem happens when the door is operated manually. The most likely situation is that someone unlocks the door, comes in, then manually locks it. I think that the manual lock action does not get reported... it may happen too fast and get lost?  This is mostly speculation. I am away from home the next few days but will try to reproduce this next week. It seems to work correctly most of the time

[LGNilsson]

Hmmm, that was supposed to have been fixed in R066, I'l follow up with the software team.

[Mishakim]

I'll add another datapoint, I have three Yale YRD240-ZW deadbolts, and am on R066, and the status on the connect.securify.com is almost always wrong -- unlocked, when they are in fact locked. Local web UI is more reliable (checking just now via VPN, it says all are locked, while connect still says all unlocked). iOS app previously was blank for these locks, now says affirmatively that it can't update sensor data.

[The19th]

While I do not have a Yale (I have a Schlage 469NX with its own issues) I'd like to second Mishakim's observations:

LCD UI and Web UI are typically are the most reliable.
The status on connect.securifi.com will usually show unlocked regardless of physical state of the lock.
iOS app 1.0 showed no icon, but at least it showed a status (if I remember correctly)
iOS app 1.1 currently shows a prohibitory icon as well as the "Could not update sensor data" error message.

[k1m]

I have the Yale 210 YRD and it just doesn't report to the IOS app, it reports correctly on the almond itself, it needs to "check-in" when used through the cloud/web interfaces before it reports correctly.  It will not do any action the first time you hit the action button, it only checks in to see where the lock is at, it doesn't matter if it is a manual or motorized locking action having been last performed.

[Oendaril]

I've got two kwikset z-wave locks I bought back in 2012 and then bought a third one this year.  I am only getting the status updates when manually operating the lock on the new one, and not reliably getting the status otherwise for that door.  One of the older ones is ~8 feet from the router between one interior wall so it wouldn't be a matter of range to the best of my knowledge.  Are any of you also using the kwiksets?