Reliable guestroom occupancy detection combines a door contact with at least one motion or presence sensor, and treats the door as the only way in or out. Motion seen after the door closes latches the room as occupied until the door opens again; no motion within a verification window after the door closes marks it unoccupied. A motion timer on its own will switch off the air-conditioning on a sleeping guest.
This technical reference is written by Singapore-based AV and IPTV integrator Prestige Solutions for interior project managers, hotel engineers and consultants who specify or accept a smart room control system. It sets out the room states, the transitions between them, the timer values to start from, where sensors go, and the tests that prove the logic before handover. Timer and temperature figures are planning values as of 2026; the controller vendor's documentation and the hotel's own comfort standard decide the final settings.
Because a passive infrared (PIR) sensor detects movement, not presence. It responds to a warm body moving across its detection zones, so a guest who is asleep, reading in bed or sitting at the desk produces little or no signal. A room that relies on "no motion for 20 minutes means empty" will make the wrong decision every night.
The opposite shortcut fails as well. A key card holder reports that a card is in the slot, not that a person is in the room, and a spare card left in place keeps an empty room fully powered. Door-plus-motion logic removes both errors because it only has to answer one question after each door closure: did anyone stay inside?
Four inputs cover almost every design: a door contact, PIR motion sensors, radar presence sensors, and the key card holder. Each answers a different question, and the logic should use each one only for what it can actually tell.
| Input | What it detects | Strength | Known weakness |
|---|---|---|---|
| Door contact (magnetic reed switch) | Entry door open or closed | Marks every possible entry and exit; simple, low cost | Misaligned magnet or a door left ajar gives a permanent "open" |
| PIR motion sensor | Movement of a warm body across detection zones | Low power, suits battery and wireless devices, no emission | Blind to still or sleeping occupants; needs line of sight |
| mmWave radar presence sensor (commonly 24 GHz or 60 GHz) | Small movements, including breathing | Detects a stationary person | Higher power draw; can respond to curtains or fans moving, and may see through thin partitions |
| Key card holder | A card is inserted | Guest understands it; gives a clear "I am here" action | Does not prove presence; basic types accept any card |

Five states are enough for most hotels: unsold, sold-unoccupied, verifying, occupied and staff. The first two come from the property management system (PMS) room status; the others come from the sensors in the room. Keeping the commercial status and the physical status as separate inputs lets the same sensors produce different behaviour in a sold room and an unsold one.
| State | Entered when | Typical room behaviour | Leaves when |
|---|---|---|---|
| Unsold | PMS reports the room vacant or checked out | Deep setback, lights and switched sockets off, humidity limit still enforced | PMS check-in, or door opens (staff entry) |
| Sold-unoccupied | Verification window ends with no motion | Moderate setback, lights off, curtains per hotel standard | Door opens |
| Verifying | Door closes | No change to the room; the controller is counting | Motion seen (to occupied) or window expires (to unoccupied) |
| Occupied | Motion seen while the door is closed | Guest setpoint and scenes; nothing times out | Door opens (back to verifying after it closes) |
| Staff | Door opened with a staff card, or housekeeping status set | Work lighting, guest setpoint untouched | Staff status cleared and door closes |
The important property is in the "occupied" row: once motion is seen behind a closed door, the state is latched, because nobody can leave without opening the door. That single rule protects a sleeping guest.
Every door closure starts a verification window, and the first motion event inside that window decides the outcome. The sequence below can be handed to a vendor as a functional description and checked line by line during commissioning.
Start from the values below and adjust after the mock-up room has been lived in for a few days. They are planning values as of 2026, not manufacturer specifications.
| Parameter | Starting range | Effect of setting it too short | Effect of setting it too long |
|---|---|---|---|
| Verification window after door closes | 10 to 30 minutes | Guest who lies down straight away is marked absent | Empty room runs at full comfort for longer |
| Sensor settle time after door closes | 5 to 15 seconds ignored | The departing guest's last movement is counted as presence | A quick entry may be missed |
| Warning dim before lights off | 30 to 60 seconds | Lights cut without notice | Negligible |
| Door-ajar alarm | 3 to 5 minutes | Nuisance alarms during luggage delivery | Conditioned air lost to the corridor |
| Unoccupied temperature setback | 2 to 4 °C above guest setpoint (cooling) | Little saving | Slow recovery and humidity rise |
In a tropical climate the setback has a second limit: humidity. Specify the unoccupied mode as a raised setpoint with a humidity ceiling, not as cooling switched off, and let the mechanical engineer set the figure.

