Deadbolt locked but iris doesn't know
0

25 posts in this topic

I've been having a random issue with our front door deadbolt.
Occasionally it seems that when we lock it manually, iris doesn't "get the memo".
For instance, this morning my wife and I both left at the same time. She locked the door behind her and I paused to verify it was, in fact, locked.
After we were both gone for about 10 minutes our away rule ran and set the alarm... I also have a rule that will lock the front deadbolt if it is unlocked when the alarm is set.
It seems that iris THOUGHT the door was not locked, and I received a notification saying that iris was locking the front door because it was unlocked when the alarm was set.
I have looked at my history, filtered by that particular device, and I see several instances over the last few days where it was unlocked more than once without a "locked" event between them (obviously you cant unlock a door that isn't already locked). Its almost like sometimes when it is locked manually, iris isn't notified.

I just tried something and got a strange result. From the web based interface I ran the "home" scene which also unlocks the front door... I looked at the history and it showed the front door was unlocked.
I then ran the "away" scene and received the notification that the deadbolt was going to be locked because the alarm was set... then I checked my log. It did not show an entry that the front door locked. I was in the web based interface, so I went to devices and it showed the front door deadbolt as "locking". After about 5 minutes it still showed as "locking", with no indication that it was locked in the log. I ran the home scene again and checked the log... it showed that it had been unlocked. Then I waited a minute or two and ran the away scene (again, received a notification that the deadbolt would be locked) and now the log shows the door was locked at that time.
 

Share this post


Link to post
Share on other sites

Had the exact same thing happen last night, it showed the door was unlocked when it wasn't. I just pulled the batteries, waited 10 seconds, plugged it back in, and cycled the lock open and closed manually and the status was correct again. For how long, we shall see.


Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

I'm only two weeks in to having a (Schlage) deadbolt on the system.  What you described is what I've been experiencing almost since it was installed. For the first few days, notifications were reliable. Now, more often than not, the notifications either don't occur at all, or come 15-20 minutes after the lock has been manually locked/unlocked.

Dan8785 likes this

Share this post


Link to post
Share on other sites

I have also seen where it can take 15 minutes or more for Iris to realize my lock did in fact unlock when asked to through the app so I cannot lock it again until it detects the unlock.  So I will only unlock it through the app if absolutely necessary since I don't want to rely on the person I'm unlocking it for to lock it again and I don't want the house to remain unlocked while I wait for Iris to detect the locks true state.  I moved one of my locks to my SmartThings system and unfortunately it wasn't any more reliable and I don't like relying on community created apps to set the codes in my lock or to send the codes in clear text to the SmartThings IDE from the Keypad so I moved the lock back to Iris.

Share this post


Link to post
Share on other sites

I've had the same thing going on with the Kwikset locks,  but to be honest with you I think I have the away scene set to lock the doors when the last one leaves - without really specifying not to if they are already locked. 
I'll have to check and see, but honestly I haven't really worried about it.

 

Share this post


Link to post
Share on other sites

Well, I first noticed this several months ago. My wife would be the last to leave and I would get a notification saying the door was being locked because the alarm came on.
I kept fussing at her about leaving it unlocked when she leaves, and she insisted that she had double checked and had, in fact, locked it upon leaving. Eventually I was able to verify this.
It seemed to get better for a while, but lately it has started up again.
It bothered me at first (I thought maybe it was somehow unlocking after we left), but now that I know it is actually locked but iris doesn't realize it, it doesn't bother me as much.
I like getting that notification to let me know someone forgot to lock the door, (and the fact that iris will then do it for me), but I have no confidence in its accuracy, so it really means nothing when I get it.

Share this post


Link to post
Share on other sites
59 minutes ago, awraynor said:

Same thing for my garage doors. Neither open nor closed is greyed out. Look through camera and fortunately it's shut. 

Similar to this?

Deadbolt.png     Deadbolt 2.png

Manually cycling the lock brought it back.

 

Share this post


Link to post
Share on other sites

17 days after installation, and my Schlage just disconnected. Manually cycling didn't bring it back. Followed the IRIS instructions, but even using the programming code didn't bring it back. Instructions said a factory reset was the next thing to try, which involves removing the cover and disconnecting the battery, then reconnecting the battery while pressing the front Schlage button. Did it, and I immediately got a notification that the deadbolt had reconnected to IRIS. However, it had reset to the default codes and said there were 0 people authorized with a pin code. Tried to authorize myself, but the IRIS app assumes you are already authorized and so it just had an option for adding a visitor. All buttons grey. Half hour later, and the buttons were functioning, but had to change the PIN through the programming code at the lock -- it didn't automatically read the IRIS PIN. I can't remember if that's how I had to do it originally, but last week I was able to change the IRIS PIN and it automatically changed the door PIN. Couldn't do that tonight.

Share this post


Link to post
Share on other sites

I'm glad I'm not crazy.  I got onto the forum today just to see if anyone else is having this happen.  I have the Schlage touch-screen deadbolt.  This issue seems to have started in the last few weeks for me.   I never recall having this issue in the past.  It is annoying, especially since I happen to have company staying at my house right now so I'm paranoid that the lock wasn't locked properly...  

Share this post


Link to post
Share on other sites

Had this same problem with my Schlage and found that it seems to be very bad at sending and receiving signals. I tested this by moving my hub to within 10 feet of the lock and have had no problems. I have been meaning to test this using a range extender plugged in next to the door to see if that would solve the problem since most people can't get their hubs close to the door.


Sent from my iPad using Tapatalk

Share this post


Link to post
Share on other sites
2 hours ago, klawtrax said:

Had this same problem with my Schlage and found that it seems to be very bad at sending and receiving signals. I tested this by moving my hub to within 10 feet of the lock and have had no problems. I have been meaning to test this using a range extender plugged in next to the door to see if that would solve the problem since most people can't get their hubs close to the door.


Sent from my iPad using Tapatalk

Factory resetting the lock and then re-pairing next to the hub seems to work as well.  I removed the lock from the door and set it next to hub during the pairing process and then re-installed the lock before rebuilding the Z-wave network.

Share this post


Link to post
Share on other sites
3 hours ago, Vettester said:

Factory resetting the lock and then re-pairing next to the hub seems to work as well.

So are you now getting consistent, accurate and timely notifications? Mine seems to be making too many "hops" through my Z-wave mesh even after multiple rebuilds. Status does usually get reported, usually 10-15 minutes after the status changes. However, notifications almost never work.

Share this post


Link to post
Share on other sites

I tend to thing this is a Iris problem more than a lock issue.  I have switched two of the three locks I have over to Smart things.  I keep meaning to do the last one but just haven't got around to it.  Since the free plan now has rules and scenes, it hasn't been a big deal.  The lock is on the front door and we don't use it that often, so it stays locked most of the time. 

The two locks on ST lock and unlock almost immediately when ever I activate the routines to do so.  The one on Iris, the one time I hit the scene just to make sure it worked it did nothing.

Share this post


Link to post
Share on other sites
So are you now getting consistent, accurate and timely notifications? Mine seems to be making too many "hops" through my Z-wave mesh even after multiple rebuilds. Status does usually get reported, usually 10-15 minutes after the status changes. However, notifications almost never work.

I don't use notifications for my locks, but I'm receiving status changes in less than 15 seconds and all of my rules and scenes are triggering on time.
pavalov likes this

Share this post


Link to post
Share on other sites

I tried moving my locks to SmartThings around December with new batteries but they weren't any better there, in fact my front lock was worse than it had been on Iris before moving it, so I'm guessing Terminal's SmartThings network and mine differ in how many devices the locks connected to between the hub and lock.  Also in the IDE I could see my pins being sent in clear text from the 3rd party lock manager so I decided to move them back to Iris.  After moving them back I had to remove my Yale lock from the garage door and put it right next to the hub when removing it and re-pairing it then I replaced the batteries and it is working much better.

Share this post


Link to post
Share on other sites

Iris is aware of this issue. I had the same problem and spent a lot of time on the phone. 

 

In the end, factory resetting and repairing the locks right next to the hub, then running the Zwave tool has made it work almost perfectly (again). According to tier 2 it's a priority fix they are aware of. 

Share this post


Link to post
Share on other sites
On 5/10/2017 at 3:07 PM, CTMaineah said:

In the end, factory resetting and repairing the locks right next to the hub, then running the Zwave tool has made it work almost perfectly (again). According to tier 2 it's a priority fix they are aware of. 


That's because doing this process updates the firmware on the lock. You aren't aware this is what's happening, but if you check the lock's firmware on the Gillian's portal before and after the process you'll see that it changes.

***Edit... It's the device driver that's updated not the firmware.

CTMaineah likes this

Share this post


Link to post
Share on other sites

Good little tid bit! Much appreciated. I also learned a lot about z wave devices and how they can screw up your network if they aren't mapped right or they connect to an intermediate device which goes down.


Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

That's because doing this process updates the firmware on the lock. You aren't aware this is what's happening, but if you check the lock's firmware on the Gillian's portal before and after the process you'll see that it changes.

Lol the firmware on my lock says N/A


Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites
1 hour ago, accessdenied79 said:


Lol the firmware on my lock says N/A

Correction.... it's the device driver that's updated.

"devadv:driverversion":"1.1"

Share this post


Link to post
Share on other sites
Correction.... it's the device driver that's updated.
"devadv:driverversion":"1.1"

Mine shows 1.0, so I am going to do mine. Go figure it is offline anyways. Lol.


Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

Unpaired mine, factory reset, and re-paired it and now my driver is 1.1. Seems like it would do that automatically. For those doing this, don't forget to add your users back to the lock. Haha.


Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
0