-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bluetooth - eve motion v1 pairing issue #76380
Comments
homekit_controller documentation |
Hey there @Jc2k, @bdraco, mind taking a look at this issue as it has been labeled with an integration ( |
I'm seeing the same issue with the Eve Weather outdoor sensor (v1, no screen).
|
I updated the Eve Weather (2015) firmware with the Eve app to 2.1.2 (809) and then tried again in Home Assistant (after unpairing/resetting the device). Same error. |
Seeing the same issue with my eve motion as well. Eve Water Guards work fine. |
2022.8.5 won't fix it, but it should give a better error which might help figure out whats wrong. |
It could be Jc2k/aiohomekit#135 but hopefully not since that one is unfixable without a kernel/bluez change |
Just thought I would resubmit the log after performing a fresh install of 2022.8.5, bleak and aiohomekit debug. 2022-08-16 17:01:43.628 DEBUG (MainThread) [aiohomekit.controller.ble.discovery] Eve Motion C11E (EB:E6:CB:BB:A0:52): Ensure connected with device EB:E6:CB:BB:A0:52: Eve Motion C11E; rssi=-48 |
It sure looks like Jc2k/aiohomekit#135 as it appears bluez can't resolve the services on the device.
|
bluez/bluez#316 These issues look related |
Can you try 2022.9.x beta? I have an eve motion v1 pairing successfully on that version |
I have an Eve Energy (firmware: 2.1.2) and I am getting the same error on 2022.9.0 |
I have successfully paired Eve Energy, Room, Thermo but there is something specific with Eve devices. I have 4 Eve Thermo that I can pair but not always from first try. My setup: HA 2022.9.4 in kubernetes with Bluez 5.65 on host (Ubuntu Jammy) and 5.64 in container |
I got the same issue on 2022.9.4 Traceback (most recent call last): |
It is strange it works fine sometimes. |
That's super annoying right? Unfortunately there isn't an api to tell bluez to try to resolve services again so we are stuck on this one. |
I have tested with a macos install and it works perfectly. I gave up on BlueZ, although the latest kernel 5.19 made the pairing process a bit better still after a while the devices would go undetected. Now the issue I have is finding a long range bluetooth adapter compatible with mac. Any ideas? Thank you! |
We added some retry logic to try again if the service resolution fails in 2022.11.x. That might help but it really should be fixed at the bluez level as this is only a workaround for that |
Thank you for continuing to keep an eye on the problem even though the issue is with a dependency. Hopefully it will get fixed at the bluez level someday… |
The problem
When trying to pair home assistant with a eve motion v1 (HomeKit motion sensor) I am getting a message "An unhandled error occurred while attempting to pair with this device. This may be a temporary failure or your device may not be supported currently."
I first tried on my production system then performed a fresh install on a RPI4 4GB 64bit to make sure it was not my bluetooth adapter.
Home Assistant 2022.8.1
Supervisor 2022.07.0
Operating System 8.4
Frontend 20220802.0 - latest
What version of Home Assistant Core has the issue?
2022.8.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 controller
Link to integration documentation on our website
https://www.home-assistant.io/integrations/homekit_controller/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: