home-assistant[bot]
commented
1 day ago 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)
The problem
While HA knows and shows that MQTT device as "Unavailable" - the Homekit bridge is exposing this devices with "Available / Online" state. So you can even false control them...
This is very old issue still not fixed https://community.home-assistant.io/t/when-a-device-is-unavailable-in-hass-it-does-not-reflect-this-in-apple-home-as-no-response/123381/4
What version of Home Assistant Core has the issue?
2024.11.3
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 Bridge
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