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