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