Closed Zackptg5 closed 3 weeks ago
I was able to do this, just this morning with HA 2004.5.5... It just worked, when I powered on the lock I saw the notice in HA and the I adopted it using the code...
I have a single ESP32 bluetooth proxy and bluetooth is turned off on my system. Not sure if that helps... Now I just got to figure out why it's not showing up in the rest of HomeKit from the Apple side...
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.
The problem
I have 3 Aqara U100 locks and an M2 hub. Have a separate BLE usb device in my HA box which the hub and 2 of the locks all bind to homekit via HA without issue. However, one of my locks is too far away so I got an Atom M5 Stack as a bluetooth proxy via esphome addon/integration. The proxy device is literally right next to the lock so it's not a range issue but I'm getting the generic error 133
What version of Home Assistant Core has the issue?
core-2024.4.2
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
No response
Diagnostics information
logs_atom-bluetooth-proxy-305d64_logs.txt
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response