Kwikset 914 - Hubitat registers that it was manually unlocked when it wasn't?

So I have a rule set so that if a door is unlocked in the middle of the night, I get a notification and my Google nest speakers also send out an announcement. Mainly for security purposes, since I have no kids to be strict about.

Anyways, last night I got a scare because it triggers at 3am that our door has been unlocked (see screenshot for log). Checked our cameras and nothing was outside or inside the house, so I checked the door and it was indeed locked. This happens a number of times before it just stops around 4am.

Has anyone seen this before? I've had this locked set up for a year and this has never happened. Not sure what the fix is, but for now I've removed the battery and will put it back after 10 minutes and hopefully it doesn't happen again.

I have 4 Kwikset locks, 2 x 914 and 2 x 916, in use for several years now without a single issue. Mine are all Zigbee, but I have never seen anyone post about issues with them. Are you using quality batteries in yours? I have taken to using Duracell alkaline batteries since it’s easier to judge battery life than with lithium batteries. The only other thing I could think would be a possibility is if the messages got bogged down in a queue (if the lock was indeed inactive at that time). Perhaps shutting down the hub, pulling power for a minute and restarting, since that is the only way to reboot the radios.
Also, in the events log, my locks all differentiate between being unlocked/locked physically or by digital command.

2 Likes

Just checked the batteries, I'm also using Duracell batteries. What's odd is that it is reporting the batteries are at 100%, when they've been in the lock for a few months.

If removing the batteries and replacing them doesn't work, I'll try out shutting the hub down!

In terms of the event log, mine also differentiates between digital and manual, it says "unlocked by admin code" when it is unlocked via code.

Side note: Looking further back into the logs, this seems to have been happening the past few days, but it happened during the day so I never got the notification/alert.

Thanks for the suggestion, I'll give it a shot!

A few scattershots...

What hub model and software version?

What does your Zigbee mesh look like? Any wired devices and/or dedicated repeaters?

My 910 models (I think are functionally the same as 914) re-pair easily, so that may be worth a shot.

Have you noticed the hub 'missing' any events? (Wondering if the lock is sending spurious events, or if they are simply queued and being sent whenever they 'break through.')

2 Likes
  1. Model is C-8, version is 2.3.6.146
  2. No dedicated repeaters, but I do have zigbee lightbulbs that as I use as repeaters
  3. If the other steps don't work, I'll try unpairing and re-pearing!
  4. No to 'missing' any events, all my other stuff seems to be working as expected

Good news is that it hasn't had the weird log events since, so I'm hoping a simple reset of the batteries was enough

Appreciate the further questions though, helps me troubleshoot it a bit more if I need to!

1 Like

You don't have to unpair it. (In fact, you don't want to unpair it. Unpairing will remove it from rules, dashboards, notifications, etc.)

Just follow the device instructions for pairing, and place the hub in pairing mode. (I think it's pushing the 'B' button 9 times for those locks, IIRC.)

2 Likes

Can you clarify if this is with the zigbee version or the zwave version of this lock?

The logs are definitely Zigbee (so if it appears to really be Z-Wave, something is way off :slight_smile: ).

1 Like

Much appreciated, I'll give it a shot later!

These are indeed zigbee. I believe all my stuff are zigbee, though I forget the reasoning as to why I decided on that vs zwave. It's been working out well though, this is the first "hiccup" so far

1 Like

On my phone, so I couldn’t see the logs ……

It’s very strange for them to still be reporting 100% battery. Are you seeing the battery reporting in the logs?

1 Like

Yup, I do see the 100% in the logs.

Looks like the issue is still happening. Gunna try replacing the batteries, if it still continues then I'll try the pair instructions from JB_TX and report back!

So an update:

  1. I did notice the lock was lagging behind in the logs when I manually unlocked and locked it. It wouldn't update the logs (and wouldn't trigger my notification).
  2. I have another 914 lock on my garage door that is working just fine, not sure what the difference is
  3. I actually did a factory reset on my front door lock (the one with issues) and re-paired it since it wouldn't be that hard to set everything up again. Unfortunately, still having the lagging issues and now I can't lock/unlock from the hubitat web page, but I can with my garage lock

I'm starting to think this might be an issue with the lock itself, which would suck because it's a couple months over the warranty.

EDIT: So it's doing the same thing where it's getting a barrage of "unlocked by manual" when it hasn't been unlocked and the state is constantly "unlocked" even though it is currently locked. Definitely going to call Kwikset and see if they have a solution

1 Like

If they don’t, then I wonder if a Kwikset Convert can be used as a fix. I have one of these, but can’t remember if it can be attached to the keypad. I’ll try to check it out later today if I have time. If not, maybe the board can be used. I’m assuming that they just reused the Zigbee board in the stripped down version.

Just an update so if anyone else has this issue:

I called Kwikset and they basically figured it was an issue with the board in the lock. I was a couple months out of warranty, but they sent me a replacement anyways. Super easy customer service (Was like a 10 minute call, not counting the hold time). Funnily enough, now that the replacement arrived I was looking at the logs and the issue stopped happening.

I'll be monitoring it again, but at least if it starts again (which I'm honestly expecting it to, eventually at least) then I'll have a replacement ready.

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.