Homekit Device - Lock Unable to Control Device

WyspSedai commented 1 week ago

The problem

"PDU status was not success: Insufficient authorization"

I have two Yale Assure Lock 2 devices that I would like to use the Homekit Device Integration to manage. I am able to successfully add the devices however I cannot control them due to the error stated above.

I'm able to use the Yale Bluetooth Integration with no errors, however I keep having to reautorize the devices. I have bluetooth proxies connected and have had otherwise zero issues with any other bluetooth related functions.

Please advise

What version of Home Assistant Core has the issue?

core-2024.5.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Homekit Device

Link to integration documentation on our website

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

Diagnostics information

homekit_controller-3fc08fb649406a43be9bce96d871fae3-LF000Q8-fa7eb126f482ea2dc2d9be9782a8f63a.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Failed to call service lock/unlock. 98:1B:B5:68:F8:81: PDU status was not success: Insufficient authorization (3)

Additional information

No response

home-assistant[bot] commented 1 week ago

Hey there @jc2k, @bdraco, mind taking a look at this issue as it has been labeled with an integration (homekit_controller) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `homekit_controller` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign homekit_controller` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

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

bdraco commented 1 week ago

HomeKit needs a an additional key which is vendor supplied. There is no way to get this key since it is fed in from the August or Yale app on an iOS device.

Instead of pairing with HomeKit, unpair from HA, pair to an iOS device, setup the august integration so it can keep the key up to date, and use https://www.home-assistant.io/integrations/yalexs_ble/

If you still have trouble, create a new owner account in August, and set that up in HA to feed the keys to yalexs_ble so you won't have an iOS device logged in that is rotating the key for the secondary owner account since only HA will be using it.

home-assistant / core