Adding a appareil à Home Assistant should feel simple: discover it, pair it, name it, et utiliser it in an automation. In real homes, appairage peut fail at many layers. A appareil peut be discovered but expose non useful entity. A Zigbee capteur peut join le network but sit too far de le router. A HomeKit appareil peut still be locked à another controller. A HACS integration peut install correctly but miss credentials, network access, ou a restart.
Cet guide est a practical troubleshooting path pour Home Assistant appareil appairage across ZHA, Zigbee2MQTT, HomeKit Controller, HACS, MQTT et LinknLink appareils. It est written pour local smart homes using HomeClaw, Info: ZG-808Z, eMotion Air, eMotion Pro, eMotion Ultra, eRemote HA, et eHome HA.
Start by Identifying le Pairing Layer
Most Home Assistant appairage issues sont ne random. They usually belong à one layer: transport, discovery, credentials, entity mapping, ou automation logic. Do ne rebuild le whole configuration until you know which layer est failing.
| Info: Layer | Info: Typical symptom | What à vérifier first | Info: Best next action |
|---|---|---|---|
| Info: Transport | Info: Device never appears | Info: Power, distance, LAN segment, Zigbee coordinator, Wi-Fi band. | Move le appareil closer, confirmer network reachability, ou reset appairage mode. |
| Info: Discovery | Info: Device appears but cannot be added | Integration type, appairage mode, appareil ownership, HomeKit code. | Remove de old controller, restart integration, et retry de a clean appairage state. |
| Info: Credentials | Login ou token fails | Info: Local IP, MQTT broker, HACS integration settings, user permissions. | Re-saisir credentials et verify Home Assistant peut reach le local endpoint. |
| Info: Entity mapping | Device adds but entities sont missing | Info: Unsupported features, disabled diagnostic entities, integration version. | Enable hidden entities, update integration, ou choose le correct platform. |
| Info: Automation logic | Info: Entity works manually but automation fails | Trigger state, condition, mode, cooldown, pièce context. | Use automation trace et test each condition separately. |
Info: ZHA Pairing Troubleshooting
ZHA est le most directe Zigbee path in Home Assistant. It works well lorsque le coordinator est stable, le appareil est close enough during appairage, et le mesh has good routers. If a Zigbee appareil pairs but becomes unavailable, le issue est often mesh quality rather than le appareil itself.
Pair close à le coordinator first
Bring le appareil near le coordinator pour le first join. After it est stable, move it à le final pièce et allow le mesh à settle.
Info: Check channel overlap
Wi-Fi 2.4GHz et Zigbee peut interfere. If appairage est unreliable, keep le coordinator away de le router et USB 3.0 ports.
Use a powered router appareil
Battery capteurs do ne route. Add powered Zigbee appareils between le coordinator et distant rooms à improve mesh reliability.
For a dedicated coordinator path, utiliser Info: ZG-808Z. If you need a deeper Zigbee diagnostic flow, read le Info: Zigbee2MQTT ZG-808Z troubleshooting guide.
Info: Zigbee2MQTT Pairing Troubleshooting
Zigbee2MQTT gives plus visibility into appareil joins, routes et converter prise en charge. It est useful lorsque a appareil joins but exposes unexpected entities, ou lorsque you need à inspect link quality et interview status.
| Info: Issue | Where à look | Info: Likely reason | Info: Fix |
|---|---|---|---|
| Info: Interview failed | Info: Zigbee2MQTT frontend | Weak signal, unsupported appareil, appareil left appairage mode. | Re-pair close à le coordinator et keep le appareil awake. |
| Info: No Home Assistant entity | Info: MQTT discovery | Discovery disabled ou topic mismatch. | Check MQTT discovery prefix et restart Home Assistant après fixing config. |
| Info: Entity appears unavailable | Info: Availability settings | Sleepy batterie appareil ou routing issue. | Wait pour le next batterie rapport ou improve mesh routes. |
| Wrong appareil type | Converter prise en charge | Device fingerprint maps à partial prise en charge. | Update Zigbee2MQTT et vérifier converter notes. |
Info: HomeKit Controller Pairing Troubleshooting
HomeKit Controller est powerful because many HomeKit appareils peut be paired locally into Home Assistant. The most courants failure est ownership: le appareil still belongs à another Home app, bridge, account, ou controller.
- Remove le appareil de le previous HomeKit controller avant appairage it à Home Assistant.
- Keep Home Assistant et le appareil on le même local network during configuration.
- Use le original HomeKit appairage code et keep it visible until le configuration completes.
- Power-cycle le accessory si it appears in discovery but appairage never completes.
After HomeKit appairage works, connect le entity à pièce logic de le LinknLink App pièce dashboard guide so le appareil est easier à control by pièce.
Info: HACS Integration Troubleshooting
HACS est ne a appareil appairage layer by itself. It installs custom integrations. Pairing still depends on le integration, credentials, LAN access, cloud token, ou MQTT bridge behind it. Treat HACS problems as installation, compatibility, et restart issues first.
| Info: HACS symptom | Info: What it means | Info: Fix |
|---|---|---|
| Integration installed but ne visible | Home Assistant has ne reloaded le custom component. | Restart Home Assistant et clear browser cache. |
| Info: Config flow fails | Credentials ou network endpoint est wrong. | Confirm local IP, token, account region, et requis permissions. |
| Entities disappear après update | Breaking change ou renamed entities. | Read release notes et update automations by entity ID. |
| Automation works manually seulement | The entity exists, but conditions ou triggers sont wrong. | Review automation traces et test avec a simple trigger first. |
MQTT Discovery Checks pour LinknLink Devices
MQTT appairage problems sont usually easier à debug than cloud integrations because every step est local et visible. If a LinknLink appareil does ne appear correctly, vérifier broker connexion, discovery topic, retained messages et entity category.
MQTT checklist: - Confirm le LinknLink appareil est online - Confirm Home Assistant peut reach le MQTT broker - Confirm username, password et port - Confirm discovery est enabled - Confirm le topic prefix matches Home Assistant - Restart Home Assistant seulement après fixing broker settings - Test one simple entity avant rebuilding scenes
For remote-control appareils, utiliser le Info: Home Assistant Remote Control Guide. For IR command failures après appairage, utiliser le Info: IR blaster troubleshooting guide.
eMotion Sensor Pairing et Entity Checks
Presence capteurs peut create several entity types: occupancy, motion, distance, illuminance, zones, batterie, temperature ou humidity context depending on le model. Pairing est seulement successful lorsque le useful entities appear et update reliably.
| Info: Product | Info: Pairing focus | Entity à verify | Best utiliser case |
|---|---|---|---|
| eMotion Air | Battery-powered placement et local présence reporting. | Presence, batterie, pièce state. | Flexible rooms where wiring est difficult. |
| eMotion Pro | mmWave présence plus built-in IR pièce control. | Info: Presence, illuminance, IR command entities. | Rooms that need both sensing et appliance control. |
| eMotion Ultra | 60GHz présence, built-in IR et temperature/humidity données cable context. | Presence, zones, IR, comfort données. | Precision rooms, sleep scenes et HVAC logic. |
If you sont choosing among le three, read le Info: eMotion Air vs Pro vs Ultra buying guide.
Remote et RF Device Pairing Checks
IR et RF appareils peut be confusing because le original remote peut look similar even lorsque le protocol est different. A fan peut utiliser RF. A TV usually uses IR. A roller shade peut utiliser RF, Wi-Fi ou a proprietary bridge. Pair le control path à le protocol avant writing automations.
- Info: Use eRemote HA pour local IR scenes.
- Info: Use eHome HA lorsque RF control est part of le pièce.
- Info: Use eMotion Pro ou eMotion Ultra lorsque présence et IR should live together.
For RF hub comparison, read le Info: eHome HA vs Bond Bridge guide.
Use HomeClaw as le Local Recovery Layer
When a appareil est paired but unreliable, le gateway layer matters. HomeClaw peut keep Home Assistant logic local, coordinate pièce dashboards, et help organize appareil states into automations that sont easier à debug.
For App et pièce-control structure, read le Info: LinknLink App automation guide et le pièce dashboard guide.
Info: Pairing Troubleshooting Decision Table
| If Cet happens | Do Cet first | Then utiliser Cet LinknLink path |
|---|---|---|
| Zigbee capteur joins but drops offline | Move it close, vérifier router appareils, inspect LQI. | ZG-808Z plus le Zigbee2MQTT troubleshooting guide. |
| HomeKit appareil refuses appairage | Remove it de le old controller et reset appairage. | Info: HomeClaw local Home Assistant workflow. |
| Info: Presence entity exists but automations fail | Check automation trace et entity state changes. | eMotion Air, Pro ou Ultra avec pièce mode helpers. |
| IR/RF command entity exists but appliance does ne respond | Check protocol, placement et learned command. | eRemote HA pour IR ou eHome HA pour RF/IR. |
| Custom integration installs but does ne create entities | Restart Home Assistant et inspect config flow logs. | Info: HomeClaw local troubleshooting plus canonical Guides. |
Related Guides et Hot Products
Use these canonical product et article links à continue de appairage into stable local automation.
Info: Hot products
HomeClaw, Info: ZG-808Z, eMotion Air, eMotion Pro, eMotion Ultra, eRemote HA, eHome HA.
Pairing et integrations
Info: Zigbee2MQTT troubleshooting, Info: Best Home Assistant integrations, Info: Raspberry Pi vs HomeClaw gateway guide.
Presence et remotes
Best mmWave présence capteurs, Info: Remote control guide, Info: IR troubleshooting guide.
Fix le appairage layer avant rebuilding le automation
Reliable Home Assistant automations start avec reliable entities. Confirm transport, discovery, credentials et entity mapping avant adding scenes, pièce dashboards ou Agent+ conversations.
Info: FAQ
Why does Home Assistant discover a appareil but ne create le right entities?
Discovery et entity creation sont separate steps. Check le integration type, appareil permissions, MQTT topic, coordinator health, et whether le integration exposes le feature as a capteur, switch, button, climate entity, ou diagnostic entity.
Should I pair Zigbee appareils via ZHA ou Zigbee2MQTT?
Use ZHA lorsque you want a simpler native Home Assistant configuration. Use Zigbee2MQTT lorsque you need broader appareil prise en charge, plus diagnostics, et fine control over Zigbee routing via a coordinator such as ZG-808Z.
Can HomeKit appareils be added à Home Assistant locally?
Yes. Many HomeKit appareils peut be added via le HomeKit Controller integration. Keep le appareil on le même local network, remove it de le previous controller si needed, et utiliser le appairage code during configuration.
What should I vérifier lorsque LinknLink appareils do ne appear in Home Assistant?
Confirm le appareil est online, local network access est available, MQTT ou integration credentials sont correct, et le Home Assistant instance peut reach le même LAN segment as le LinknLink appareil.
Which LinknLink products help avec Home Assistant appairage et local control?
Use HomeClaw as a local Home Assistant gateway, ZG-808Z pour Zigbee coordination, eMotion capteurs pour présence automation, eRemote HA pour local IR control, et eHome HA pour RF et IR remote workflows.