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