Compatibility is a chain, not a single yes/no label. A device may support a radio protocol but still depend on a compatible controller, integration, firmware version, network feature, security mode, and exposed device profile.
Check these layers
| Layer | Verify | Common hidden mismatch |
|---|---|---|
| Physical protocol | Zigbee, Z-Wave region, Wi-Fi band, Bluetooth, Matter transport | Correct product name but different regional radio |
| Controller | Coordinator, bridge, border router, Bluetooth adapter/proxy | Unsupported chipset or outdated firmware |
| Integration | Official integration documentation and supported authentication | Device works in vendor app but API access differs |
| Device profile | Exposed clusters, endpoints, command classes, or Matter device type | Pairing succeeds but a feature is not exposed |
| Network | IPv6, multicast, VLAN routes, DNS/mDNS, ports, radio channel | Discovery works from a phone but not from Home Assistant |
| Versions | Home Assistant, integration, add-on, coordinator, device firmware | Instructions apply to an older release |
| Ownership | Fabric, controller, cloud account, HomeKit pairing state | Device is already owned by another controller |
Known-issue records
Each future record must include: exact product/model, region when relevant, connection path, controller, integration, affected versions, observed symptom, evidence source, safe workaround, resolution status, last verification date, and links to the detailed Troubliq guide and primary documentation.
Status labels
- Documented: confirmed by current official or maintainer documentation.
- Reproducible report: supported by detailed issue reports but not yet documented as a general limitation.
- Community pattern: repeated reports used to guide investigation, not presented as proof.
- Resolved: a fix is released and the applicable version is identified.
- Unverified: insufficient evidence; not used for a definitive recommendation.
Safe verification order
- Identify the exact hardware model and regional version.
- Record current software and firmware versions.
- Check official integration and manufacturer documentation.
- Check maintainer release notes and reproducible issue reports.
- Use community reports to identify edge cases, then label their evidence level.
- Back up and apply one reversible change at a time.
Start with Troubleshooting Guides or the Diagnostic Decision Tree.
Home Assistant 2026.9 compatibility changes
| Area | Affected behavior | Safe action | Status |
|---|---|---|---|
| Flexit Nordic (BACnet) | The deprecated fireplace-mode switch entity was removed. | Replace uses of switch.<device>_fireplace_mode with climate.set_preset_mode and preset_mode: fireplace. |
Documented breaking change |
| KNX exposes | An entity’s first value is no longer sent automatically to the KNX bus. | Enable “Send on initialization” or set send_on_init: true when the first value must be transmitted. |
Documented breaking change |
| LLM APIs | Tool names are now prefixed by the providing integration’s domain. | Update custom prompts that name tools directly; for example, use the new domain-prefixed name. | Documented breaking change |
| Persistent notifications | Updating an existing notification now produces update_type: updated instead of added. |
Add updated to automations intended to catch both new and changed notifications. |
Documented breaking change |
| UniFi Protect | UniFi Protect 7.2.105 or newer is required; older systems stop integration setup. | Back up, update UniFi Protect through its supported process, then reload the integration. | Documented minimum version |
| Update entities | Installing, skipping, or clearing a skipped update from a user-started script now requires an administrator account. | Run the script as an administrator or move the operation to an automation where appropriate. | Documented permission change |
| Vacuum custom integrations | The deprecated base battery_level property was removed. |
Custom integrations must expose battery level through a separate battery sensor. | Documented developer change |
| Z-Wave JS lock management | Actions that manage lock users and credentials now require an administrator account. | Run those sensitive actions only from an administrator context. | Documented permission change |
Primary source: Home Assistant 2026.9 backward-incompatible changes. Readers should also review later 2026.9 patch notes before changing a live system.
Current Home Assistant 2026.9.3 issue reports
Important: the records below are open upstream reports, not proof that every 2026.9.3 installation is affected. Confirm your exact version, integration and complete log context before changing a working system. Prefer backups and reversible checks; do not delete entities, reset devices or restore backups solely because a report looks similar.
| Exact symptom | Area | Evidence and status | Safest next step |
|---|---|---|---|
This entity is no longer being provided, Error connecting to bridge, or [Errno 113] Host is unreachable |
Osram Lightify on Core 2026.9.3 | Upstream issue #182777; open report first filed September 20, 2026. | Confirm the bridge is reachable from the Home Assistant host and preserve the full first traceback. Do not delete entities or factory-reset the bridge while the report is unresolved. |
This entity is no longer being provided by the netatmo integration for battery status |
Netatmo on Core 2026.9.3 | Upstream issue #182672; open report filed September 19, 2026. | Verify that only the battery entity is affected. Keep the device and integration intact while checking the issue for a maintainer update. |
| The automatic-backup list shows only the newest backup although older files remain on the destination | Home Assistant backups after 2026.9.3 | Upstream issue #182746; open report. | Confirm the backup files exist at the storage destination before deleting, rotating or recreating anything. Protect the emergency kit and encryption key. |
cannot import name RECOMMENDED_USE_GOOGLE_SEARCH_TOOL or integration setup/import failure |
Google Generative AI integration | Upstream issue #182623; open report. | Preserve the complete import error and installed Core/integration versions. Avoid editing package files manually; follow the upstream issue for a supported repair. |
LibraryShutdown, invalid PDUStatus, AccessoryDisconnectedError, or decryption-desynchronization errors during pairing |
Onvis SMS2, HomeKit over Thread | Upstream issue #182679; open report. | Preserve the device’s current ownership and Thread credentials. Compare the failure with the ownership-safe HomeKit recovery guide before resetting anything. |
Backup restore returns Unknown error |
Home Assistant backup restore | Upstream issue #182849; open report. | Keep the original backup unchanged, record the installation type and versions, and verify the correct recovery key using the backup encryption guide. |
Integration health cards
These cards describe the safest diagnostic starting point. They are independent summaries, not official Home Assistant certification and not a promise that every device or firmware combination is supported.
Home Assistant Core
Check first: Settings → System → Logs, Repairs, Supervisor/Core status, storage and the first error before dependent integrations fail. Safe recovery: preserve a current backup and change one variable at a time. Core unresponsive guide.
ZHA and Zigbee
Check first: coordinator visibility, stable serial path, integration startup error, firmware and USB conflicts before touching paired devices. Avoid: resetting the coordinator or rebuilding the mesh as a first step. ZHA coordinator guide.
Zigbee2MQTT
Check first: coordinator access, MQTT connection, device wake state and the interview log. Avoid: repeated rapid pairing attempts that hide the first useful failure. Interview failure guide.
Matter and Thread
Check first: fabric ownership, Matter server status, preferred Thread dataset, border router availability, IPv6 and multicast. Avoid: factory-resetting a commissioned device before documenting ownership. Matter/Thread guide.
MQTT
Check first: broker connection, discovery replay, retained availability, birth messages and topic names. Avoid: clearing retained topics until you know which publisher owns them. MQTT restart guide.
Philips Hue
Check first: bridge reachability, integration options, grouped-light entities and disabled entities. Avoid: deleting the bridge integration to recover a hidden room or zone. Hue group guide.
Shelly
Check first: power, current IP, firmware, local protocol access and VLAN/firewall paths. Avoid: cloud-only diagnosis when local discovery or RPC is failing. Shelly guide.
HomeKit Device
Check first: current controller ownership, pairing state, Thread credentials and whether the accessory still exists in another controller. Avoid: factory reset before documenting the existing fabric. Already-paired recovery guide.
Privacy: never publish raw diagnostics without reviewing them for tokens, credentials, coordinates, device identifiers, addresses and private URLs. Home Assistant’s diagnostic guidance requires sensitive values to be redacted.
Last reviewed: September 23, 2026. Issue status can change after this review; follow the linked upstream record for the newest maintainer activity. This database will not claim universal compatibility from a successful pairing report alone.