Closed zarboz closed 4 years ago
Hey there @Jc2k, mind taking a look at this issue as its been labeled with a integration (homekit_controller
) you are listed as a codeowner for? Thanks!
Does your device hang with the circle spinning until it errors out? You can try this quick edit to see if your issue was like mine.
https://github.com/home-assistant/home-assistant/issues/30592#issuecomment-574048154
Btw @Jc2k, I see that the tlv file was edited again and went back to \x01. Are you still working on this fix? I've manually edited the flag back to \x00 in the mean time.
When running homeassistant as native OS I can pair homekit device
when virtualizing using VMDK install I cannot pair a homekit device and receive above error
@hukuma1 the error I get is a little different
It sits and thinks then prompts for pin and fails pairing
Use case is a LG WebOS TV that is homekit enabled
am able to add to iphone homekit app directly.
I ended up just pairing the TV using webos pairing but it would be nice to figure out why i cant pair Home kit stuff to the HASS.IO vmdk install
@Hukuma1 Don't worry about that reverting, now that you are paired it will continue to work. The fix is stalled upstream though - we don't know how to tell which devices need a 0 and which need a 1.
@zarboz This looks like an environment issue rather than a homekit_controller thing. You see the error originates inside python:
File "/usr/local/lib/python3.7/socket.py", line 716, in create_connection
sock.connect(sa)
That's a timeout waiting for the OS to reach from your failing environment to the homekit device. I'm not really sure about how to help you go about resolving something like that - no amount of changes of the homekit protocol code will help if its failing before the protocol even starts executing! :-(
Note that even if we got this to pair the Television type is currently not supported either :-(
(Next step is probably to take this to the homekit_python project (https://github.com/jlusiardi/homekit_python/) - report a bug there if the CLI there also fails in the same way).
@Jc2k thanks will continue bug report there if I can find more details about incident
Hi, I've the same problem on the native OS:
Logger: homeassistant.components.homekit_controller.config_flow
Source: components/homekit_controller/config_flow.py:453
Integration: homekit_controller (documentation, issues)
First occurred: 06:15:34 (4 occurrences)
Last logged: 06:23:11
Pairing attempt failed with an unhandled exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/homekit_controller/config_flow.py", line 453, in async_step_pair
pairing = await self.finish_pairing(code)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohomekit/controller/ip/discovery.py", line 83, in finish_pairing
response = await self.connection.post_tlv(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohomekit/controller/ip/connection.py", line 416, in post_tlv
response = await self.post(
^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohomekit/controller/ip/connection.py", line 377, in post
return await self.request(
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohomekit/controller/ip/connection.py", line 440, in request
raise AccessoryDisconnectedError(
aiohomekit.exceptions.AccessoryDisconnectedError: Connection lost before request could be sent
Home Assistant release with the issue:
arch : unk dev : false docker : true hassio : true os_name : Linux python_version : 3.8 version : 0.195 virtualenv : true
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.): hassio on raspberry pi 3B
Integration: https://www.home-assistant.io/integrations/homekit_controller/
Description of problem: Homekit devices are discovered but are unable to be paired
Steps to reproduce:
Logs attached