core: Secretlab MAGRGB Thread HomeKit Configuration Error
The problem
So, I am not sure whether what I am trying to do is wrong or not so apologies in advance if I am being stupid. I used the link from the system log entry to get here.
I have bought the following light which comes with my desk, which is effectively a nanoleaf https://secretlab.co.uk/products/magrgb-diffused-rgb-strip-smart-edition
I installed the nanoleaf app and added the light. During this process it connected to my thread border router, which is a Google Nest Hub. Everything seems to work fine.
I went into Home Assistant and received the notification that a new decive had been discovered and it identifies the light as a HomeKit Device.
In settings, I attempt to configure this device but it returns with the error that it cannot be configured and asks to enter a code. I try the code on the device but receive the same error “Pairing attempt failed with an unhandled exception”
I have copied the corresponding entry from the system log
My setup is
- Home Assistant Green (wired into router)
- One Thread border router, which is my Google Nest Hub
- I don’t currently have anything to do with HomeKit or Apple installed on the network
- I do have one more device (matter) working over thread on the network
- If I go to my Thread integration in Home Assistant and click configure, it shows one entry for my preferred network which is my Google Nest Hub
I am pretty sure I might be doing something dumb so any advice really welcome, thanks!
What version of Home Assistant Core has the issue?
core-2024.2.0
What was the last working version of Home Assistant Core?
core-2024.2.0
What type of installation are you running?
Home Assistant OS
Integration causing the issue
HomeKit
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?
Logger: homeassistant.components.homekit_controller.config_flow
Source: components/homekit_controller/config_flow.py:490
Integration: homekit_controller (documentation, issues)
First occurred: 08:27:05 (4 occurrences)
Last logged: 08:38:01
Pairing attempt failed with an unhandled exception
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/aiohomekit/controller/coap/connection.py", line 294, in do_pair_setup
response = await self.pair_setup_client.request(request).response
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/homekit_controller/config_flow.py", line 490, in async_step_pair
self.finish_pairing = await discovery.async_start_pairing(self.hkid)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohomekit/controller/coap/discovery.py", line 57, in async_start_pairing
salt, srpB = await self.connection.do_pair_setup(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohomekit/controller/coap/connection.py", line 293, in do_pair_setup
async with asyncio_timeout(16.0):
File "/usr/local/lib/python3.12/asyncio/timeouts.py", line 115, in __aexit__
raise TimeoutError from exc_val
TimeoutError
Additional information
No response
About this issue
- Original URL
- State: open
- Created 5 months ago
- Comments: 15 (7 by maintainers)
So the discoveries don’t currently time out. So if the device only has intermittent thread connectivity, or it has decided to switch thread off and go back to bluetooth, you might catch an old stale discovery. Restarting and it not coming back is consistent with this sort of thing. Hopefully moving the nest closer will sort things out, in which case you’ll need more router capable Thread devices or more BRs.