Guestroom HVAC and Lighting Scene Interlocks
Q&A

Guestroom HVAC and Lighting Scene Interlocks

HOME > Q&A

Guestroom lighting scenes and HVAC should be linked by a written sequence of operation, not by ad hoc programming. The room controller owns the link: occupancy and key-card state decide the room mode, and each mode sets both a lighting scene and an HVAC setpoint and fan behaviour. When the sequence is written down with timing values, both the installer and the hotel engineering team can test it and diagnose it later.

This engineering note is written by Singapore-based AV and IPTV integrator Prestige Solutions for interior project managers and hotel engineering teams specifying smart room control in new or refurbished guestrooms. It sets out a reference sequence, the timing values we start from, how the room controller hands off to the building management system (BMS), and the interlock faults that most often reach handover untested. Values are typical starting points as of 2026 and should be agreed with the hotel's energy and comfort targets.

Room modes drive both lighting and HVAC

Define a small set of room modes and make every lighting and HVAC action a consequence of the mode. Programming lighting and air-conditioning as separate logic is the root cause of most conflicts, such as lights turning off while the fan coil stays on high in an empty room.

Room modeTriggerLightingHVAC
Unsold / vacantPMS status vacant, no occupancyAll offSetback, e.g. 27–28°C, fan auto-low
Sold, guest awayPMS checked-in, no key card, no occupancyAll offMild setback, e.g. 25–26°C
WelcomeKey card inserted after check-inWelcome scene (entry, bedside, curtains open if daytime)Guest setpoint, fan auto
OccupiedKey card present or occupancy detectedGuest-selected scenesGuest setpoint within limits, e.g. 20–26°C
SleepSleep or "all off" key at bedsideAll off except low-level night path lightSetpoint offset +1°C after a delay, fan low
Window / balcony door openDoor contact openNo changeFan coil off or fan only after a short delay
HousekeepingStaff card or service modeWork scene at full brightnessNo change from current mode
Hotel guestroom smart room control keypad with lighting and air-conditioning scenes
Every lighting and HVAC action should follow from a defined room mode.

Timing values we start from

Timing decides whether a room feels responsive or annoying, and it must be written into the specification rather than left to the programmer's defaults. The values below are our starting points; the hotel adjusts them during mock-up testing.

ParameterStarting valueReason
Key card removed to lights off15–30 sTime to leave the room with light
Key card removed to HVAC setback10–15 minAvoid cycling if the guest returns quickly
No occupancy (card present) to "guest away"30–60 min, only with reliable presence sensingHandles cards left in the holder
Balcony door open to fan coil off30–60 sIgnores brief opening, stops conditioning the outdoors
Sleep key to setpoint offset30 minComfort while falling asleep
Vacant room pre-cool before arrivalTriggered by PMS check-in or scheduled arrivalRoom comfortable on entry without cooling all day

In Singapore's climate, deep setbacks in vacant rooms need a humidity check. A room left at a high setpoint with the fan off for days can build humidity and odour; many hotels run a periodic dehumidification or fan cycle in vacant mode for that reason.

Controller and BMS responsibilities

The room controller should decide room mode and send setpoint and mode requests; the BMS should keep ownership of plant and central schedules. Splitting it this way keeps the guestroom working if the BMS link is lost and keeps plant safety logic where the mechanical engineer designed it.

  • Room controller: room mode, lighting scenes, fan coil valve and fan speed for the room, local setpoint limits, door and window interlocks.
  • BMS: chilled water plant, AHUs and fresh air, central schedules, alarms from fan coils, energy reporting.
  • Interface: typically BACnet/IP or Modbus TCP from the room control server or gateway to the BMS, or KNX to BACnet gateways on smaller sites. Agree the point list early: room mode, setpoint, actual temperature, fan speed, valve state, door contact, alarm.
  • PMS: check-in and check-out status to the room control server, so vacant and sold modes follow real occupancy.
Guestroom entry with key card holder, smart control panel and HVAC thermostat
The room controller decides room mode; the BMS keeps ownership of plant.

Lighting interfaces and scene ownership

