Controme Miniserver - loses connection - homekit_controller integration not ready yet

[flame4ever]

The problem

After about 3 days and a reboot of Home Assistant, the Home Assistant homekit_controller can no longer connect to the Controme server via HomeKit. It is also strange that the IP 10.254.81.57 is given in the log, but the Controme server is running on a different ip.

2023-10-27 12:11:01.446 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Controme Miniserver B8-27-EB-FE-51-39' for homekit_controller integration not ready yet: Error while connecting to device 10.254.81.57:51826: [Errno 101] Connect call failed ('10.254.81.57', 51826) (ConnectionError); Retrying in background

What version of Home Assistant Core has the issue?

core-2023.10.5

What was the last working version of Home Assistant Core?

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

2023-10-27 12:11:01.446 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Controme Miniserver B8-27-EB-FE-51-39' for homekit_controller integration not ready yet: Error while connecting to device 10.254.81.57:51826: [Errno 101] Connect call failed ('10.254.81.57', 51826) (ConnectionError); Retrying in background

Example YAML snippet

-

Anything in the logs that might be useful for us?

-

Additional information

After deleting the HomeKit_controller device in Home Assistant, resetting the Controme HomeKit server and the restart of both servers, I can connect it again and it works again for a few days.

[home-assistant]

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.

_{^{(message by CodeOwnersMention)}}

---

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

[alghofaily55]

+1
Failed to call service light/turn_on. Timeout while waiting for response

[Jc2k]

Can you please confirm what your +1 means. Do you have the same device? Do you see a wrong ip address like OP?

If you follow the steps of OP does it work for a few days again, then stop?

[alghofaily55]

sorry ,, my issue after yesterday update OS11.1 ,, all homekit device are delay or not response

thanks

[flame4ever]

Is there any way to reset the HomeKit device integration?

[flame4ever]

After it was possible 3 times to re-integrate my HomeKit device it is now no longer possible and it appears after some waiting time the error "Config flow could not be loaded "

[flame4ever]

After updating to 2023.11, the integration worked again.
However, after updating to 2023.11.1, it cannot re-establish the connection.

