Natural-language control is useful when the goal is clear but the device path is not. A request such as preparing a room for movie time may involve a light, a media player, a presence state and an IR controller. LinknLink App Agent+ can help organize that intent into a proposed workflow when the relevant capabilities and permissions are available.
This guide focuses on the handoff between the request and Home Assistant. It does not assume that every integration supports the same action. Review the proposed entities, conditions and commands before enabling a scene, especially when it controls climate, locks, access devices or other household systems.
What an Automation Handoff Means
Intent
Describe the desired household result, room and timing in plain language.
Handoff
Convert the request into visible triggers, conditions, entities and actions.
Approval
Check the plan in LinknLink App or Home Assistant before the automation runs.
The handoff is the point where an Agent turns a household goal into a structured automation that can be checked in the target system. The request, room, trigger, conditions and actions should remain visible so a person can correct scope before the routine changes a device.
Before You Start
- Choose one Home Assistant area and name the devices using room-first labels.
- Confirm which LinknLink App, Agent+ and Home Assistant capabilities are available in the current setup.
- List the intended trigger, presence condition, target device and expected end state.
- Decide which actions are read-only, which create a draft and which require direct confirmation.
- Keep locks, alarms, garage doors, purchases and destructive file actions outside silent execution.
- Select a low-impact first action such as one light, a notification or a media pause command.
Build a Reviewable Agent+ Automation Handoff
1. State the household intent
Describe the result, room and time window instead of starting with a list of menu clicks.
2. Set the boundary
Name the Home Assistant area, permitted devices and actions that must not be included.
3. Map the trigger
Choose a button event, schedule, presence transition or other supported trigger.
4. Add context
Use eMotion Air, eMotion Pro or eMotion Ultra presence entities when occupancy changes the decision.
5. Separate device actions
List lights, media, climate and IR or RF commands as separate reviewable actions.
6. Ask for the handoff
Request a structured preview containing the trigger, conditions, entities, services and assumptions.
7. Check entity identity
Verify each entity belongs to the correct room and device before approving the plan.
8. Run a low-impact test
Test one visible and reversible action while observing the trigger and resulting state.
9. Add appliance control
If an AC or TV is involved, use a compatible IR controller such as eRemote HA and test the command independently.
10. Define fallback behavior
Specify what happens when the sensor is unavailable, the room is vacant or a device does not respond.
Example Prompts and What to Review
| Use case | Example request | Review before action |
|---|---|---|
| Movie mode | Prepare a living-room movie scene when the room is occupied and show every light and media action before approval. | Area, presence state, media player and light entities |
| Work mode | Create a desk-light handoff for the office during work hours, but do not control climate yet. | Time window, office presence and one light |
| Cooling request | When the bedroom is occupied, prepare one cooling command and show the IR target before running it. | Compatible IR controller, appliance and manual override |
| Vacancy guard | If the room is vacant, turn the request into a notification instead of starting the full scene. | Vacancy delay and fallback action |
| Media pause | When no one remains in the room, propose a media pause action and keep it reviewable. | Presence transition, player and delay |
| Manual exception | If the user changed the light manually, show the difference and wait for confirmation. | Current state, proposed state and approval |
Use Read, Prepare, Approve and Execute Stages
| Stage | Agent task | User control |
|---|---|---|
| Read | Inspect only the permitted source. | Choose the app, date range, room, folder or account. |
| Prepare | Extract entities and build a draft or proposed plan. | Check assumptions, missing information and affected resources. |
| Approve | Present the action and destination. | Confirm or revise before execution. |
| Execute | Run the supported action after approval. | Verify the result and keep a reversal path when possible. |
Review Checklist
- Does the request name the correct room and expected result?
- Are the trigger and presence condition mapped to the intended entities?
- Are light, media, climate and IR or RF actions separated for review?
- Does the proposed handoff include unavailable and vacant-room behavior?
- Are sensitive devices excluded from silent execution?
- Can each action be tested and reversed independently?
- Does the target Home Assistant automation show the same entities as the Agent preview?
- Was the smallest useful action tested before expanding the scene?
Privacy, Permissions and Safer Defaults
Cross-app tasks can touch personal communications, calendars, files, photos, locations and household devices. Grant the smallest useful permission, keep unrelated data out of scope and avoid sharing credentials, passwords, one-time codes or private account details.
Use drafts for messages and attachments. Use scene previews for smart-home changes. Keep purchases, access control, security devices and destructive file actions behind explicit human confirmation.
Troubleshooting
The Agent selects the wrong room
Use the exact Home Assistant area and entity names, then request a new preview with the old scope excluded.
Presence is not part of the handoff
Confirm that the relevant sensor entity is exposed to the integration and add the occupancy rule explicitly.
The plan contains too many actions
Split the request into read, prepare, approve and execute stages, starting with one device.
The IR appliance does not respond
Test the compatible IR controller and command manually before adding it to the Agent handoff.
A routine runs after the room is vacant
Review the vacancy delay, automation mode and fallback path, then test an occupied-to-vacant transition.
The proposed state differs from Home Assistant
Compare entity IDs, services, device availability and current state rather than relying on display names alone.
Related LinknLink Products
- eMotion Air: battery-powered mmWave presence context for room automations.
- eMotion Pro: mmWave presence sensing for supported Home Assistant workflows.
- eMotion Ultra: 60GHz presence, Temperature and Humidity Sensor Cable support and built-in IR.
- eRemote HA: compatible IR appliance control for Home Assistant.
- HomeClaw: a local Home Assistant and AI gateway path.
Related LinknLink App and Home Assistant Guides
- Home Assistant AI Agent Room Scene Guide
- Home Assistant AI Agent Safety Checklist
- LinknLink AI Agent Shopping List and Home Tasks Guide
- LinknLink AI Agent Home Maintenance Tasks Guide
- eMotion Air Home Assistant Setup Guide
- Home Assistant IR Blaster Troubleshooting Guide
Frequently Asked Questions
What is an Agent+ automation handoff?
It is a reviewable transition from a natural-language household goal to a structured Home Assistant plan with triggers, conditions, entities and actions.
Does Agent+ replace Home Assistant?
No. Home Assistant remains the target automation environment when the integration is supported. Agent+ helps organize the request and prepare the proposed work.
Can presence sensors be part of the handoff?
They can provide room context when the integration exposes their entities. Check the area, state and availability before approving the automation.
Can the handoff control an air conditioner?
A compatible IR controller such as eRemote HA is required for supported Home Assistant appliance control. Test the command separately and keep a manual override.
What should be the first Agent+ automation?
Start with one room and one reversible action such as a light, notification or media pause. Add climate and multi-device behavior after the first test.
How should sensitive actions be handled?
Locks, alarms, access devices, purchases, messages and destructive actions should require direct human review rather than silent execution.
Start with One Room and One Reversible Action
Choose one room, one trigger and one low-impact action. Ask Agent+ to show the proposed Home Assistant handoff, verify the entities, then expand the scene only after the first run is clear.