home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.54k stars 30.72k forks source link

Unable to pair Fibaro CO Sensor as a HomeKit Device #126116

Closed cmsj closed 1 month ago

cmsj commented 1 month ago

The problem

I'm trying to migrate a Fibaro CO Sensor from HomeKit to Home Assistant.

I removed the sensor from HomeKit and after resetting it, it shows up as Discovered in Home Assistant, via an Everything Presence Lite bluetooth proxy in ESPHome. When I click the Configure button, a dialog appears telling me to wait for the wizard, but after a minute or so I get:

Error
Config flow could not be loaded: <html>
 <head><title>504 Gateway Time-out</title></head>
 <body>
 <center><h1>504 Gateway Time-out</h1></center>
 <hr><center>nginx</center>
 </body>
 </html>

I enabled debug logging for aiohomekit, but this was all I got across multiple attempts to pair:

➜  ~ grep aiohomekit /config/home-assistant.log
2024-09-17 12:28:04.353 DEBUG (ImportExecutor_0) [aiohomekit.protocol.tlv] sending [
  1 (Identifier): (2 bytes/<class 'bytes'>) b'\x01\x00'
  2 (Salt): (1 bytes/<class 'bytes'>) b'\x01'
]
2024-09-17 12:28:04.366 DEBUG (MainThread) [aiohomekit.controller.ble.controller] Starting BLE controller with instance: <habluetooth.wrappers.HaBleakScannerWrapper object at 0x7f62afe9a9f0>
2024-09-17 12:28:04.367 DEBUG (MainThread) [aiohomekit.controller.ble.controller] Discovery for 5d:50:7f:00:0d:62 already found
2024-09-17 12:28:14.526 DEBUG (MainThread) [aiohomekit.controller.ble.controller] Discovery for 5d:50:7f:00:0d:62 already found
2024-09-17 12:28:14.526 DEBUG (MainThread) [aiohomekit.controller.ble.discovery] FIBARO CO Sensor (AC:17:02:2D:0E:66): Ensure connected with device AC:17:02:2D:0E:66: FIBARO CO Sensor; rssi=-62
2024-09-17 12:29:23.779 DEBUG (MainThread) [aiohomekit.controller.ble.controller] Discovery for 5d:50:7f:00:0d:62 already found
2024-09-17 12:29:23.780 DEBUG (MainThread) [aiohomekit.controller.ble.discovery] FIBARO CO Sensor (AC:17:02:2D:0E:66): Ensure connected with device AC:17:02:2D:0E:66: FIBARO CO Sensor; rssi=-55
2024-09-17 12:31:14.074 DEBUG (MainThread) [aiohomekit.controller.ble.controller] Discovery for 5d:50:7f:00:0d:62 already found
2024-09-17 12:31:14.075 DEBUG (MainThread) [aiohomekit.controller.ble.discovery] FIBARO CO Sensor (AC:17:02:2D:0E:66): Ensure connected with device AC:17:02:2D:0E:66: FIBARO CO Sensor; rssi=-58
➜  ~

What version of Home Assistant Core has the issue?

core-2024.9.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

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?

No response

Additional information

No response

home-assistant[bot] commented 1 month ago

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. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


homekit_controller documentation homekit_controller source (message by IssueLinks)

cmsj commented 1 month ago

I'm going to close this issue as I replaced the device with one that is known to work.