Front door unlocked by itself this morning

Devices & Integrations Connected Things
1

I have a routine that when either my or my wife’s iPhone is arriving, the front door unlocks and several lights come on.

My wife and I were at work today when I got a text message that the front door unlocked. I have cameras all over, and Immediately checked for intruders. My 2 dogs were in their cages sleeping, and are right next to the front door. Anyone coming through that door would have woken them.

My wife is not liking that the front door unlocked by itself. I agree with her.

Could it be that the presence detection, now that it is working (thanks to JDRoberts) on her iPhone 6s Plus somehow triggered the event? She was about 20 miles away and I was about 30 miles away.

I looked at the logs and nothing appears to be amiss.

2

You should contact ST support and let them help review your lock/logs and see if they can determine a cause

https://support.smartthings.com/hc/en-us

1 Like
3

Here is the log. I don’t see anything that would point to why it unlocked.

Unlocked
Name Value
archivable true
data
{
“method”: “command”,
“lockName”: “Front door lock”
}
date 2018-01-08 10:20:45.645 AM CST (2018-01-08T16:20:45.645Z)
description Unlocked
deviceId 1fafe49a-0115-4c97-a4cf-37717324bb5f
deviceTypeId 89d413bc-0ec9-435f-8e52-a1eb60a86b65
displayed true
eventSource DEVICE
groupId f6f64263-f3dd-4f2f-9e55-2b59d8218372
hubId 18e4b8c6-461b-40a1-8376-eb7597069d1d
id e15eb330-f48f-11e7-bcbb-06fc1d6a493a
isStateChange true
isVirtualHub false
linkText Front door lock
locationId 975a2cc3-3c2e-4624-b855-f88ead4f0780
name lock
rawDescription catchall: 0104 0101 02 01 0140 00 1FF7 01 00 0000 20 01 0102FFFF000000000000
translatable false
unixTime 1515428445645
value unlocked
viewed false

4

I’m curious… What brand of Lock?

In general, I would not allow presence to trigger any unlocking events; though it’s more likely for Presence Sensors to temporarily report “away” (while still at home) than the other way around. Of course, in that scenario it could still trigger an unlock action when it returns to the correct state of “present”.

1 Like
5

This is a Kwikset lock. At exactly 10:20 am this morning the lock unlocked again. This was the same time the lock unlocked yesterday.

I have a Nest detector that is tied to a routine to unlock the door when the detector goes off. Nothing in the log for the detector looks amiss. I have removed this feature and will check tomorrow if the door unlocks at 10:20.

1 Like
6

You can look at the event logs for your lock in the IDE to identify the source of the unlock event/command.

1 Like
7

Here is the event log for yesterday at 10:20 am

Unlocked
Name Value
archivable true
data
{
“method”: “command”,
“lockName”: “Front door lock”
}
date 2018-01-08 10:20:45.645 AM CST (2018-01-08T16:20:45.645Z)
description Unlocked
deviceId 1fafe49a-0115-4c97-a4cf-37717324bb5f
deviceTypeId 89d413bc-0ec9-435f-8e52-a1eb60a86b65
displayed true
eventSource DEVICE
groupId f6f64263-f3dd-4f2f-9e55-2b59d8218372
hubId 18e4b8c6-461b-40a1-8376-eb7597069d1d
id e15eb330-f48f-11e7-bcbb-06fc1d6a493a
isStateChange true
isVirtualHub false
linkText Front door lock
locationId 975a2cc3-3c2e-4624-b855-f88ead4f0780
name lock
rawDescription catchall: 0104 0101 02 01 0140 00 1FF7 01 00 0000 20 01 0102FFFF000000000000
translatable false
unixTime 1515428445645
value unlocked
viewed false

Here is the event log at 10:20 am today

Unlocked
Name Value
archivable true
data
{
“method”: “command”,
“lockName”: “Front door lock”
}
date 2018-01-09 10:20:44.743 AM CST (2018-01-09T16:20:44.743Z)
description Unlocked
deviceId 1fafe49a-0115-4c97-a4cf-37717324bb5f
deviceTypeId 89d413bc-0ec9-435f-8e52-a1eb60a86b65
displayed true
eventSource DEVICE
groupId f6f64263-f3dd-4f2f-9e55-2b59d8218372
hubId 18e4b8c6-461b-40a1-8376-eb7597069d1d
id 0b3f4600-f559-11e7-9133-060b1608ab28
isStateChange true
isVirtualHub false
linkText Front door lock
locationId 975a2cc3-3c2e-4624-b855-f88ead4f0780
name lock
rawDescription catchall: 0104 0101 02 01 0140 00 1FF7 01 00 0000 20 01 0102FFFF000000000000
translatable false
unixTime 1515514844743
value unlocked
viewed false

I don’t see what is commanding the lock to unlock.

Here is a new entry on the log that shows a code was created. Neither I nor my wife did this

