HomeClaw + eMotion Ultra: Local Presence Automation Guide for Home Assistant

HomeClaw + eMotion Ultra: Local Presence Automation Guide for Home Assistant

HomeClaw and eMotion Ultra solve different parts of a Home Assistant setup. HomeClaw provides a local AI gateway path for organizing and preparing smart-home workflows, while eMotion Ultra supplies 60GHz presence data, temperature and humidity context through its sensor cable, and built-in IR control.

This guide turns that combination into a reviewable workflow. It does not assume that an AI request should immediately change a device. Start by exposing the smallest useful set of entities, inspect the proposed automation and approve one reversible action before expanding the routine.

HomeClaw private AI gateway for Home Assistant local smart home control

What This AI Agent Workflow Does

Local gateway layer

Use HomeClaw as the local Home Assistant and AI gateway path for planning and reviewing routines.

Presence and climate context

Use eMotion Ultra presence, temperature and humidity entities as separate automation inputs.

Room control

Use the built-in IR function for compatible appliances only after the command has been tested.

The Agent interprets the goal and prepares supported work, while the target application provides the data, permissions and actions. Availability can vary by operating system, region, app version and connected service.

Before You Start

  • Install Home Assistant on the supported HomeClaw path and confirm the local gateway is reachable.
  • Add eMotion Ultra to the LinknLink environment and verify its 60GHz presence entity.
  • Connect the included Temperature and Humidity Sensor Cable to eMotion Ultra and confirm both readings separately.
  • Name the room, presence entity, climate entities and IR target clearly before asking for a routine.
  • Keep a manual override and a rollback path for every device action used during testing.
Control note: Start with read-only review or a draft. Confirm recipients, dates, files, locations and smart-home devices before any external or sensitive action.

Step-by-Step Workflow

1. Build the entity map

Record the eMotion Ultra presence, temperature and humidity entities, then identify the compatible IR appliance in the same room.

2. Start with read-only context

Ask HomeClaw to summarize the available room signals and point out missing or stale values without changing a device.

3. Define the decision

State the occupied or vacant condition, a temperature or humidity threshold, the delay and the intended appliance action.

4. Prepare the Home Assistant automation

Let the supported workflow prepare a draft with trigger, conditions, action and cooldown instead of activating it immediately.

5. Review the safety boundaries

Check that vacancy delays, manual override, time windows and the intended IR target match the room use case.

6. Approve and test one action

Run the smallest reversible test, verify the result in Home Assistant and adjust thresholds before expanding the routine.

Example Prompts and What to Review

Use case Example request Review before action
Read-only room summary Summarize the living room presence, temperature and humidity entities from the last 30 minutes. Do not change any device. Entity names, timestamps and missing values
Comfort draft Prepare a Home Assistant routine that considers the room occupied and temperature above 26 C, then suggest an IR cooling action after a 5-minute confirmation delay. Trigger, threshold, delay, target appliance and manual override
Vacancy draft Draft a vacancy routine for the office using eMotion Ultra presence. Keep the lights unchanged and show the proposed next step. No false vacancy during quiet work, sleep or reading
Humidity review Compare the current humidity reading with my chosen threshold and suggest a Home Assistant notification plan without sending it. Threshold, notification destination and draft-only behavior
Manual test Show the exact IR command that would be tested for the living-room appliance, then wait for my confirmation. Correct room, appliance, command and approval step
Prompt pattern: State the goal, define the permitted scope, add constraints, name prohibited actions and request a preview before execution.

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

  • Are the presence, temperature and humidity entities mapped to the correct room?
  • Does the draft include a confirmation delay and a manual override?
  • Is the IR target compatible and clearly named?
  • Are the temperature and humidity thresholds appropriate for the room and season?
  • Can the routine be disabled or reversed without changing unrelated devices?

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

HomeClaw cannot see the entities

Confirm the Home Assistant connection, entity exposure and room names. Start with one device or sensor group before expanding the scope.

The temperature or humidity value is missing

Check that the Temperature and Humidity Sensor Cable is fully connected to eMotion Ultra and that the two entities update independently.

The room is marked vacant too soon

Increase the vacancy delay, review the detection placement and avoid using a single short observation window as the only condition.

The IR action is not reliable

Test the appliance command manually, confirm line of sight and keep the action behind an explicit approval until the result is stable.

Related LinknLink Products

  • HomeClaw: a local Home Assistant and AI gateway path.
  • eMotion Ultra: 60GHz presence, climate context through its sensor cable, and built-in IR.
  • eMotion Pro: 24GHz room presence and supported automation signals.
  • eRemote HA: local IR control for compatible appliances in Home Assistant.
  • eHome HA: IR/RF control and Home Assistant workflows.

Related LinknLink App and Home Assistant Guides

Frequently Asked Questions

What does HomeClaw add to an eMotion Ultra Home Assistant setup?

HomeClaw can provide a local AI gateway path for organizing, reviewing and preparing supported Home Assistant workflows, while eMotion Ultra provides presence, climate-context and IR inputs.

Does eMotion Ultra include the Temperature and Humidity Sensor Cable?

Yes. The cable is included with eMotion Ultra. eMotion Pro supports the hardware but requires the cable to be purchased separately.

Should presence, temperature and humidity be one Home Assistant trigger?

Usually keep them as separate entities and combine them with explicit conditions, delays and manual override so each signal can be tested independently.

Can HomeClaw activate an IR routine automatically?

Use a review-first workflow during setup. Confirm the target appliance, command, schedule and fallback before enabling any automatic action.

Is this setup suitable for local-first smart-home workflows?

It can be a suitable local-first path when the Home Assistant connection, device permissions and supported integrations are configured locally; verify the actual deployment before relying on it.

Start with One Reviewable Action

Choose one bounded task, ask the Agent to show its plan and approve only the smallest useful action. Verify the result in the target app before expanding the workflow.