2023-11-06 09:58:06.695 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Controme Miniserver XX-XX-XX-XX-XX-XX-XXFF [10.254.81.57:51826] (id=XX:XX:XX:XX:XX:XX): Connecting to accessory failed: [Errno 101] Connect call failed ('10.254.81.57', 51826); Retrying in 3 seconds
2023-11-06 09:58:17.029 DEBUG (MainThread) [aiohomekit.controller.abstract] [10.254.81.57:51826] (id=XX:XX:XX:XX:XX:XX): Accessories cache loaded (c#: 2) (gsn: None) (has broadcast_key: False)
2023-11-06 09:58:17.029 DEBUG (MainThread) [aiohomekit.controller.abstract] [10.254.81.57:51826] (id=XX:XX:XX:XX:XX:XX): Description updated: old=None new=HomeKitService(name='Controme Miniserver XX-XX-XX-XX-XX-XX-XXFF', id='XX:XX:XX:XX:XX:XX', model='Controme Miniserver XX-XX-XX-XX-XX-XX', feature_flags=<FeatureFlags: 0>, status_flags=<StatusFlags: 0>, config_num=2, state_num=1, category=<Categories.BRIDGE: 2>, protocol_version='1.0', type='_hap._tcp.local.', address='10.254.81.57', addresses=['10.254.81.57', '192.168.1.201', 'fe80::XXXX:XXXX:XXXX:XXXX', 'fe80::XXXX:XXXX:XXXX:XXXX', '2003:d4:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX'], port=51826)
2023-11-06 09:58:17.029 DEBUG (MainThread) [aiohomekit.controller.abstract] [10.254.81.57:51826] (id=XX:XX:XX:XX:XX:XX): Disconnected event notification received; Triggering catch-up poll
2023-11-06 09:58:17.029 DEBUG (MainThread) [aiohomekit.zeroconf] XX:XX:XX:XX:XX:XX: Device rediscovered
2023-11-06 09:58:17.030 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Starting reconnect loop to 10.254.81.57:51826
2023-11-06 09:58:17.030 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Attempting connection to 10.254.81.57:51826
2023-11-06 09:58:17.038 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Controme Miniserver XX-XX-XX-XX-XX-XX-XXFF [10.254.81.57:51826] (id=XX:XX:XX:XX:XX:XX): Connecting to accessory failed: [Errno 101] Connect call failed ('10.254.81.57', 51826); Retrying in 0 seconds
2023-11-06 09:58:17.790 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Attempting connection to 10.254.81.57:51826
2023-11-06 09:58:17.797 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Controme Miniserver XX-XX-XX-XX-XX-XX-XXFF [10.254.81.57:51826] (id=XX:XX:XX:XX:XX:XX): Connecting to accessory failed: [Errno 101] Connect call failed ('10.254.81.57', 51826); Retrying in 0 seconds
2023-11-06 09:58:18.923 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Attempting connection to 10.254.81.57:51826
2023-11-06 09:58:18.930 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Controme Miniserver XX-XX-XX-XX-XX-XX-XXFF [10.254.81.57:51826] (id=XX:XX:XX:XX:XX:XX): Connecting to accessory failed: [Errno 101] Connect call failed ('10.254.81.57', 51826); Retrying in 1 seconds
2023-11-06 09:58:20.619 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Attempting connection to 10.254.81.57:51826
2023-11-06 09:58:20.626 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Controme Miniserver XX-XX-XX-XX-XX-XX-XXFF [10.254.81.57:51826] (id=XX:XX:XX:XX:XX:XX): Connecting to accessory failed: [Errno 101] Connect call failed ('10.254.81.57', 51826); Retrying in 1 seconds
2023-11-06 09:58:23.158 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Attempting connection to 10.254.81.57:51826
2023-11-06 09:58:23.166 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Controme Miniserver XX-XX-XX-XX-XX-XX-XXFF [10.254.81.57:51826] (id=XX:XX:XX:XX:XX:XX): Connecting to accessory failed: [Errno 101] Connect call failed ('10.254.81.57', 51826); Retrying in 2 seconds
2023-11-06 09:58:26.965 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Attempting connection to 10.254.81.57:51826
2023-11-06 09:58:26.973 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Controme Miniserver XX-XX-XX-XX-XX-XX-XXFF [10.254.81.57:51826] (id=XX:XX:XX:XX:XX:XX): Connecting to accessory failed: [Errno 101] Connect call failed ('10.254.81.57', 51826); Retrying in 3 seconds

This is displayed if the connection is successful.

2023-11-06 10:32:56.294 WARNING (MainThread) [homeassistant.components.homekit_controller.connection] HomeKit device update skipped as previous poll still in flight: XX:XX:XX:XX:XX:XX

[codyc1515]

Can you please share a link to the device's page where it is for sale? Is that device HomeKit Certified? Do you have any other devices on a 10.254.x.x network?

[flame4ever]

This is the device's page https://www.controme.com/, as fare as i know it`'s HomeKit Certified.
But they user homebridge of homebridge.io Firmware: 0.4.53.

Do you have any other devices on a 10.254.x.x network:
This is an internal created IP of Home Assistant.

[bdraco]

We effectively have same problem as aio-libs/aiohttp#4451 (comment)

[bdraco]

We also need a happy eyeballs implementation for esphome/aioesphomeapi#233 (comment)

[flame4ever]

The Problem still exists with:
Core 2023.12.3
Supervisor 2023.12.0
Operating System 11.2
Frontend 20231208.2

[flame4ever]

The Problem is solved with:
Core 2024.1.2
Supervisor 2023.12.0
Operating System 11.3
Frontend 20240104.0