Kwikset 888 and 910 locks keep receiving Lock/Unlock commands

Last night, my Kwikset 888 kept locking/unlocking.

dev:4832022-01-06 08:43:40.488 am infoBack Door Lock was unlocked via command [digital][6:4]
dev:4832022-01-06 08:43:37.105 am infoBack Door Lock was locked via command [digital][6:3]
dev:4832022-01-06 08:43:33.973 am infoBack Door Lock was unlocked via command [digital][6:4]
dev:4832022-01-06 08:43:30.654 am infoBack Door Lock was locked via command [digital][6:3]
dev:4832022-01-06 08:43:27.738 am infoBack Door Lock battery is 100%
dev:4832022-01-06 08:43:27.407 am infoBack Door Lock was manually unlocked [physical][6:2]
dev:4832022-01-06 08:43:21.177 am infoBack Door Lock battery is 100%
dev:4832022-01-06 08:43:18.141 am infoBack Door Lock is locked
dev:4832022-01-06 06:09:59.307 am infoBack Door Lock was locked via command [digital][6:3]
dev:4832022-01-06 06:09:55.874 am infoBack Door Lock was unlocked via command [digital][6:4]
dev:4832022-01-06 06:09:52.448 am infoBack Door Lock was locked via command [digital][6:3]
dev:4832022-01-06 06:09:49.151 am infoBack Door Lock was unlocked via command [digital][6:4]
dev:4832022-01-06 06:09:40.365 am infoBack Door Lock was locked via command [digital][6:3]

I have not updated to 2.3.0.124 yet.

I rebooted the hub last night. This morning, I rebooted the hub again, Excluded the lock, did a Factory Reset, re-included...and now it's doing the same thing. I had to switch the driver to something else to get it to stop. As I was reconnecting it to Webcore and such, it didn't start acting up again until I added it to Alexa, and allowed it to be unlocked by app. I'm going to reset it again and not add it to anything, and see what happens when I connect to Alexa again.

This morning

lock locked Back Door Lock was locked via command [digital] DEVICE digital 2022-01-06 09:41:25.663 AM PST
lock unlocked Back Door Lock was unlocked via command [digital] DEVICE digital 2022-01-06 09:41:22.622 AM PST
lock locked Back Door Lock was locked via command [digital] DEVICE digital 2022-01-06 09:41:19.620 AM PST
lock unlocked Back Door Lock was unlocked via command [digital] DEVICE digital 2022-01-06 09:41:16.660 AM PST
lock locked Back Door Lock is locked DEVICE 2022-01-06 09:41:13.657 AM PST
lock unlocked Back Door Lock was unlocked via command [digital] DEVICE digital 2022-01-06 09:39:54.825 AM PST
lock locked Back Door Lock is locked DEVICE 2022-01-06 09:39:51.004 AM PST
lock unlocked Back Door Lock was unlocked via command [digital] DEVICE digital 2022-01-06 09:39:27.152 AM PST
lock locked Back Door Lock was locked via command [digital] DEVICE digital 2022-01-06 09:39:24.033 AM PST
lock unlocked Back Door Lock was unlocked via command [digital] DEVICE digital 2022-01-06 09:39:20.961 AM PST

Anyone else having similar issues?

Definitely not! Interesting that it's a consistent 3 second delay. Did you by any chance take a look at the back door lock device and see what it's in use by? Any indications there? Of course if you disable the Alexa integration and the issue goes away I think you have your culprit, but that's kinda scary.

1 Like

I have a Kwikset 912 (Zigbee) and just reviewed my logs.. nothing but normal unlocking. Are you sure adding a lock to Alexa is a good idea?

Right now they are only controlled by Alexa and the Hubitat App. I even put a new Z-wave+ RF chip in the front lock that I bought back in July (Lazy).

I haven't connect them to anything else yet. I'll give them some time first. One thing I was wondering about, though, was the Plus connection.

Front Door:

  • deviceType: 3
  • zwaveSecurePairingComplete: true
  • inClusters: 0x5E,0x72,0x5A,0x98,0x73,0x7A
  • secureInClusters: 0x86,0x80,0x62,0x63,0x85,0x59,0x71,0x70,0x4E,0x8B,0x4C,0x5D
  • deviceId: 566
  • S2: 128
  • manufacturer: 144

Back Door

  • deviceType: 3
  • zwaveSecurePairingComplete: true
  • inClusters: 0x5E,0x72,0x5A,0x98,0x73,0x7A
  • secureInClusters: 0x86,0x80,0x62,0x63,0x85,0x59,0x71,0x70,0x5D
  • deviceId: 1345
  • S2: 128
  • manufacturer: 144

From what I know, the 0x5E command means Plus, and they are securely paired, but according to the Z-wave Details page, they are both at S0. Doesn't the S2:128 mean they should be S2?

@erktrek , the front lock has been connected to Alexa for years. The back lock has been connected since February.

No. S2 = 128 is S0 security.

0=no security
1=S2 unauth
2=S2 auth
3=S2 unauth + auth
4=S2 access control
128 = S0

It is a bit mask of security values:

2 Likes

Sorry I meant from a security standpoint.. not to mention giving Amazon the literal keys to your house. It's all in your level of comfort.. :grimacing:

No big deal. :slight_smile: I just meant that being connected to Alexa shouldn't have been the problem, unless Alexa changed somehow. I went ahead and disconnected them from her anyways...I tend to use the dashboard button to unlock them anyways.

1 Like

:grinning_face_with_smiling_eyes: - apologies I did not mean to give you a hard time.. I'm always interested in different use cases and the potential pitfalls. Also not a big fan of cloud stuff for the most part even though I use it..

The concern with the Alexa control is having an open window or a "vibration speaker" that can be stuck on a window and commands relayed to the Echo..

I just got one of these and am going to test - not sure how well it will work with double or triple pane glass so that's somewhat comforting. There have been reports of hacks using lasers beamed at the microphone input but that seems more like a lab trick than an actual IRL deal..

I've seen it done with a laser. And my wife and son share your concern. :wink:

That said, I created a virtual switch so I could open/close my garage (Zen17) with Alexa (Doesn't need a code that way.) However, you have to say "Turn on garage" instead of "open".

1 Like

It appears to be a Webcore problem. We shall see.

1 Like

I really like the WebCoRE interface. Very logical to the programmer in me and the debugging is great. However I have since moved on to Node-RED... :wink:

Do I need a raspberry pi to run that? I'm interested in trying it.

You can run it in docker if you want.. very easy to set up. Feel free to PM me if you want some assistance or have any questions!!!

I would also mention that even though it may appear to be crazy complicated in reality it's very very simple. You have to be careful not to overthink things too much.

Okay wanted to report back - using the above device and my android phone + sound recorder app - I was able to get Alexa to turn on/off my kitchen lights through a double pane window.. about 10 ft away :grimacing:

Make sure you are very careful about what you allow Alexa to control and also would recommend NOT allowing purchases via Alexa either...

The speaker itself is interesting but not very good otherwise..

Alexa and her friends of similar ilk (but different names)....
One modest step forward in convenience for man,
one giant leap backwards in privacy & security for mankind.

And to think we use to unplug "the one" modem from the mainframe at night for "access security" threat reduction. :zzz: :thinking:

1 Like

I've been meaning to put my Echo on a smart outlet and turn it off as necessary. Like when we are away from the house and maybe at night.

1 Like