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