We are 3000 miles away from our Vera unit so I can’t physically test it now.
Our last guests left the deadbolt unlocked and we had someone else who is technically challenged go Lock the door for us. The door can not be physically opened but the state on findvera did not change to LOCK.
I can remotely change the status on FindVera back and forth from LOCK to UNLOCK etc. I’m guessing that our helper turned the deadbolt far enough that the door can’t be opened but not far enough for the cams to register if the door is unlocked or locked? Does this make sense and can anyone verify this with their schlage deadbolt. Thanks in advance!!
Just took the laptop downstairs and tried a few things…
From the inside, if I throw the lever so its at 12 o’clock, the deadbolt sticks out enough
to lock the door, but it registers as open.
From the outside, if I push the top botton and rotate enough for the bolt to start to engage
enough to lock the door, but not fully rotate, it
and finally if i tell the lock to unlock from vera , but dont throw the bolt in time from the
outside it also shows as unlocked. However it does change state to lock if I start
over again and complete a lock cycle properly.
this is all using vera2/ui3 but will probably apply to all others. I guess since the bolt
is not motorized it can be fooled (or is it better to say confused). Will be interesting
to see what others find.
I have found that with my deadbolt, if I have the lock physically locked and then go into Vera and operate the lock using the buttons (either one), then the lock will make bolt-throwing sound and someone at the lock would have an opportunity to turn the lock from the outside. If you do not physically operate the lock in the short window, the button press in Vera changes the state to unlocked and stays there, even though the lock is and always was physically locked.
It is a bug that I reported and was supposed to be fixed in the new firmware .991, I’m not sure if it is fixed yet but MCV is aware of it.
edit: doesn’t look like it was fixed in .992, I am trying it now
It is disappointing to hear that the even when the bolt is securely positioned in the lock or unlock position that it’s state can be changed incorrectly with VERA.
I have .979 now and with older releases I don’t think you were able to artificially change the state. We originally installed the lock with the cams in the wrong position and we had the state reading unlock for months since we are so far away. I know I clicked on lock in Vera and it would not change to the LOCK state.
I hope this issue is fixed. The status indicator of LOCK and UNLOCK is worthless if it can be artificially forced with VERA. We were planning on adding 3 more schlage deadbolts to our vacation home to monitor all the doors with VERA but I’m no longer sure it is worth it.
It is good to hear that it worked properly at some point. I got my Vera and lock late last year and I can’t remember its status ever working correctly in Vera when using the buttons. I was told it would be addressed in the latest release, but I’m on 1.1.307 (UI3) now and it isn’t working correctly.
Hopefully they can figure this out soon as it can be a security issue, especially if your are primarily using Vera remotely and don’t “know” the door is locked.
I’m sorry to hear about the trouble with the deadbolt. The status of the lever lock is reported correctly whether it’s changed remotely or at the lock itself. If it didn’t, that might be the straw that breaks the camel’s back for me. I’d probably give up on Vera, what with all it’s crazy, unpredictable, flaky behaviors.
MCV needs to fix the deadbolt problem as a top priority.
I have noticed this as well. I have one Schlage deadbolt and one lever.
I have tested both the MCV v 1.xx software as well as SQRemote (which as I understand it is interfacing with Vera so it may simply be obtaining data from the Vera unit.
The lever lock always reports correctly, but the deadbolt is just a toggle. The actual position of the deadbolt does not affect the status in Vera or SQ Remote.
Unless you go and physically throw the bolt, then Vera correctly reports. AFAIK, the cam in the lock is working correctly with Vera, I think it is something simple like the button in the UI just needs to not change state from presses/clicks and only report status based on cam position. If it was that easy they would have fixed it by now though.
That is a good suggestion Les, but I guess the lock worked correctly at some point in Vera. It just looks like such an easy fix, just kill the button’s status change based on presses/clicks.
I am quite certain that my deadbolt lock worked as expected on earlier versions of Vera’s UI2. At some point, that functionality was ‘broken’, although I can’t say when.
The problem is, I had no idea it even ‘broke’, until one day I called my wife and told her to lock the front door (after checking on the house remotely), and it turned out that the lock was already locked.
As reported by others, the lock state DOES report correctly as long as you don’t try to control it via Vera. Manual lock and unlock reports properly. Press the ‘unlock’ button on Vera, and the lock state is incorrect until another manual lock and unlock occurs.
-Robert
Best Home Automation shopping experience. Shop at Ezlo!