Added "Code 0"
Name Value
archivable true
data
{
“codeName”: “Code 0”,
“lockName”: “Front door lock”
}
date 2018-01-09 11:16:41.936 AM CST (2018-01-09T17:16:41.936Z)
description Added "Code 0"
deviceId 1fafe49a-0115-4c97-a4cf-37717324bb5f
deviceTypeId 89d413bc-0ec9-435f-8e52-a1eb60a86b65
displayed true
eventSource DEVICE
groupId f6f64263-f3dd-4f2f-9e55-2b59d8218372
hubId 18e4b8c6-461b-40a1-8376-eb7597069d1d
id dc547ec0-f560-11e7-818e-06cb5f8e121a
isStateChange true
isVirtualHub false
linkText Front door lock
locationId 975a2cc3-3c2e-4624-b855-f88ead4f0780
name codeChanged
rawDescription catchall: 0104 0101 02 01 0140 00 1FF7 01 00 0000 06 01 000001000435343232
translatable false
unixTime 1515518201936
value 0 set
viewed false

What could have created a code? Has my network been compromised?

Any help is welcome. We do use the presence detection so disabling it really isn’t an option.

Thank you

8

It looks like the event is coming from the lock itself.

I don’t think your network is compromised, you’ve either got a SmartApp (do you have SmartLocks from ST installed?) that is sending those code programming commands or maybe a ghost event being crossed with some other app/event. Some folks have seen this after a recent ST outage issue.

The simplest fix was to exclude the lock and repair it, this usually resets it. If it continues to happen have ST support look into the event log and trace back the source using those id’s above.

2 Likes
9

Thank you for taking the time to help. I will do as you suggest and keep an eye on the lock status.

On a side note, I checked the presence sensor logs and nothing looks amiss there either so I’m off to replace the batteries, exclude it from the network and add it back. I do not have Smartlocks installed, and was unaware of such an app.

Here are the presence sensor logs for those days

My wife’s iPhone 6s Plus

Date Source Type Name Value User Displayed Text
2018-01-09 4:24:17.130 PM CST
2 hours ago DEVICE presence present Lynn has arrived
2018-01-09 7:46:13.045 AM CST
11 hours ago DEVICE presence not present Lynn has left
2018-01-08 6:22:37.478 PM CST
1 day ago DEVICE presence present Lynn has arrived
2018-01-08 7:08:02.778 AM CST
1 day ago DEVICE presence not present Lynn has left

My iPhone 6s

Date Source Type Name Value User Displayed Text
2018-01-09 4:32:15.722 PM CST
2 hours ago DEVICE presence present Tom has arrived
2018-01-09 5:32:20.958 AM CST
13 hours ago DEVICE presence not present Tom has left
2018-01-08 4:31:28.605 PM CST
1 day ago DEVICE presence present Tom has arrived
2018-01-08 5:23:36.693 AM CST
2 days ago DEVICE presence not present Tom has left

10

I am going to hang my head in shame. My original thoughts were to just let this topic fade away, but decided to fess up and be a man.

I have a routine at 5:10 am that turns one living room light on at 50% brightness, and at 5:20 am it turns all the lights on and unlocks the front door. I leave the house right around 5:25 am. I do this because sometimes I snore and my wife ends up sleeping on the sofa. This routine is a gentle way to wake her up rather than all the lights coming on at once.

We have both been home for the last few days and this routine would wake her up if she was sleeping on the sofa. Since we were sleeping well past 5:10, I changed the 5:10 am to 10:15 am and (yep) the 5:20 am to 10:20 am. Being old, I forgot about this, and now that we are both going to work at the normal time, I neglected to change the times back. THAT is why the lock was unlocking at precisely 10:20 am every day.

Still doesn’t explain how it created a code of 0 but that isn’t as important.

I will take 20 slaps with a wet noodle. The lock was doing exactly what is was supposed to do.

Thanks to all that offered advice. I’ll slink over to the corner and be quiet for a while.

4 Likes
11

Yeah, go to the corner and… actually, don’t do that. A post like yours is incredibly helpful! We all forget things, miss things, do the right thing only to have it backfire on us later. We write routines that work in a context, then change the context but forget that the routine was dependent on it…

Thanks for putting it out there. Your post will help someone else.

4 Likes
12

One other safeguard is to set the routine to not run in Away or Night mode

1 Like
13

I agree with Glen 99 percent of the time the odd things that are happening are due to operator error (for each and every one of us…) finding and correcting those mistakes are often a challenge to solving problems and coming up with solutions.

I’m glad you figured out what was causing the odd behavior.

14

Good to hear because had I not got the follow up on this I would have literally forever remembered this post where a guy had his smart lock open up on him by itself and that would always be in my mind if I ever bought one or was talking to others about them.

I am still voting against having a smart lock open up based on a presence sensing. But if other people are happy with how it works then I’m not mad at anybody.