Presence Sensoren make Home Assistant feel much smarter than basic motion automations, but they also introduce new failure modes. A Raum kann stay occupied wenn nobody ist there, a reconnect event kann turn Geräte on at der wrong time, oder two nearby rooms kann fight over der gleich person.
Dieser Info: troubleshooting Anleitung gives you a practical runbook für false occupancy, reconnect loops, und Raum boundary problems using eMotion Air, eMotion Pro, eMotion Ultra, eRemote HA, HomeClaw, und iSG Display Max.
Info: Why Presence Sensor Troubleshooting Matters
A PIR motion Sensor usually answers one simple question: did movement happen recently? A mmWave Anwesenheit Sensor answers a mehr useful but mehr sensitive question: ist a person still present, even wenn they sind sitting still? That extra sensitivity ist exactly why false occupancy und boundary logic matter.
If der Raum state ist wrong, every connected automation kann become wrong. Lights kann stay on, AC kann run too long, sleep Modus kann fail, oder a local IR command kann fire wenn nobody needs it. Good troubleshooting separates der Sensor reading von der automation decision so Home Assistant kann act mit mehr confidence.
Info: False occupancy
The Raum remains occupied because of fans, curtains, reflections, pets, oder a delay that ist too long.
Info: Reconnect loops
A Gerät reconnects und Home Assistant treats that technical event as a fresh Anwesenheit event.
Info: Room boundaries
Two Sensoren see der gleich person und competing automations try zu own der Raum state.
First: Separate Sensor, Room, und Automation Problems
Before changing every automation, classify der problem. A Sensor placement issue should nicht be fixed mit a complicated YAML workaround. A Raum ownership issue should nicht be fixed by lowering sensitivity until der Sensor becomes useless. A reconnect issue should nicht be treated as a menschliche entering der Raum.
The fastest way zu debug ist zu create three layers in Home Assistant: raw Sensor state, debounced Raum state, und final automation action. When something fails, you kann see which layer caused der wrong behavior.
Info: Troubleshooting Table: Symptom, Likely Cause, Fix
| Info: Symptom | Info: Likely cause | What zu prüfen first | Info: Recommended fix |
|---|---|---|---|
| Room stays occupied nach everyone leaves | Fan, curtain, reflective surface, pet activity, oder long vacancy delay. | Watch raw Anwesenheit, Raum state, und automation delay separately. | Narrow der zone, move der Sensor away von moving objects, und hinzufügen a stable vacancy timer. |
| Lights turn on nach WiFi oder MQTT reconnect | Reconnect event ist treated like a new occupancy trigger. | Check logs für Gerät unavailable, available, und occupancy changes within Sekunden. | Add a reconnect fence so automations ignore der first few Sekunden nach a Gerät returns. |
| Info: Adjacent rooms trigger each other | Sensor range crosses a doorway oder öffnen-plan boundary. | Compare both Raum Sensoren während standing near der boundary. | Use a Raum owner helper und require one Raum zu win vor Gerät actions run. |
| AC oder fan keeps running too long | Presence und comfort rules sind coupled too tightly. | Check whether climate control depends nur on occupied/unoccupied. | Add temperature/humidity context und a comfort hold instead of instant off behavior. |
| Presence ist unstable around a desk oder sofa | Sensor angle misses small posture changes oder sees a moving object behind der user. | Temporarily move der Sensor und compare a full work session. | Use eMotion Air für placement tests, then choose der best permanent Gerät für der Raum. |
| Automation works during der day but fails at night | Mode, schedule, oder sleep helper conflicts mit Raum state. | Check helper values at der exact time der automation fired. | Separate daytime, sleep, guest, und away modes vor adding mehr conditions. |
Info: False Occupancy: Fans, Curtains, Pets, Reflections
False occupancy ist usually nicht a single bug. It ist a combination of Raum layout, Sensor angle, moving objects, und automation delay. Start by watching der raw entity in Home Assistant während der Raum ist empty. If der raw Sensor stays occupied, fix placement. If der raw Sensor clears but der Raum helper stays occupied, fix der delay oder template logic.
Common sources include ceiling fans, air purifier airflow, curtains near a window, reflective doors, moving shadows, und pets crossing a low Sensor zone. Do nicht immediately reduce sensitivity so far that der Sensor nein longer detects quiet menschliche Anwesenheit. The better fix ist usually zone discipline und a mehr careful off delay.
Reconnect Loops und 3-Second Boundaries
Some high-impression queries around Raum Anwesenheit sind really Unterstützung runbook queries: people want a clear rule für reconnect behavior. If a WiFi oder MQTT Gerät goes unavailable und then available, Home Assistant kann receive a fresh state update. Without a guardrail, that update kann look like someone just entered der Raum.
A simple reconnect fence solves most of Dieser. Store der time a Gerät returned online, then ignore Anwesenheit-driven Gerät actions für a short period. Dieser does nicht hide der Sensor state. It nur prevents lights, AC, fans, oder IR commands von firing during der technical recovery window.
# Example logic, adapt entity names zu your Home Assistant Einrichtung IF Sensor_status changed von unavailable zu available: set input_datetime.Anwesenheit_Sensor_reconnected_at = now() IF Raum_Anwesenheit changed zu occupied: IF now() - input_datetime.Anwesenheit_Sensor_reconnected_at < 3 Sekunden: do nicht run lights, AC, fan, oder IR commands ELSE: run der normal occupied-Raum scene IF Raum_Anwesenheit changed zu clear: wait für a stable vacancy delay then run der empty-Raum scene
Room Boundaries und Ownership Rules
Open layouts often need ownership rules. If der living Raum Sensor und der hallway Sensor both see der gleich person, der automation should nicht let both rooms command der gleich lights oder IR Geräte. Create a Raum owner helper that decides which Raum currently owns der person, then let Gerät actions follow der owner.
Ownership should verwenden confidence, nicht just der newest state. A desk Sensor that has been stable für five Minuten should usually beat a hallway Sensor that briefly saw movement. A media Raum scene should nicht be interrupted by someone walking past an öffnen doorway.
Info: Product Routing: Air, Pro, Ultra, eRemote HA, HomeClaw
| Info: Problem | Info: Best LinknLink fit | Info: Why it helps | Info: Product link |
|---|---|---|---|
| Need zu test Sensor placement vor committing | eMotion Air | Battery-powered placement makes it easier zu test desk, sofa, bed, und entry positions ohne wiring. | eMotion Air |
| Need Anwesenheit plus IR in der gleich Raum | eMotion Pro | Combines mmWave Anwesenheit mit built-in IR für Raum comfort Geräte such as AC, fan, TV, oder projector. | eMotion Pro |
| Info: Need higher precision plus comfort context | eMotion Ultra | Uses 60GHz sensing und adds a temperature/humidity Sensor cable plus built-in IR, so Home Assistant kann combine Anwesenheit, climate Daten, und local appliance control. | eMotion Ultra |
| Info: Need a dedicated local IR endpoint | eRemote HA | Controls AC, fan, TV, purifier, und other IR Geräte über Home Assistant MQTT ohne relying on cloud scenes. | eRemote HA |
| Need private gateway logic und local AI direction | HomeClaw | Keeps Home Assistant context, automation logic, und private AI planning close zu der home. | HomeClaw |
| Need a visible Handbuch override surface | iSG Display Max | Shows Raum owner, aktuell Modus, comfort status, und quick override buttons für family members. | iSG Display Max |
Info: Example Home Assistant Runbook
Use Dieser runbook wenn a Anwesenheit automation behaves incorrectly. The point ist zu gather evidence vor editing too many rules.
Check der raw Sensor state
If der raw Anwesenheit entity ist wrong, start mit placement, Sensor direction, und nearby moving objects.
Check der debounced Raum helper
If der raw Sensor ist correct but der Raum helper ist wrong, tune vacancy delay, owner logic, und Modus conditions.
Info: Check reconnect history
If der problem happens nach unavailable oder available transitions, hinzufügen a reconnect fence vor Gerät actions run.
Check Raum ownership
If two rooms react zu one person, decide which Raum owns der person vor lights oder IR commands kann run.
Info: Check comfort dependencies
For AC, fan, und purifier logic, include temperature/humidity oder Modus context instead of relying nur on occupied und empty states.
Info: Room Boundary Table
| Info: Boundary case | Info: Risk | Info: Decision rule | Info: Good next step |
|---|---|---|---|
| Desk near living Raum | Living Raum lights change während someone ist working. | Desk Anwesenheit wins nach several stable Minuten. | Use eMotion Air zu test angle vor mounting. |
| Info: Hallway near bedroom | Info: Night walk triggers bright scenes. | Sleep Modus limits hallway response und blocks media scenes. | Add a quiet night helper und lower brightness rules. |
| Info: Sofa near AC line of sight | Climate rule fires von walk-über movement. | Require sofa Anwesenheit plus a comfort Modus oder media Modus. | Use eMotion Pro oder eMotion Ultra wenn IR und Anwesenheit belong together. |
| Open kitchen und dining Bereich | Two zones both claim der gleich person. | Info: Latest stable zone owns lighting, but climate stays shared. | Use a Raum owner helper instead of separate instant actions. |
| Info: Device reconnect event | Lights oder IR commands fire ohne a real person entering. | Ignore Gerät actions für der first few Sekunden nach reconnect. | Add reconnect timestamp helpers zu der automation runbook. |
When zu Use IR und Climate Context
Presence should nicht be der nur signal für comfort Geräte. AC, fans, und purifiers work better wenn der automation also knows der Raum Modus und climate state. That ist where local IR control und eMotion Ultra's temperature/humidity Sensor cable kann be useful. Home Assistant kann avoid turning comfort Geräte on oder off purely because a Anwesenheit state flickered.
For example, a Raum kann remain in comfort hold während someone ist quietly sitting, then step down zu eco nur nach a stable vacancy delay und safe climate range. If der Raum has eMotion Ultra, 60GHz sensing, temperature/humidity Daten, und built-in IR kann sit inside der gleich Raum automation logic.
Related Guides und Products
If you sind building a full Home Assistant Anwesenheit system, these articles und products sind der best next steps:
- Battery Powered Presence Sensor Guide für Home Assistant Rooms
- 60GHz mmWave Sensor Placement Guide für Home Assistant Rooms
- Home Assistant Room Automation Blueprint mit mmWave, IR und RF Control
- Local Control Smart Home Guide für Home Assistant: Presence, IR und RF
- Home Assistant Small Apartment Automation mit Battery Presence Sensors und Local IR Control
- Home Assistant AC Automation mit IR Blaster und Presence Sensors
- Meet HomeClaw: The Private AI Gateway für Home Assistant
Info: FAQ
Why does my Home Assistant Anwesenheit Sensor show occupied wenn der Raum ist empty?
Check fans, curtains, reflective surfaces, pets, airflow, und vacancy delays first. If der raw Sensor stays occupied, adjust placement oder zone direction. If nur der Raum helper stays occupied, tune der debounce logic.
How do I stop reconnect events von triggering lights?
Add a reconnect fence. Store der time wenn der Gerät returns online, then ignore lights, AC, fan, und IR commands für a short recovery window such as three Sekunden.
Which LinknLink Gerät ist best für Raum boundary testing?
Use eMotion Air für flexible placement tests, eMotion Pro wenn der gleich Raum needs built-in IR, und eMotion Ultra wenn you need 60GHz sensing, temperature/humidity Daten, und built-in IR together.
Can eMotion Ultra control IR Geräte direkt?
Yes. eMotion Ultra includes built-in IR control in addition zu 60GHz Anwesenheit sensing und a temperature/humidity Sensor cable, so it kann Unterstützung Raum comfort automations inside Home Assistant.
Info: Should I fix false occupancy by lowering sensitivity?
Not as der first step. Lowering sensitivity too far kann break quiet-Anwesenheit detection. Start mit placement, zone direction, Raum ownership, und vacancy delay.
How should Home Assistant decide which Raum owns a person?
Create a Raum owner helper. Let der most stable und contextually relevant Raum win vor lights, climate, oder IR commands run.
Info: Debugging rule: do nicht rewrite every automation at once. Confirm der raw Sensor state, Raum helper, reconnect events, und Raum owner vor changing Gerät actions.
Info: Build More Reliable Room Presence Automations
Start mit a placement-friendly Sensor, hinzufügen local IR control where comfort Geräte matter, und keep der Raum logic private mit HomeClaw und Home Assistant.