Homekit status August Smart lock changing without change

Configured my August lock 3rd gen with Connect yesterday and set it up with HASS. Also added it to Homekit through HASS (bluetooth is unable to reach from my AppleTV to the lock).

Yesterday evening I then locked the door (it was unlocked) through a scene in Homekit. From Homekit I then got the notifications:
Front door locked
Front door unlocked
Front door locked.

Looking in the logs from HASS, I can see entries from the HASS homekit component:
“Set state to 1” for the front door.
Four seconds later a new state that the front door is locked
About 40 seconds later a new state that the front door is unlocked
And about 1 min 30 after that that the front door is locked again.

2018-10-01 22:23:32 DEBUG (Thread-10) [homeassistant.components.homekit.type_locks] lock.front_door: Set state to 1
2018-10-01 22:23:36 DEBUG (MainThread) [homeassistant.components.homekit.accessories] New_state: <state lock.front_door=locked; changed_by=Erik Hendrix, battery_level=100, friendly_name=Front Door @ 2018-10-01T22:23:36.719197-06:00>
2018-10-01 22:23:36 DEBUG (SyncWorker_0) [homeassistant.components.homekit.accessories] lock.front_door: Updated battery level to 100
2018-10-01 22:23:36 DEBUG (SyncWorker_15) [homeassistant.components.homekit.type_locks] lock.front_door: Updated current state to locked (1)
2018-10-01 22:24:16 DEBUG (MainThread) [homeassistant.components.homekit.accessories] New_state: <state lock.front_door=unlocked; changed_by=Erik Hendrix, battery_level=100, friendly_name=Front Door @ 2018-10-01T22:24:16.550381-06:00>
2018-10-01 22:24:16 DEBUG (SyncWorker_10) [homeassistant.components.homekit.accessories] lock.front_door: Updated battery level to 100
2018-10-01 22:24:16 DEBUG (SyncWorker_15) [homeassistant.components.homekit.type_locks] lock.front_door: Updated current state to unlocked (0)
2018-10-01 22:25:43 DEBUG (MainThread) [homeassistant.components.homekit.accessories] New_state: <state lock.front_door=locked; changed_by=Erik Hendrix, battery_level=100, friendly_name=Front Door @ 2018-10-01T22:25:43.690289-06:00>
2018-10-01 22:25:43 DEBUG (SyncWorker_2) [homeassistant.components.homekit.accessories] lock.front_door: Updated battery level to 100
2018-10-01 22:25:43 DEBUG (SyncWorker_18) [homeassistant.components.homekit.type_locks] lock.front_door: Updated current state to locked (1)

Looking at the history in the August app, it is not showing anything about lock/unlock/lock.
And just now, as I was checking the August app I got notifications from HomeKit that the door was unlocked, and then locked again. Yet at no time did I unlock/lock the door here:

2018-10-02 07:56:48 DEBUG (MainThread) [homeassistant.components.homekit.accessories] New_state: <state lock.front_door=unlocked; changed_by=Erik Hendrix, battery_level=100, friendly_name=Front Door @ 2018-10-02T07:56:48.694840-06:00>
2018-10-02 07:56:48 DEBUG (SyncWorker_5) [homeassistant.components.homekit.accessories] lock.front_door: Updated battery level to 100
2018-10-02 07:56:48 DEBUG (SyncWorker_4) [homeassistant.components.homekit.type_locks] lock.front_door: Updated current state to unlocked (0)
2018-10-02 07:57:51 DEBUG (MainThread) [homeassistant.components.homekit.accessories] New_state: <state lock.front_door=locked; changed_by=Erik Hendrix, battery_level=100, friendly_name=Front Door @ 2018-10-02T07:57:51.780791-06:00>
2018-10-02 07:57:51 DEBUG (SyncWorker_14) [homeassistant.components.homekit.accessories] lock.front_door: Updated battery level to 100
2018-10-02 07:57:51 DEBUG (SyncWorker_15) [homeassistant.components.homekit.type_locks] lock.front_door: Updated current state to locked (1)

