HA can't manipulate August Locks

[awshirley]

The problem

HA can't lock/unlock my locks any longer. If I use the app on the lock, HA will show the status change and that's all. If fact when I start HA now, the locks are greyed out.

And it does this with the current release and the new wake code I've been testing.

What version of Home Assistant Core has the issue?

2022.2.6

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

August

Link to integration documentation on our website

https://www.home-assistant.io/integrations/august/

Diagnostics information

Nothing in the logs.

Example YAML snippet

N/A

Anything in the logs that might be useful for us?

N/A

Additional information

N/A

[probot-home-assistant[bot]]

august documentation august source _{^{(message by IssueLinks)}}

[probot-home-assistant[bot]]

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (august) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

[bdraco]

Let's see what else august changed today as they continue their migration to using CloudFlare

Please enable debug logging and email me the results to nick@koston.org. Please don't post it publicly though.

Add the following to configuration.yaml, and restart:

logger:
  default: info
  logs:
    custom_components.august
    homeassistant.components.august: debug
    yalexs: debug
    pubnub: debug

[bdraco]

Thanks for the log. The api is reporting the lock status as unknown for all of the locks. How is it displaying in the august app? Can you send a screenshot?

"LockStatus":{"status":"unknown",<SNIP>,"isLockStatusChanged":false,"valid":true,"doorState":"unknown"}

[awshirley]

Looks like I'm still having the same issue with the Connects you sent me. I'm running HA core core-2022.3.3

[bdraco]

I'm starting to thing the problem is with the wifi network.

• How far are the connects from the nearest access point
• If you have multiple access points, are the connects locked to the nearest one
• What is the DTIM period on the wifi SSID?
• Which vendor are using using for the access points + firmware version

[awshirley]

Nick,

1.  The connects are within 20 - 25 ft of the AP.

2.  I only have one AP.

3.  DTIM is 1

4.  The AP is a Netgear Nighthawk AC1900 running the latest version of DD-WRT

Thanks,

Andrew Shirley

---- On Fri, 11 Mar 2022 20:01:13 -0600 J. Nick Koston @.***> wrote ----

I'm starting to thing the problem is with the wifi network.

How far are the connects from the nearest access point

If you have multiple access points, are the connects locked to the nearest one

What is the DTIM period on the wifi SSID?

Which vendor are using using for the access points + firmware version

— Reply to this email directly, https://github.com/home-assistant/core/issues/66501#issuecomment-1065787471, or https://github.com/notifications/unsubscribe-auth/AEHJG5UNWDRUKGCNS76S5ETU7P3GTANCNFSM5OKWRZCQ. Triage notifications on the go with GitHub Mobile for https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.

[bdraco]

I added diagnostics to the integration earlier this. Hopefully in next month's release the data will show something useful that will help with the troubleshooting

[awshirley]

What is needed to activate the diagnostics?

---- On Wed, 16 Mar 2022 16:04:23 -0500 J. Nick Koston @.***> wrote ----

I added diagnostics to the integration earlier this. Hopefully in next month's release the data will show something useful that will help with the troubleshooting

— Reply to this email directly, https://github.com/home-assistant/core/issues/66501#issuecomment-1069630786, or https://github.com/notifications/unsubscribe-auth/AEHJG5QH5ZCVEISRGZLY5LDVAJEFPANCNFSM5OKWRZCQ. Triage notifications on the go with GitHub Mobile for https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.

[bdraco]

Once 2022.4.0 is released, you'll be able to download diagnostics from the integrations screen.

[awshirley]

Cool!  I can't wait to try it.

---- On Thu, 17 Mar 2022 19:59:31 -0500 J. Nick Koston @.***> wrote ----

Once 2022.4.0 is released, you'll be able to download diagnostics from the integrations screen.

https://user-images.githubusercontent.com/663432/158917543-bd180edc-794c-4098-9508-9c468cdfb59b.png

— Reply to this email directly, https://github.com/home-assistant/core/issues/66501#issuecomment-1071914841, or https://github.com/notifications/unsubscribe-auth/AEHJG5TOB5HYHIBEYS6LWR3VAPIPHANCNFSM5OKWRZCQ. Triage notifications on the go with GitHub Mobile for https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.

[chickenxcouncil]

It looks like this is still an issue, at least for me. I had no issues until I did an upgrade in HA. I went from core_2021.8.6 to core_2022.3.8 and thats when the problem began. I have since been updating as new updates come out but none seem to solve the problem. I will say that my access point is near the device but it is just outside of the "good" range so it will occasionally disconnect but it is usually connected when this problem is occuring.

[Br3nda]

still an issue today. The status changes to "locking" or "unlocking" but the lock hardware itself doesn't react.

[bdraco]

Please provide diagnostics and information about affected locks. August has changed the api quite a bit and trying to keep the older locks (and bridges) working takes a lot of guess work since they don't document anything

[hufftheweevil]

I use Node-RED for my August integration, so I can't speak for HA specifically. But I recently created a new module that seems to be working well for me. I've included some consolidated documentation that may help others in trying to understand the current API: https://github.com/hufftheweevil/august-api/blob/main/endpoints.md https://github.com/hufftheweevil/august-api/blob/main/definitions.md

[bdraco]

I use Node-RED for my August integration, so I can't speak for HA specifically. But I recently created a new module that seems to be working well for me. I've included some consolidated documentation that may help others in trying to understand the current API:

https://github.com/hufftheweevil/august-api/blob/main/endpoints.md

https://github.com/hufftheweevil/august-api/blob/main/definitions.md

Do you have any insights into the query params on the endpoints as that's usually the endless source of problems for us since specific models require different incantations of query params

[hufftheweevil]

Only what's listed in the Data Keys column of each table in the definitions. I've only worked with the latest version of the Wifi lock, so I can't speak on older versions. Sorry I can't be more help.

[bdraco]

Thanks. The problem here is likely we have the params wrong for a specific bridge model or lock. AFAIK There isn't a way to figure it out without trapping the traffic from the app when you actually have one on your account so the only way I've been able to fix these cases is to have someone share owner access to the lock that doesn't work and figure out what's different. Unfortunately that takes a lot of time and someone willing to share owner access so I haven't been able to keep up with all the combinations (I can't even get people to post diagnostics most of the time)

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[bdraco]

No stale

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[alpual]

I believe I'm still having this issue, too.