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