Place sensors so that the bed, the desk and the bathroom are each seen by at least one of them, and so that none looks out through the entry door. Coverage gaps cause false "unoccupied" decisions; a sensor with a view of the corridor causes false "occupied" ones.
Five situations account for most occupancy complaints, and each has a defined response. Writing them into the specification turns site arguments into test cases.
| Case | What goes wrong | Design response |
|---|---|---|
| Guest lies down immediately and does not move | No motion in the window; room set back with a guest inside | Longer window at night, radar presence sensor over the bed, or "do not disturb" and privacy latch treated as presence |
| Housekeeping props the door open | Room held in occupied state at guest setpoint | Staff state with its own setpoint; door-ajar timer |
| Door contact fails open | Room never leaves occupied; no saving | Server report of rooms with no door-close event in 24 hours |
| Motion sensor fails silent | Every closure ends in "unoccupied" | Server report of sold rooms with zero motion events in 24 hours; fall back to guest-setpoint mode |
| Pet, robot cleaner or curtain movement | False occupied latch | Sensitivity and mounting adjustment; accept as the lower-risk error |
The last row states a principle worth agreeing with the operator early: when the inputs disagree or a sensor is suspect, the room should fail towards "occupied". An empty room kept comfortable costs a little energy; an occupied room set back costs a complaint. How the same room behaves when it loses its server connection is covered in the failure mode reference for smart room control network loss.
Test the transitions, not just the devices. A sensor that lights its indicator when someone waves at it has not shown that the room will make the right decision at two in the morning.
| Test | Method | Pass criterion |
|---|---|---|
| Enter and stay | Enter, close door, move normally | Occupied latched within the settle time plus one sensor report |
| Still occupant | After latching, lie still on the bed for longer than the verification window | No change to lights or setpoint |
| Leave | Exit and close door; wait out the window | Warning dim, then lights off and setback at the configured time, within the agreed tolerance |
| Bathroom entry | Enter, go directly to the bathroom, close its door | Occupied latched |
| Two occupants | Two people in; one leaves | Room returns to occupied after the door closes |
| Sensor removed | Disconnect the motion sensor or remove its battery | Fault reported; room falls back to guest-setpoint mode |
Run the full table in the mock-up room and in every room type, then a reduced set on a sample of each floor. Sampling levels and defect classes are set out in the room-by-room commissioning checklist for smart room control. Record the final timer values per room type in the handover document. Related guestroom systems that share the same controller are listed on the Prestige Solutions home page.

Yes. The card holder can stay as a guest-facing switch for lighting while the door contact and motion sensor decide the air-conditioning setback. The controller then ignores a card left in the slot once the verification window ends with no motion, which removes the spare-card workaround without changing guest habits.
PIR, ultrasonic and radar sensors of the type used for room control output a presence or motion signal, not an image, and do not identify a person. The event log does show when a room was entered and left, so access to that log should be limited to the engineering and security roles the hotel defines.
It can be, as an indication and not a guarantee. A corridor indicator or housekeeping app showing "unoccupied" helps staff plan room attendance, but the logic can be wrong in the cases listed above, so staff procedure should still require knocking and announcing before entry.
Contact Prestige Solutions to review your site drawings and current operating pattern. Call +65 8010 2337 or +65 9825 8218, message us on WhatsApp (+65 8010 2337), or email sales@prestigesolutions.com.sg. You can also browse the full product range before the site walk.
Explore our full product range or speak with our technical team for a tailored consultation.