Home Assistant energy saving becomes more useful when an automation can read room context instead of following the clock alone. A schedule can turn an air conditioner off at a fixed time, but it cannot know whether a room became empty earlier or is still being used. A presence signal can add that missing context.
This guide shows how to combine a supported mmWave presence sensor, Home Assistant entities, environmental readings where available, and tested IR or device control. It also explains where the LinknLink App, Agent+, HomeClaw, and iSG Display Max fit. The goal is a reviewable automation workflow, not a promise of a particular energy result.
eMotion Air is a battery-powered presence-sensing option for supported room-context workflows.How Presence-Based Energy Automation Works
The basic path is simple:
- A sensor reports a supported room state.
- Home Assistant exposes that state as an entity or condition.
- An automation applies a time delay, temperature threshold, or other user-defined condition.
- A supported device receives the action through its configured integration or IR path.
The sensor does not directly turn an air conditioner or light on and off. Home Assistant holds the automation logic, and the final command depends on the device integration. For example, eMotion Air can provide presence, light, temperature, and humidity data through its supported Bluetooth or Zigbee path; eMotion Pro uses its documented Wi-Fi and MQTT Home Assistant path and includes built-in IR for supported appliance workflows. A separate IR controller such as eRemote HA can provide an IR-to-MQTT path where the appliance and setup are compatible.
Agent+ belongs above these layers. It can help a user understand connected devices, describe a desired scene, or review a proposed workflow when the relevant app version, permission, and integration support it. Agent+ is not the presence sensor, IR hardware, or a replacement for Home Assistant.
Why Presence Can Improve Energy Automations
Presence adds context to a rule. Compare these two examples:
- Schedule-only: turn the AC off at 10 PM.
- Context-aware: if the room has been unoccupied for a user-defined period, take the configured comfort or energy action.
The second rule can respond to how a room is being used. It still needs sensible delays, an accurate installation, and a manual path. Presence does not always reduce energy use; the result depends on the setpoint, climate, appliance behavior, timing, and the automation choices made by the household.
Use a delay to protect comfort
A short absence can be a person moving between rooms, getting a drink, or standing outside the sensing area. A vacancy delay gives the user time to return before an action is sent. The exact value is a configuration choice and should be tested in the actual room rather than copied as a universal number.
Example 1 — AC Control When a Room Becomes Unoccupied
A practical workflow looks like this:
eMotion Air or eMotion Pro → occupancy state → Home Assistant → defined delay → eRemote HA or supported IR path → AC command.
Before adding the rule, confirm that the air conditioner responds to the selected IR commands and that Home Assistant shows the expected entity or automation state. Test the IR action independently. Then add the presence condition and a delay. Keep a manual override in the LinknLink App, Home Assistant dashboard, or the appliance remote so a person can restore comfort without waiting for the next sensor event.
IR is command-based rather than a universal feedback channel. The device may receive an off or temperature command without Home Assistant knowing every detail of the appliance's current physical state. Treat the automation as a configured workflow for a supported appliance, not as a guarantee that every AC model will behave identically.
Example 2 — Presence + Temperature Conditions
When the selected sensor exposes the required environmental data, temperature can refine a presence automation. A simple pattern is:
- Room is occupied and the temperature is above a configured threshold: run the supported cooling workflow.
- Room is unoccupied for the defined period: send the configured reduction or stop action.
Use the readings that the particular product and integration actually provide. Do not assume that every sensor exposes temperature or humidity to every platform. Avoid describing Agent+ as determining an ideal temperature automatically; the threshold and action remain user-configured and device-dependent.
Keep the condition readable
Name entities by room and purpose, such as “Living Room Presence” and “Living Room Temperature.” A readable condition makes it easier to review the automation later, whether the rule was built manually or prepared with natural-language assistance.
Example 3 — Lighting and Room Activity
Presence can also provide context for supported smart lighting. When a room becomes occupied, Home Assistant can run a configured light scene. When it remains unoccupied for a defined period, the automation can turn the lights off or restore a chosen state.
The sensor supplies the state; Home Assistant evaluates the condition; the lighting integration performs the action. eMotion Air does not directly control a light without that supported path. Start with one room and one reversible scene, then watch the state changes for a few days before expanding to multiple rooms.
Where LinknLink AI Agent Helps
AI assistance is most useful when it reduces configuration friction while leaving the underlying capability clear. In a supported LinknLink App workflow, Agent+ may help you:
- Understand setup: identify connected devices, room assignments, entities, and integration relationships.
- Describe control intent: express a supported request in natural language instead of searching through every menu.
- Prepare a scene or automation: turn “when nobody is in the room, turn off the AC after a delay” into a proposed workflow or supported automation structure.
- Review conditions: inspect state, entity availability, delays, and action scope when the current diagnostic workflow supports it.
These are different stages: suggest, prepare, create, review, and execute. Whether an action can be created or executed depends on the connected platform, permissions, device support, and current app release. Keep final review with the user. Agent+ does not add mmWave sensing, IR transmission, or Home Assistant entities by itself.
AI Agent Beyond the Smart Home
LinknLink AI Agent is also positioned as an everyday assistance layer. The current LinknLink App materials describe supported workflows that can include information search and summarization, connected message or email assistance, calendar events, writing, and everyday planning. Availability depends on the current app version, account connection, and permissions.
That broader positioning matters in practice: a user might ask for a short automation checklist, prepare a calendar reminder for filter maintenance, or summarize setup notes, then return to the smart home workflow. Image creation and other creative tools should be treated as release- and tool-dependent. This guide does not claim universal access to every service, mailbox, calendar, model, or media workflow. MULTI_MODEL_CAPABILITY: HOLD.
HomeClaw for AI + Home Assistant Workflows
HomeClaw is positioned as an AI smart home gateway for supported Home Assistant workflows. It can provide a local-first path for users who want AI interaction close to the home, while the LinknLink App provides the everyday control surface. The exact behavior depends on the connected Home Assistant entities, integrations, permissions, and supported software path.
HomeClaw is not required for every LinknLink App action, and it does not make every device or protocol compatible. Keep the hardware, Home Assistant, App, and AI layers separate when planning a system.
iSG Display Max as a Home Control Surface
iSG Display Max can serve as a fixed Home Assistant dashboard and shared room control surface.iSG Display Max is best understood here as a fixed smart home dashboard and Home Assistant control center. It gives household members another way to view rooms, scenes, and supported controls. It is not the AI Agent processing core, and it does not replace the sensor or appliance integration.
Best Practices for Smart Home Energy Automation
- Start with one room and one measurable outcome.
- Use clear room and entity names.
- Verify the presence state before adding a device action.
- Use a defined vacancy delay and adjust it after observing the room.
- Test IR commands independently before combining them with presence.
- Retain a manual override.
- Review any AI-assisted automation before creating or enabling it.
- Document which product supplies each signal and which integration performs each action.
For deeper setup context, compare the mmWave presence sensor guide, the Home Assistant IR blaster guide, and the AI Agent safety checklist.
Common Questions
Can Home Assistant use presence sensors to reduce unnecessary HVAC use?
Yes, when the sensor exposes a supported presence state and Home Assistant can use it in an automation. The action, delay, and device response remain user-configured, so the workflow should be tested in the actual room.
Can a mmWave presence sensor control an air conditioner?
The sensor provides room context. Home Assistant and a supported device or IR path perform the action. A compatible IR controller or a product with built-in IR may be required, and the command should be tested separately.
How does IR AC control work with Home Assistant?
An IR device sends supported remote commands through the configured Home Assistant path. Confirm the appliance model, command coverage, integration, and whether state feedback is available before relying on the automation.
Where does LinknLink AI Agent fit into the automation?
Agent+ is a natural-language and AI assistance layer. It can help explain connected devices or prepare and review supported scenes and automations; it is not the sensor, IR transmitter, or Home Assistant automation engine.
Can AI Agent create Home Assistant automations?
Where the current app version and connected workflow support it, Agent+ can help turn a natural-language goal into a proposed or supported automation. Review the entities, conditions, delay, and actions before enabling it.
Do I need HomeClaw to use LinknLink AI Agent?
No. HomeClaw is an optional Home Assistant-centered AI gateway path. The required setup depends on the specific App workflow, account, integration, and device path.
Next step: Start with the LinknLink App, choose a supported room context, and use the Home Assistant room scene guide to keep the automation reviewable.