Anyone any ideas why this is happening and better, how to fix it? :slight_smile:

The looks seem to indicate that the change came from Home Assistant. To be sure, can you update your config and reproduce the issue:

logger:
  default: warning
  logs:
    homeassistant.components.homekit: debug
    pyhap: debug

Please post the log afterwards.


Just for me to understand your setup better: The August Look is paired with Home Assistant and to interface with it in the Home App you’r using the homekit component, right?

Hey,

I’ve got debugging turned on and will post when it happens again.

Yes, August lock is paired with Home Assistant, and Home Assistant is paired with Homekit. Using the Home app on my iPhone to run the scene.

Just wondering what you found with this… I set up html5 notifications on Wednesday and for the last 2 days I am getting constant notifications that the door was locked and u locked, yet August history shows no change unless it is a real one, so I’m not really sure why HA is reporting the state changes. I could see if it was losing connection to the August connect and showing Unavailable, but it’s not. I had a constant ping from my PC on the same network to August connect overnight and it doesn’t look like it’s dropping, just looking for some ideas to get this to be more reliable.

To be fair, haven’t even looked at this anymore as it hasn’t happened.

In my case it wasn’t HASS reporting but rather HomeKit (which was getting the information from HASS). It sounds to me that you are receiving it from HASS instead.

What version of HASS are you running?

I’m on the latest non-beta version (updated before bed last night). It happened multiple times overnight again but I just don’t know where the problem is coming from. I’m debating re-adding the component.

I doesn’t look like a HomeKit error to me, considering the as I understand it the lock is paired with Home Assistant. I would consider readding the lock or locking for similar error descriptions unrelated to HomeKit.

I decided not to purchase the Connect. I just use the Z-wave with HASS and it works 80 percent of the time lol. I went ahead and added the lock to homekit of my GF tablet so that it would communicate through bluetooth. Now my automation triggered Zwave unlock AND the bluetooth unlock. Now im at 100 percent lol

My issue is definitely not Homekit, this was the only/closest thing I could find as far as someone else having my same experience. I re-added the lock component and it’s still going crazy. Within the August app, it doesn’t show any state changes at these times, so it’s only happening within Home Assistant. Sadly, I have no idea how long this has been happening either because I just recently set up “lock state” based alerts and automations. The worst part, is we go out of town a lot and we have friends and family check up on the house. Since I have an alarm system set up within HA, I wanted to use the state of the lock to disarm the alarm and then send me a picture, but at this point, I get these fake positives all day (and night). I’ll just change my automations around to fix this and rely on the August app for the true notifications for lock/unlock states. Thanks guys

Can you add the following in your configuration.yaml:

 logger:
   default: warning
   logs:
     homeassistant.core: debug

You might already have logger in there, main line is to include debug for the core component. That will still result in quite a bit of information going into the logs.
When you then notice the false notification, check in the logs around that timeline for entries similar to:
[homeassistant.core] Bus:Handling &lt;Event state_changed[L]: entity_id=lock.

Here is an example of one of those entries for my front door:
[homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=lock.front_door, old_state=<state lock.front_door=locked; changed_by=Erik Hendrix, battery_level=96, friendly_name=Front Door @ 2018-11-02T09:33:18.689934-06:00>, new_state=<state lock.front_door=unlocked; changed_by=Erik Hendrix, battery_level=96, friendly_name=Front Door @ 2018-11-02T09:37:56.228264-06:00>>

Do you see any errors being reported in the HASS log file?

Erik, did you ever end up resolving this? I just installed 3 August locks and am experience the same thing.

This has been a while to honestly do not recall anymore. However, what I ended up doing is getting a ZWave adapter, connecting it to my Home Assistant and then adding August lock to my ZWave. It’s been working fine for quite a long time now.
I expose my lock to HomeKit from Home Assistant then.

Ah ok. Thanks for letting me know!