Scenes should be defined once, in the lighting system or room controller, and recalled by number from everywhere else. With DALI lighting, scenes are stored in the drivers or a DALI gateway; with KNX or relay and dimmer channels in the room controller, scenes live in the controller configuration. Either way, keypads, the TV or IPTV app, and the mobile app should recall "scene 3" rather than set individual channel levels. This keeps the interior designer's levels intact and lets one change update every interface.

Interlock faults found at commissioning

Most interlock faults only appear when modes change, so testing must walk through transitions, not just scenes. These are the faults we most often find before handover:

FaultSymptomUsual cause
Fan coil stays on after checkoutVacant room fully cooledPMS status not mapped to vacant mode
Lights off while guest asleep in bathroomGuest complaint at nightNo occupancy sensor in bathroom; card removed by mistake
Balcony door contact reversedFan coil off when door is closedNormally-open versus normally-closed wiring mismatch
Guest setpoint ignoredThermostat shows change, room does not coolBMS schedule overriding the room controller
Welcome scene at 3 a.m. at full brightnessLate arrival discomfortNo time-of-day variant of the welcome scene
Rooms cycle between modesFan speed changes every few minutesPresence sensor too sensitive or poorly positioned

Transition test sequence

We test every room type through a fixed sequence of transitions, logging lighting and HVAC state at each step:

  1. Vacant room: confirm lights off and HVAC at vacant setback.
  2. Check in through the PMS: confirm pre-cool starts if specified.
  3. Insert key card: welcome scene and guest setpoint; repeat after 10 p.m. to confirm the night variant.
  4. Change scenes from each keypad, the TV and the app; confirm the same scene result.
  5. Open balcony door: fan coil stops within the set delay; close it: HVAC resumes.
  6. Press sleep: lights off except night path; setpoint offset applies after the delay.
  7. Remove key card: lights off within 15–30 s; HVAC setback after the set delay.
  8. Check out through the PMS: vacant mode applies.
  9. Disconnect the BMS link: room continues to operate locally.
Engineer commissioning guestroom lighting and HVAC control logic
Walk each room type through every transition, not only through each scene.

Handover items for diagnostics

Hand over the written sequence of operation, the timing table as commissioned, the BMS point list, the PMS mapping, and a transition test record per room type. With these, the engineering team can compare any complaint against the documented behaviour and see whether the fault is in the logic, a sensor or the BMS. Other hotel references are on the Prestige Solutions home page.

Energy and comfort settings to agree with the hotel

The timing and setpoint values in this note are commercial decisions as much as engineering ones, so the hotel's operations and engineering heads should sign them off before programming. Deeper vacant setbacks save more chilled water energy but take longer to recover when a guest arrives; a room at 28°C can take 20–40 minutes to feel comfortable, depending on the fan coil size and solar load. Pre-cooling on PMS check-in solves most of this, but only if front office checks guests in through the PMS rather than on paper during busy periods. Guest setpoint limits are another trade-off: a lower limit of 20°C protects the chiller plant and reduces condensation risk on cold surfaces, while some luxury brands allow 18°C. Record every agreed value in the sequence of operation with the date and the approver, so later changes are deliberate and traceable rather than made quietly by a programmer at a guest's request.

FAQ

Can guests override the vacant-room setback?

Guests only control the room while it is sold and occupied. Setpoint limits, such as 20–26°C, stop extreme settings, and the room returns to its mode logic when the key card is removed.

Why use both a key card switch and an occupancy sensor?

The key card shows intent to be in the room, but guests leave cards or dummy cards in holders. An occupancy sensor confirms real presence, so the room can move to "guest away" when nobody is there.

How does the room behave during a power failure?

After power returns, the controller should restore the last room mode from memory and not switch every light on. Test this at mock-up by switching off the room distribution board for a minute.

Contact Prestige Solutions to review your site drawings and current operating pattern. Call +65 8010 2337, message us on WhatsApp, or email sales@prestigesolutions.com.sg. You can also browse the full product range before the site walk.

Previous Article Hotel IPTV Fault Isolation: TV, Network and Headen Next Article Guestroom Phone Deployment and Labelling: Field No

Interested in Our Solutions?

Explore our full product range or speak with our technical team for a tailored consultation.