Last night around 8pm I get a panicked call from my parents. WebCoRE was sending them messages that their front door was unlocked, however it was actually locked. I dug into it and found that at 7:57pm, a user got home, and unlocked the door via code. Since that time, the Lock and Smartthings apparently aren’t fully communicating as the lock still thinks it’s unlocked even though it’s currently locked. Therefore, WebCoRE was functioning properly on unlocked notifications since ST thinks the lock is unlocked, but it isn’t.
I am using the @RBoy Universal DT Handler that they bought and just updated them to the latest revision today, with no change. I have also tried a Z-Wave repair with no luck.
Any ideas before I go ahead and exclude/include the lock and have to reconfigure the entire thing all over again? Also to be noted, the batteries are reporting 64% and the hub has been rebooted as well.
They’ve had it installed for years. It’s to be noted that when I wrote the OP, through the IDE, it was showing “ACTIVE” however “Last Activity” reported 16 hours ago. Now, it’s showing INACTIVE with the last activity as of an hour ago. I will give changing the batteries a shot. Perhaps due to the wicked cold temps here, the batteries are shot.
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
#4
For this lock that’s pushing the lower limits. It should be changed at 75% to optimal operation.
Also note that there have been major platform problems yesterday and today affecting many users, but not all. It’s just really hard to troubleshoot anything right now. You can go ahead and change the batteries, but I wouldn’t do anything major until the platform issues settle down.