August Smart Lock Gen2 constantly sending "unlocked" signal to HASS

Configuration
1

47
47752×984 138 KB

Can anyone explain to me why exactly this would be happening with my August Smart Lock Gen2? It happens literally all day and night. I have a Connect I’m using as well. Only thing I can possibly think of is that the Connect keeps dropping signal or going into an “unknown” state and when it comes back online it defaults to sending an “unlocked” signal until it can determine that it is in fact locked? Just a theory. But I also have the settings in the August app set to notify when the Connect goes offline and I haven’t been receiving notifications that this is happening. I’ve only been using HASS for a couple of weeks and just getting around to setting automations when I realized this was happening, so not sure if it has been doing this since I set up the integration or not. I’m assuming it has been.

If someone could shine I light on this I would appreciate it. Haven’t been able to find much documentation about this happening to anyone else.

Also, attaching the automations I have set up just to make sure I didn’t FUBAR those.

33 50 10

Thank you!

2

I have the same issue…
The problem is that the August loses connectivity to the network. When this happens, for whatever reason, it appears as an ‘unlock’ event.

Also, just wanted to let you know that you can actually pull the user that is performing the unlock / lock as an attribute, or use it in notification data templates:

  - service: notify.pushover
    data_template:
      message: "{{ state_attr('lock.front_door', 'changed_by') }} disarmed alarm via lock code"

That allows you to do cool stuff like take actions based on WHO unlocked the door

3

I had a feeling it had something to do with losing network connectivity. Is there anyway to prevent this? I’ve been considering dropping the direct integration and going through SmartThings hub and then reintegrating SmartThings and see if all those ‘unlocked’ notifications make it through that. Might try that later or try to pull it in through HomeKit.

And thanks for the tip on the ‘who’ unlocked it. Didn’t know I could do that.

4

Seeing something similar on my end and had a hunch it was network related. Figure out any fix or workaround?

I just don’t understand why it loses network it treats the re-connection as an unlock/lock action. Is this something that can be changed?

5

I posted this in another thread on this board.
https://community.home-assistant.io/t/august-lock-keeps-randomly-showing-unlocked-when-its-not/

I recently installed the August Smart Lock Pro + Connect and am having the same issue.
I have a notification set to alert me via Join when the state changes from ‘unlocked’ to ‘locked’ and another when the state changes from ‘locked’ to ‘unlocked’

The lock hasn’t been touched for over 20 hours but I’ve received 3 sets of unlock and lock alerts.
Each time I received the alerts, I checked the lock and confirmed it was locked and the app shows that it was locked as well.

The signal strength of the Connect is strong

Screenshot_20191230-111150_August
Screenshot_20191230-111150_August496×582 13.2 KB

Also, when I checked the status of the Connect module, it doesn’t go offline.

Screenshot_20191230-111150_August_connect

6

When the August Connect loses connectivity to your wireless, or the lock, HA sees it as “unlocked”.
If you fix the connectivity problem, it’ll stop happening.

Keep in mind the Connect is connecting to your Wi-Fi and that seems fine, but the Connect has to also be within BT range of the lock itself. Try relocating the Connect closer to the lock, preferable with unobstructed line-of-sight.

7

The Connect is only a few feet away so there’s nothing I can do about the BT connectivity. The Wifi seems fine.

It might be better if once it reconnects, it should confirm the status before simply returning “Unlocked”

8

You could build a template sensor that sets “Locked” when it’s either “Locked” or “Unknown” and “Unlocked” otherwise…

9

Would you please check to see if its fixed once new version is released with this commit?