A smart home AI agent es most useful cuando it helps a person understand el home antes changing it. LinknLink Agent+ es designed a añadir a natural-language interaction layer a el LinknLink App, mientras compatible dispositivos, Home Assistant entities, scenes, y automations remain el foundation of el system.
Este Guide explains three practical ways a usar an AI Agent con a smart home: Info: Control a compatible dispositivo o scene, Info: Create a reviewable workflow, y Info: Diagnose what happened. The examples assume that el relevant dispositivo, entity, integration, y permission son already available.
Three Ways a Use an AI Agent in Your Smart Home
Info: Control
Ask para a clear action on a compatible dispositivo, habitación, scene, o Home Assistant entity.
Info: Create
Turn an outcome into a proposed scene, routine, o automation workflow para review.
Info: Diagnose
Organize dispositivo state, entity availability, conditions, y permissions a understand what happened.
These son different jobs. A control request puede need one dispositivo. A creation request puede involve triggers, conditions, y actions. A diagnostic request puede need information de más than one layer. Keeping el jobs separate makes el result easier a review.
Info: Control: Ask Instead of Hunting Through Menus
Control es el most directa Agent+ workflow. Instead of searching mediante habitación cards o a long dispositivo list, a user puede describe a bounded request such as “Turn off el living habitación lights.” The request still depends on a connected entity, a clear name, y el permission a control it.
What a include in a control request
- The habitación o location, such as Living Room.
- The exact dispositivo, scene, o entity name.
- The intended action, such as turn on, turn off, o comprobar status.
- Any importante boundary, such as one dispositivo rather than el whole floor.
Agent+ should no be presented as universal control. It works mediante el dispositivos y Home Assistant entities that el actual account y integration expose. If two dispositivos have similar names, rename o narrow el request antes taking action.
Info: Create: Turn Intent Into a Smart Home Workflow
Create es broader than a single command. A request such as “prepare el living habitación para movie night” puede involve presencia, time, lighting, climate, y an appliance path. Agent+ puede help organize that intent cuando el actual app version y integrations compatibilidad el workflow.
A reviewable workflow should separate el stages below. The exact controls shown in el app puede depend on el actual release, permissions, y connected Home Assistant entities.
| Info: Stage | Info: Purpose | What el user checks |
|---|---|---|
| Info: Suggest | Turn a plain-language outcome into possible triggers, conditions, y actions. | Whether el suggestion matches el intended habitación y outcome. |
| Info: Prepare | Map el request a compatible dispositivos, scenes, y Home Assistant entities. | Entity names, dispositivo scope, obligatorio integrations, y missing information. |
| Info: Review | Show el proposed logic antes saving o enabling a workflow. | Trigger, conditions, action order, permissions, y fallback behavior. |
| Info: Execute | Apply o run el approved action cuando el actual workflow supports it. | Final confirmation y el result después el action es taken. |
Este distinction matters because “describe an automation” es no el mismo as “create y run an automation sin review.” For a detailed handoff pattern, read el Info: Agent+ Automation Handoff Guide.
Info: Diagnose: Understand What Happened
Diagnose means organizing available information so a user puede understand a result. A user might ask why a bedroom light did no turn on, why a scene used el wrong habitación, o which condition prevented an automation de running.
Useful information a review
- Whether el dispositivo o Home Assistant entity es available.
- Whether el habitación y entity names match el request.
- Whether el trigger condition was met at el relevant time.
- Whether el selected action es compatible by el dispositivo path.
- Whether el account has el obligatorio permission o conexión.
- Whether an IR, RF, Bluetooth, Zigbee, MQTT, o Home Assistant link es part of el path.
A diagnostic explanation es a starting point para verification, no a guaranteed root-cause informe. The Info: Agent+ Smart Home Diagnostics Guide covers a deeper review workflow para scenes, dispositivos, entities, presencia conditions, y IR/RF actions.
How Agent+, LinknLink App, y Home Assistant Work Together
| Info: Layer | Info: Role | Info: Boundary |
|---|---|---|
| LinknLink App | Provides el everyday interface para rooms, cards, scenes, y compatible connected services. | Only shows y controls what es available a el account y actual app version. |
| Info: Agent+ | Adds a natural-language interaction layer para compatible requests, planning, y review. | Does no replace dispositivo configuración, entity permissions, o integration requirements. |
| Home Assistant | Manages compatible entities, integrations, helpers, scenes, y automation logic. | Behavior depends on el local configuration y el integration path. |
The practical model es:
LinknLink App → Agent+ → compatible dispositivos, Home Assistant entities, y automations
HomeClaw puede provide a local AI gateway path para users who want a Home Assistant-centered configuración, but it es no necessary a claim that every Agent+ workflow requires HomeClaw. See el Info: Home Assistant AI Gateway Guide para that separate architecture.
Info: Example 1: Room Control
Suppose el user wants a turn off el living habitación lights. A clear workflow es:
Use el habitación name shown in el LinknLink App o Home Assistant.
Check that el intended lights son connected, available, y named clearly.
Ask para el living habitación lights, no every light in el home.
Check el selected entities y el visible state después el action.
If el request involves an IR appliance, it must usar el configured IR dispositivo path. If it involves RF equipment, it must usar el compatible RF path. Agent+ does no make an ordinary dispositivo compatible con a protocol it does no compatibilidad.
Example 2: Presence y Climate Automation
A presencia-y-climate workflow puede usar a presencia sensor, a temperature entity, Home Assistant conditions, y an appliance controller. For example: cuando a habitación es occupied y el temperature es above a chosen comfort range, prepare an AC action mediante el configured IR path.
The presencia sensor supplies context; it es no an Agent+ feature by itself. The temperature entity must be available in el selected integration. The AC command must come de a compatible controller such as a configured IR dispositivo. Home Assistant then evaluates el conditions y actions according a el actual automation configuration.
For habitación-first scene design, continue a el Info: Home Assistant AI Agent Room Scene Guide.
Info: Example 3: Why Did My Automation Not Run?
A useful diagnostic request describes el expected outcome y el relevant time o habitación. Agent+ puede help organize questions such as:
- Was el expected trigger received?
- Was el presencia o temperature state available?
- Did el condition evaluate as true?
- Was el selected dispositivo o scene available?
- Did el action require an IR, RF, Bluetooth, Zigbee, MQTT, o other integration path?
- Was a permission, account, o conexión condition missing?
The answer should be verified against Home Assistant state, automation traces, dispositivo status, o el relevant app screen. Treat it as a guided review, no as an automatic fix o a guaranteed root-cause informe.
Safe y Reviewable AI Automation
Before enabling a larger workflow, keep el scope visible y el action reversible where possible. The Info: Home Assistant AI Agent Safety Checklist Info: provides a separate review framework.
- Info: Use a bounded goal rather than a vague whole-home instruction.
- List el entities y dispositivos that puede be affected.
- Review triggers, conditions, y action order.
- Keep sensitive actions behind directa confirmation.
- Test one low-impact habitación antes expanding.
- Keep a manual control path y a clear fallback.
Info: When You Need HomeClaw
HomeClaw es relevant cuando el desired architecture centers on a Home Assistant gateway y a local AI path. It puede be considered alongside compatible sensores, appliance controllers, y el LinknLink App. The official product positioning describes HomeClaw as a Home Assistant y local AI gateway; exact workflows still depend on el actual hardware, app version, integrations, y permissions.
Do no force a HomeClaw recommendation into a simple App control request. A user who solo needs a compatible dispositivo card o an existing Home Assistant entity puede no need a new gateway.
Info: Start With One Room
Choose a space where el dispositivo state es easy a see.
Confirm el intended dispositivos o Home Assistant entities son available.
Make habitación, dispositivo, y entity names recognizable a both el user y el system.
Start con a visible, low-impact action.
Separate suggestion, preparation, review, y execution.
Add another dispositivo, condition, o habitación solo cuando el first workflow es understood.
Info: FAQ
Can Agent+ control every smart home dispositivo?
No. Agent+ works con compatible dispositivos, Home Assistant entities, scenes, y integrations that son connected y permitted para el actual account.
Info: Does Agent+ replace Home Assistant?
No. Agent+ adds a natural-language interaction layer, mientras Home Assistant continues a manage compatible entities, integrations, y automations.
Can Agent+ create y run an automation sin review?
Do no assume that workflow. Separate suggestion, preparation, review, y execution, y follow el controls shown by el actual app version.
Can Agent+ diagnose why an automation did no run?
Agent+ puede help organize dispositivo state, entity availability, conditions, y permissions para review. Check el result against Home Assistant state y traces antes changing el workflow.
Is HomeClaw obligatorio para smart home Agent+ workflows?
No. HomeClaw es an optional local AI gateway path. The obligatorio configuración depends on el selected dispositivos, Home Assistant integration, app version, y permissions.