HospitalityNovember 14, 20267 min read

Guest-Room Thermostat: Fan-Coil or BMS Gateway?

How a hotel guest room's control system should connect to fan-coil or VRF HVAC, which points to expose, and what to prove in the mockup room.

A hotel guest-room thermostat connects to the mechanical system in one of two ways: a direct fan-coil interface that drives the valve and fan speed itself, or a gateway/BACnet point exposed to a VRF system or BMS that the control system reads and writes to. The choice depends on what the mechanical contractor installed, not on what the control platform prefers. Either way, the points that must be exposed are the same — setpoint, fan speed, mode, occupancy state, window contact, and fault/alarm — and who supplies each point has to be settled between the MEP contractor and the controls integrator before the mockup room is built, not after.

Fan-coil direct control or a BMS gateway — which one applies?

If the property runs two-pipe or four-pipe fan-coil units at each guest room, a dedicated fan-coil thermostat can drive the unit directly. Crestron's fan-coil thermostats, for example, provide variable heating, cooling, and fan-speed control through 0-10V signals to the valve and fan, along with a heating relay for traditional elements — all addressed over a Cresnet wired bus back to the room's control processor (CHV-TSTAT-FCU-PIR-10-W-T). That thermostat also carries a built-in PIR sensor so the unit can toggle automatically between occupied and unoccupied setpoints as motion is detected or stops being detected — a feature worth asking about directly if occupancy-based setback is part of the design.

If the property instead runs VRF or a central plant under a building management system, the room-side device usually needs to speak the BMS's protocol rather than drive the fan coil directly. Crestron's DIN-rail fan-coil controller supports this case: it includes an RS-485 port for Modbus or BACnet alongside its Cresnet port, and it can run standalone or integrated with a home automation system or a BMS (DIN-TSTAT-FCU). That dual-protocol support is what lets one room-side device serve either as a Cresnet-networked thermostat for a Crestron-only room or as a BACnet/Modbus point feeder when the mechanical system is centrally managed. A property evaluating a VRF bridge product should also ask whether it exposes BACnet over IP for control and feedback, since gateway products built for that purpose exist in the market and that's the kind of bridge a mechanical engineer should be asked to confirm.

Older in-room thermostats built around fixed relay outputs for fan speed and heat/cool staging rather than the newer 0-10V modulating and BACnet/Modbus-capable designs should be treated as an earlier generation; a new guest-room build should be speced against current fan-coil or gateway hardware rather than carried forward on relay-only units.

Who supplies and programs the mechanical interface?

This is the question that causes the most friction mid-project, and it has to be answered at design, not at commissioning. CEDIA's guidance on BMS/HVAC integration is explicit that mismatched protocols and lack of collaboration between the engineers managing a building's mechanical systems and the AV/controls integrators are two of the most common technical failures on these projects, and that the fix is coordination at the design phase, with both the BMS supplier and the controls team working to an open protocol set such as BACnet, Modbus, or KNX rather than a proprietary one-off bridge (BMS Control For HVAC Systems). In practice this means the mechanical contractor's scope should state, in writing, which points are exposed at the thermostat or gateway and in what format, and the controls integrator's scope should state what it reads from and writes to those points — setpoint, fan speed, mode, occupancy, window contact, and any fault or alarm signal the fan-coil or VRF unit can report.

Window contacts and fault signals deserve particular attention because they are often left out of early mechanical submittals. A window contact that cuts conditioning when a door or window is open, and a fault signal that surfaces a frozen coil or failed compressor to the room system rather than leaving a guest with no heat or cooling until housekeeping notices, are both points that should be named in the interface schedule rather than assumed.

A hotel's guest-room automation naturally sits beside this mechanical interface — the same keypad or touch screen that sets a scene and triggers do-not-disturb is usually the device that shows the current setpoint and mode, so the thermostat scope and the guest-room automation scope need to be designed by the same team. Cave Group builds custom guest-room automation on Crestron, or on packaged Lutron myRoom where that fits better, and designs the thermostat and mechanical interface as part of that same hospitality scope rather than leaving it to be reconciled on site.

