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