Skip to content
Home Assistant TestFlight
MQTT

Generic MQTT devices (unavailable state)

Other · And More

Partly worksApple Home issues

1 report: 1 says it partly works.

Reported with 1 integration: MQTT.

What people report

IntegrationIn Home AssistantIn Apple HomeWhat they saidSource
MQTTPartly worksBroken in Home
Unavailable devices still show online and controllable in Apple Home
Bridge does not mark unavailable entities as No Response
Saved copy
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 …

Excerpt saved from GitHub on 2026-10-23.

Issue #132056 · 2024-12

Each row is one report from a GitHub thread, an integration’s docs, or r/homeassistant. Check the date and the linked source before you buy.

In ReReHome

Once Home Assistant’s HomeKit Bridge shares it, this device reaches Apple Home as a HomeKit accessory behind your Home Assistant bridge, so ReReHome shows and controls it like any other.

Identifiers

BrandMQTT
CategoryOther