What does sold/unsold and occupied/vacant status change?

In a hotel, the thermostat's setpoint logic has to answer to two different states that a residential thermostat never sees: whether the room is sold at all, and whether a sold room is currently occupied. A vacant, unsold room should sit at a wide energy-saving setback. Once the room is sold — typically signaled from the PMS at check-in — the setpoint should move to a pre-arrival comfort range ahead of guest arrival. Within a sold room, the PIR-based occupied/unoccupied toggle built into a fan-coil thermostat like the CHV-TSTAT-FCU-PIR-10 handles the finer-grained swing between an occupied setpoint when motion is detected and an unoccupied setpoint when the room sits empty, without dropping back to the full vacant-room setback that applies to an unsold room. Getting this three-tier logic (unsold / sold-but-vacant / sold-and-occupied) right depends on the PMS interface reaching the room system reliably, which is a separate but related integration that should be tested alongside the HVAC points.

What has to be proven in the mockup room before it repeats floor by floor?

The mockup room is where the mechanical and controls interface gets proven once, in detail, before the same design is repeated across every floor — and the HVAC side of that proof needs its own checklist distinct from the lighting and shading sign-off. At minimum, the mockup should demonstrate that the control system can read and write every agreed point (setpoint, fan speed, mode, occupancy, window contact, fault) reliably; that the PIR or door-contact based occupied/unoccupied transition behaves as designed without hunting or lag; that a simulated fault (a blocked coil, a stuck valve, or a comms loss to the gateway) surfaces as a visible alarm rather than a silent failure; and that the sold/unsold setback actually fires from a real PMS check-in and check-out event rather than a manual override. CEDIA's guidance on accurate, user-friendly feedback loops applies directly here: if a guest or staff member can't tell whether an HVAC command succeeded, there's no way to confirm from the room interface that the mechanical and controls systems are actually compatible, and that ambiguity is exactly what the mockup is meant to catch before it is built 200 times. Only once this HVAC-side testing passes should the mechanical scope, points list, and fault-handling logic be locked and handed to the mechanical and electrical trades for floor-by-floor rollout.

Frequently asked questions

Does a hotel guest-room thermostat connect directly to the fan coil, or through a gateway?

It depends on the mechanical system. A dedicated fan-coil thermostat can drive the valve and fan speed directly over 0-10V signals when the property runs individual fan-coil units at each room; when the property runs VRF or a central plant under a BMS, the room-side device typically needs a BACnet or Modbus interface to that system instead.

Which HVAC points need to be exposed at the guest-room thermostat?

Setpoint, fan speed, mode (heat/cool), occupancy state, window contact, and fault or alarm signaling all need to be named and exposed, regardless of whether the connection is a direct fan-coil interface or a BMS gateway.

Who decides which mechanical points the controls system can read and write?

The mechanical contractor and the controls integrator should agree on the points list and the protocol in writing at the design stage, not at commissioning; industry guidance from CEDIA identifies mismatched protocols and late-stage collaboration as the most common source of HVAC/BMS integration failures.

How does a sold-but-vacant room's setpoint differ from an occupied room's?

An unsold room typically sits at a wide energy-saving setback; a sold room moves to a comfort range at check-in and then swings between occupied and unoccupied setpoints within that range based on PIR or door-contact sensing, without returning to the full vacant-room setback.

What should the mockup room prove on the HVAC side before floor rollout?

The mockup should confirm that every agreed point reads and writes correctly, that occupied/unoccupied transitions behave without lag, that a simulated mechanical fault surfaces as a visible alarm, and that the sold/unsold setback actually fires from a real PMS event before the design is repeated across every floor.

Sources

Work With Cave Group

Planning a hotel technology upgrade?

Cave Group designs, installs, and supports these systems for luxury homes, hotels, and yachts across New York, New Jersey, and Europe — one partner from design through 24/7 support.

Start a Project

or explore our work