Home Assistant Presence Sensor Calibration Guide: Zones, Delays and False Positives

August 4, 2026

A presence sensor can report more useful room context than a simple motion trigger, but the result still depends on placement, detection zones, sensitivity, vacancy timing and the way Home Assistant combines entities.

This guide uses a controlled calibration process. It helps you separate sensor behavior from automation logic, reduce false occupancy states and create a testable foundation for lights, climate, IR or notification routines.

A Repeatable Calibration Workflow

Map the room

Document the sensor position, furniture, doorways and the areas that should count as occupied.

Tune one variable

Adjust placement, zone or vacancy delay one step at a time so the cause of a change is clear.

Verify the state

Test stillness, movement, doorway traffic and an empty room before enabling an automation.

Reliable presence automation starts with measured room behavior. Map the detection area, tune one variable at a time, test occupied and vacant states, then add the sensor to an automation only after the result is predictable.

Before You Start

Choose one room and record the sensor mounting height, angle and distance from the main activity area.
Name the presence, motion, temperature and automation entities clearly in Home Assistant.
Decide which areas should count as occupied and which adjacent spaces should be excluded.
Prepare a read-only dashboard or log so state changes can be reviewed after each test.
Keep a manual override and a conservative fallback for every automation used during calibration.

Control note: Start with read-only review or a draft. Confirm recipients, dates, files, locations and smart-home devices before any external or sensitive action.

Map, Tune, Test and Automate

1. Record the baseline

Observe the room while empty, occupied and quietly occupied. Note the state changes and timestamps before changing settings.

2. Check physical placement

Move the sensor only when needed, then retest the same positions so placement changes can be compared.

3. Define detection zones

Exclude doorways, reflective surfaces or adjacent rooms when the device and integration expose zone controls.

4. Tune the vacancy delay

Use a delay long enough to cover reading, resting or short trips across the room instead of switching to vacant immediately.

5. Test edge cases

Check quiet work, sleep, a person behind furniture, doorway traffic and an actually empty room.

6. Add Home Assistant conditions

Combine presence with time, temperature, humidity, media state or a helper only after the raw sensor state is understood.

7. Monitor before expanding

Keep the first automation in observation or notification mode and review several complete occupied-to-vacant cycles.

Example Prompts and What to Review

Use case	Example request	Review before action
Read-only baseline	Show the living-room presence state changes for the next 30 minutes without changing any device.	Timestamps, room state and missing or stale readings
Quiet work test	Check whether the office remains occupied while I sit still for 20 minutes. Do not enable an automation.	False vacancy, delay and sensor placement
Doorway exclusion	Compare the room state when someone walks past the doorway versus when someone stays in the room.	Zone boundary and adjacent-room detection
Vacancy draft	Prepare a Home Assistant draft that waits 15 minutes after vacancy before turning off the room lights.	Delay, target entities, manual override and rollback
Climate condition	Suggest a comfort routine only when the room is occupied and temperature is above the chosen threshold.	Presence entity, temperature entity, threshold and time window

Prompt pattern: State the goal, define the permitted scope, add constraints, name prohibited actions and request a preview before execution.

Use Read, Prepare, Approve and Execute Stages

Stage	Agent task	User control
Read	Inspect only the permitted source.	Choose the app, date range, room, folder or account.
Prepare	Extract entities and build a draft or proposed plan.	Check assumptions, missing information and affected resources.
Approve	Present the action and destination.	Confirm or revise before execution.
Execute	Run the supported action after approval.	Verify the result and keep a reversal path when possible.

Review Checklist

Does the sensor cover the intended room without treating a doorway or adjacent room as occupied?
Does quiet work or rest remain occupied for the expected duration?
Is the vacancy delay long enough for normal movement patterns?
Are raw sensor states separate from the final automation conditions?
Can the automation be paused or reversed without affecting unrelated rooms?

Privacy, Permissions and Safer Defaults

Cross-app tasks can touch personal communications, calendars, files, photos, locations and household devices. Grant the smallest useful permission, keep unrelated data out of scope and avoid sharing credentials, passwords, one-time codes or private account details.

Use drafts for messages and attachments. Use scene previews for smart-home changes. Keep purchases, access control, security devices and destructive file actions behind explicit human confirmation.

Troubleshooting

The room stays occupied after everyone leaves

Check zone boundaries, reflective surfaces and adjacent-room coverage, then test a longer empty-room observation before changing the automation.

The room becomes vacant while someone is sitting still

Review mounting position, detection range and vacancy delay. Test quietly occupied behavior before adding more conditions.

The sensor changes too often

Compare placement and zone settings one at a time, then add a short state-stability or debounce condition in Home Assistant.

The automation works in testing but not in daily use

Review time windows, helper states, entity availability and manual overrides. Keep the raw sensor history visible while diagnosing.

Frequently Asked Questions

What is the difference between motion and presence detection?

Motion detection normally reacts to movement, while presence detection can maintain an occupied state during supported periods of stillness. Actual behavior depends on the device, placement and integration.

How long should a Home Assistant presence sensor vacancy delay be?

There is no universal value. Start with the room's real movement pattern, test several empty-room cycles and choose a delay that avoids short false-vacant states.

How can I reduce false occupancy?

Map the room, exclude adjacent areas when possible, review reflective surfaces and verify the sensor's detection zone before changing automation actions.

Can presence be combined with temperature or humidity?

Yes, when those entities are available. Keep presence and climate data separate, then combine them with explicit thresholds, time windows and a manual override in Home Assistant.

Which LinknLink products can be used in a calibrated room workflow?

eMotion Air, eMotion Pro and eMotion Ultra provide different sensing capabilities. HomeClaw, iSG Display Max, eRemote HA and eHome HA can support different gateway or control roles depending on the configured Home Assistant setup.

Start with One Room and One Automation

Calibrate one room with a read-only dashboard first. Record the result, add a vacancy delay and manual override, then expand to another room only after the first routine behaves consistently.