Device is not exposed as thread capable in Apple Home

[AlexandreJubert]

The problem

I've discovered that the devices exposed to Apple Home are not properly reported as Thread compatible to companion apps.

My issue is that I'm trying to expose some nanoleafs essentials lightbulbs to the nanoleaf app, but I'm not able to leverage all of the Nanoleaf app features because my lightbulbs are reportedly using bluetooth according to Nanoleaf's app.

I'm currently running core-2024.4.3 on a raspberry pi running Home Assistant OS.

I run a thread network (via a Sonoff ZigBee flashed with multiprotocol to support zigbee too) that is currently merged with my Apple border routers, like so:

My lightbulb is properly registered as a homekit device in home assistant, and is on the thread network, as reported in the UI:

When I go back to homekit my device is exposed by the bridge in Apple Home like so:

But as soon as I try to control the light with nanoleaf, nanoleaf reports the light is using bluetooth (which is definitely wrong) and being on an unkown network:

I would expect the light to be reported as part of the thread network shared between all my apple border routers and home assistant.

Please let me know if I can provide any relevant information or logs.

Thank you for your time!

What version of Home Assistant Core has the issue?

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

Link to integration documentation on our website

https://www.home-assistant.io/integrations/homekit/

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]]

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (homekit) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `homekit` 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` 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 documentation homekit source _{^{(message by IssueLinks)}}

[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.

[AlexandreJubert]

Issue still occurs on version 2024.7.2