Many smart home users want to know whether a room is occupied, not who is in it. That distinction is central to privacy-conscious automation. A mmWave presence sensor can provide room context for supported Home Assistant workflows without creating a video image, while the rest of the system determines what action to take.
This guide explains camera-free presence automations for lighting, climate, room state, and user-configured notifications. It also shows how the LinknLink App, Agent+, HomeClaw, and iSG Display Max fit around the sensing and automation layers. Presence is not identity, a health state, or an emergency signal.
eMotion Ultra is a mmWave presence-sensing option for supported Home Assistant and room-context workflows.What a Presence Sensor Actually Tells Home Assistant
A supported presence integration can expose an occupied or unoccupied state, and some products can expose additional environmental readings. Home Assistant can use those entities as conditions for a scene, routine, climate action, or notification.
The signal does not identify a person. It does not explain why someone is stationary, determine a health state, or guarantee that a notification will reach a person. Treat it as room context. The useful question is usually “Is this room occupied for this automation?” rather than “Who exactly is present?”
Product capability still matters. eMotion Air uses 24GHz mmWave and a battery-powered Bluetooth or Zigbee path for supported presence, light, temperature, humidity, and button data. eMotion Pro uses 24GHz sensing with Wi-Fi and MQTT Home Assistant connectivity and built-in IR for supported appliance workflows. eMotion Ultra uses 60GHz sensing with its documented Wi-Fi, MQTT, environmental, and IR paths. Always confirm the product page and current integration before building a rule.
Camera-Free Smart Home Context
A camera can provide visual information and potentially more semantic context, but it also introduces a different privacy decision. A mmWave presence sensor provides occupancy context without producing a video image. That narrower signal can be a good fit for users who want automations based on room activity while limiting visual data.
MmWave does not replace cameras in every use case. It simply answers a different, narrower question. Choose the sensor and integration based on the action you want to automate, the room layout, the required data, and the privacy boundary of the household.
Keep the data path understandable
Document which device supplies the signal, how it reaches Home Assistant, and which automation uses it. For eMotion Air, the Bluetooth or Zigbee route must be supported by the selected bridge or integration. For Wi-Fi products, use the documented Wi-Fi, MQTT, or other supported path. A clear data path is easier to review than a collection of unnamed entities.
Example 1 — Night-Time Lighting
A camera-free night-light workflow can use a time condition, a presence state, and a supported light integration:
- After a user-defined evening time, a hallway or bedroom reports presence.
- Home Assistant checks the configured condition.
- A supported light scene turns on at the chosen brightness.
- After the room remains unoccupied for a defined period, Home Assistant restores or turns off the light.
This is a comfort and visibility automation, not a clinical or emergency service. Keep manual control available and choose a delay that matches how people actually move through the room.
Example 2 — Long Inactivity Notification
Some households may want a reminder when a room does not report the expected activity state during a user-defined time window. Home Assistant can use that state to trigger a configured notification through a supported channel.
This is a user-configured smart home notification, not a clinical or emergency alert. It cannot confirm why a room is inactive, identify a person, or guarantee that somebody has seen the message. Use neutral language in the notification, define the time window deliberately, and provide a way to dismiss or adjust it.
Make the notification proportional
Start with a low-consequence reminder such as “Check the studio room state.” Review how often it appears, whether the sensor placement fits the room, and whether the notification channel is appropriate. A sensor event should inform a workflow, not be treated as a complete account of a person's condition.
Example 3 — Room Climate Based on Occupancy
Presence and temperature can work together in a supported climate workflow. When a room is occupied and the temperature crosses a configured threshold, Home Assistant can run a selected climate scene. When the room remains unoccupied, it can apply a user-defined reduction or stop action.
Use the readings that the specific sensor provides. Do not assume that a presence sensor exposes every environmental entity through every integration. The automation is about occupancy context and comfort settings; it is not health analysis.
eMotion Air, Pro, and Ultra — Choosing the Right Presence Sensor
There is no single best sensor for every room. Choose based on power, network path, sensing technology, and the Home Assistant entities you actually need.
| Product | Relevant documented characteristics | Planning question |
|---|---|---|
| eMotion Air | Battery-powered 24GHz mmWave sensing, light, temperature, humidity, button, and Bluetooth/Zigbee paths. | Is a flexible battery installation and supported bridge path suitable for this room? |
| eMotion Pro | 24GHz presence sensing, Wi-Fi and MQTT Home Assistant connectivity, light sensing, and built-in IR for supported appliances. | Would a powered Wi-Fi/MQTT path and built-in IR simplify the intended room workflow? |
| eMotion Ultra | 60GHz sensing with documented Wi-Fi, MQTT Home Assistant, temperature/humidity, and built-in IR paths. | Do the room and integration require the documented Ultra sensing and connectivity options? |
These products are not interchangeable by default. Check the current product page, firmware, integration path, power needs, and room placement before choosing one. Presence sensing is a hardware capability; Home Assistant supplies supported entities and automation logic.
Add AI Agent to the Workflow
Agent+ sits at the interaction layer. It can make a supported workflow easier to describe and review, but it does not add sensing or protocol support.
Configure
When supported by the current app and integration, Agent+ can help users understand connected devices, rooms, entities, and relationships. Keep the actual device and integration boundaries visible.
Control
A user can express a supported smart-home request in natural language. The resulting action still depends on the permitted entities and connected device path.
Create
Agent+ can help organize a request such as “When presence is detected after 10 PM, turn on the hallway light” into a scene or automation workflow where that creation path is supported. Review the trigger, conditions, delay, and action before enabling it.
Diagnose
Where supported, Agent+ can help interpret current state, entity availability, and automation conditions. It should not be described as sensor intelligence, automatic repair, or a replacement for Home Assistant.
AI Agent Beyond Home Automation
The LinknLink App also presents Agent+ as an everyday assistance layer. Depending on the current release, account, and permissions, supported workflows can include information search and summarization, connected email or message assistance, calendar events, writing, and everyday planning. These capabilities are separate from presence sensing.
Image creation and other creative tools are release- and tool-dependent. This guide does not claim universal translation, video creation, video editing, or access to every service. The useful product distinction is simple: AI Agent helps users interact with supported systems; it does not turn a sensor into an identity or health-analysis device.
HomeClaw Positioning
HomeClaw can extend the LinknLink environment with a Home Assistant-centered AI gateway path for supported entities and automations. It keeps the architecture explicit: sensors provide data, Home Assistant provides the entities and automation logic, the LinknLink App provides interaction, and Agent+ provides a natural-language assistance layer.
HomeClaw is not a universal compatibility bridge and does not make every protocol or device available. Confirm the connected setup before relying on a particular action.
iSG Display Max Positioning
iSG Display Max can serve as a fixed Home Assistant dashboard and family-facing control surface. It is useful when a household wants presence, climate, scenes, and supported controls visible in one room. It is not the presence sensor or the AI Agent processing core.
Best Practices for Privacy-Conscious Automations
- Define the smallest room context needed for the automation.
- Use clear entity names and document the Bluetooth, Zigbee, Wi-Fi, or MQTT path.
- Choose a vacancy delay that matches the room rather than treating one value as universal.
- Use neutral notification language.
- Keep manual controls and a review path.
- Do not infer identity, health, or emergencies from a presence state.
- Review AI-assisted scenes and automations before enabling them.
- Link only the products and integrations that the room actually needs.
For more detail, see the mmWave presence sensor guide, the room occupancy helper guide, and the AI Agent safety checklist.
Common Questions
Does a Home Assistant presence sensor identify people?
No. A supported presence sensor provides room context such as occupied or unoccupied state. It should not be used to claim identity, health state, or a reason for inactivity.
Can mmWave presence automation work without a camera?
Yes, for workflows that only need supported room presence context. A mmWave sensor does not create a video image, but it also does not provide every kind of visual context that a camera can provide.
Can presence control lights or climate?
Presence can be a Home Assistant condition for supported lighting or climate workflows. The sensor does not directly control every device; the integration and automation perform the action.
Is a long-inactivity notification an emergency alert?
No. It is a user-configured smart-home notification. It cannot confirm a person's condition or guarantee delivery or response.
Which LinknLink sensor should I choose?
Compare the power source, sensing technology, environmental entities, network path, and IR requirements. eMotion Air, Pro, and Ultra have different documented characteristics; use the product page and current integration path as the source of truth.
Do I need HomeClaw for camera-free presence automation?
No. HomeClaw is an optional AI gateway path. A camera-free presence workflow can use the sensor's supported path and Home Assistant without making HomeClaw a requirement.
Next step: Review the LinknLink App, choose one room context, and document the sensor-to-Home Assistant path before adding a second automation.