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