Local AI in a smart home is not only a model question. The useful test is whether a gateway can understand a goal, work within the connected Home Assistant context, show its assumptions and keep sensitive actions behind human approval.
This Guide presents a repeatable evaluation path for HomeClaw and LinknLink Agent+ workflows. It separates local network reachability, supported device context, privacy boundaries and action review so a result can be compared across rooms and tasks.
What to Evaluate in a Local AI Gateway
Check the boundary
Identify which data, entities and services are in scope before asking for an action.
Test the workflow
Move from read-only inspection to a prepared action and then one approved reversible change.
Verify the result
Confirm device state, logs and manual control after the gateway completes the test.
A gateway evaluation should cover the network path, supported integrations, entity scope, privacy boundary, response quality and human approval flow. A useful test is small, repeatable and reversible rather than a large automation with many hidden assumptions.
Before You Start
- Define one Home Assistant room and one narrow question for the first evaluation.
- Record the gateway, Home Assistant host, network path and relevant integration versions.
- List the entities the workflow may read and the services it may prepare.
- Keep access control, purchases, security devices and destructive actions out of the first test.
- Use a reversible light, climate or media action if an execution test is needed.
- Decide how the result will be verified in Home Assistant after approval.
Evaluate HomeClaw and Agent+ with a Bounded Home Assistant Test
1. Define the evaluation question
State the desired answer or outcome, such as room status, device availability or a proposed scene.
2. Map the local path
Record where HomeClaw, Home Assistant, sensors and controlled devices sit on the network.
3. Set the entity scope
Name the room, entities and services allowed in the test; exclude unrelated rooms and personal data.
4. Run a read-only request
Ask for a current state summary without changing a device or configuration.
5. Check the interpretation
Compare the response with Home Assistant states, units, timestamps and entity names.
6. Ask for a prepared plan
Request the trigger, conditions, target entities, action and rollback note without execution.
7. Review privacy boundaries
Check what data was read, where the result is shown and whether unrelated context was included.
8. Test a presence scene
Use one eMotion sensor state and one room action to test how the workflow handles context and delay.
9. Test an appliance path
If an IR or RF command is needed, identify eRemote HA or eHome HA and verify the command separately.
10. Approve one action
Approve only the bounded, reversible action after checking its target, conditions and expected result.
11. Verify state and logs
Compare the device state and Home Assistant trace with the proposed plan and record any mismatch.
12. Record the evaluation
Keep the prompt, scope, response, approval, result and next constraint so future tests are comparable.
Example Prompts and What to Review
| Use case | Example request | Review before action |
|---|---|---|
| Read-only room status | Summarize the office presence, temperature and light state without making changes. | Entity scope, timestamps, units and unavailable states |
| Prepared scene | Prepare a reviewable evening scene for the living room using presence and climate context. | Trigger, delay, setpoint, lights and approval |
| Local network check | List the local gateway and Home Assistant connectivity checks before changing a device. | Host, address, integration state and manual fallback |
| Privacy review | Show which entities this task read and exclude unrelated rooms from the next request. | Data scope, result destination and excluded context |
| IR action | Prepare an AC command through eRemote HA after presence is confirmed, but do not run it yet. | IR target, command, room state, delay and approval |
| Recovery test | Explain how to stop the proposed scene and restore the last known state if the action is not correct. | Rollback, manual control and verification path |
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
- Is the first request read-only and limited to one room?
- Are the gateway, Home Assistant host and network path identified?
- Does the response use current entity state, units and timestamps?
- Are unrelated rooms, personal data and sensitive services outside the scope?
- Does the prepared plan show triggers, conditions, targets and rollback?
- Was the user asked to approve the action before execution?
- Was the result verified in Home Assistant after the action?
- Is the prompt and outcome recorded for a repeatable comparison?
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 names the wrong entity
Use the exact room and entity scope, review the entity registry and ask for the proposed target before execution.
The gateway cannot reach Home Assistant
Check local address, host status, integration credentials, firewall behavior and manual control before changing the workflow.
The response uses stale state
Compare timestamps and state history, then repeat a read-only request with a narrower entity scope.
A scene includes unrelated devices
Reduce the allowed room and entity list, ask for an explicit plan and exclude actions that are not needed.
The IR action is prepared but not correct
Verify the appliance command and eRemote HA or eHome HA path separately before adding presence or climate conditions.
A test needs to be stopped
Use the documented manual control or rollback step, then record the mismatch before running another evaluation.
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
- LinknLink App Feature Guide
- LinknLink Mobile Agent First Action Guide
- LinknLink App Automation Guide
- LinknLink App Agent+ Diagnostics Guide
- Free Home Assistant Remote Access with the LinknLink App
Frequently Asked Questions
What is a local AI gateway for Home Assistant?
It is a gateway path that helps connect an AI workflow with supported Home Assistant context and actions. The actual data and control boundary depends on the gateway, integration and configuration.
What should I test first with HomeClaw?
Start with a read-only question about one room and a small set of entities. Verify the answer before preparing or approving an action.
Does local AI mean every operation is offline?
Not necessarily. Check the product configuration, connected services and network behavior. The evaluation should document which data and services are used.
Can Agent+ control presence and climate scenes?
A supported workflow can help prepare a scene using relevant entities. Review the presence state, climate values, delay and target actions before enabling it.
Can HomeClaw work with IR devices?
When the required Home Assistant integration and compatible control path are configured, eRemote HA or eHome HA can be part of an IR/RF workflow. Test the command separately first.
How do I compare two gateway tests?
Keep the room, entity scope, prompt structure and verification method consistent, then compare interpretation, latency, action accuracy and recovery behavior.
Start with a Read-Only Home Assistant Question
Begin with one room and a read-only question about supported entities. Once the result is clear, prepare one reversible action and review every target before execution.