Cannot connect Eve Flare to Home Assistant via Thread

[ThronRyzer]

The problem

I'm trying to connect a EVE Flare light to HA using the Homekit via Thread integration.

I've added the device to Apple Home and removed it afterwards. It's then discovered for the HomeKit Integration.

After entering the Homekit Code, I receive the following error: "This accessory is already paired to another device. Please reset the accessory and try again."

Afterwards the device is not discovered anymore.

What version of Home Assistant Core has the issue?

core-2023.11.3

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

No response

Diagnostics information

home-assistant_2023-12-05T18-07-45.174Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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)}}

[groveybeans]

Same problem here^

[Jc2k]

Some Eve devices don't actually unpair cleanly. Then iOS pretends they did. When that happens you need to hard reset them before anything can pair them.

There's no magic fix here. If the device isn't in a pairable state it's not in a pairable state. In the cases I've seen it's a firmware issue so will keep happening no matter what you do.

If you have working Bluetooth in HA you can pair it over Bluetooth instead of thread. Then you can import your iOS thread network into HA with the HA iOS app. Then upgrade from Bluetooth to thread through HA as well.

[TriggrHappy]

Some Eve devices don't actually unpair cleanly. Then iOS pretends they did. When that happens you need to hard reset them before anything can pair them.

There's no magic fix here. If the device isn't in a pairable state it's not in a pairable state. In the cases I've seen it's a firmware issue so will keep happening no matter what you do.

If you have working Bluetooth in HA you can pair it over Bluetooth instead of thread. Then you can import your iOS thread network into HA with the HA iOS app. Then upgrade from Bluetooth to thread through HA as well.

Thx, the Bluetooth-workaround worked like a charm after I struggled for weeks with pairing one specific Eve Energy-plug! I used Bluetooth proxy through an ESPHome device.

[gravityrebel]

Some Eve devices don't actually unpair cleanly. Then iOS pretends they did. When that happens you need to hard reset them before anything can pair them.

There's no magic fix here. If the device isn't in a pairable state it's not in a pairable state. In the cases I've seen it's a firmware issue so will keep happening no matter what you do.

If you have working Bluetooth in HA you can pair it over Bluetooth instead of thread. Then you can import your iOS thread network into HA with the HA iOS app. Then upgrade from Bluetooth to thread through HA as well.

At the very least shouldn't these un-handled exceptions become handled ones? I'm having this issue right now and the instructions in the log seem to indicate that we should report the issue:

2024-05-17 14:47:40.821 WARNING (MainThread) [coap-server] An exception that is not an aiocoap Error was raised from a transport; please report this as a bug in aiocoap: TypeError("'NoneType' object does not support item assignment") 2024-05-17 14:47:40.825 ERROR (MainThread) [aiohomekit.utils] Failure running background task: Task-10442

I'm not sure what version of aiocoap HA is using, but Version 0.4.8 seems to have cleaned up a lot of error messages which could help. The logs also make reference to python3.12, but when I go look at the referenced path in /usr/local/lib all I see is python3.11.

In case it is helpful I am uploading my logs as well. home-assistant_2024-05-17T18-52-00.147Z.log

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.