Most buildings still run HVAC based on assumptions.
They assume a room is occupied because the schedule says so. They assume a meeting room needs the same ventilation all day. They assume a guest room is empty because nobody moved for a while. In real life, buildings are messier than that.
That is why occupancy-based HVAC control matters.
At its core, occupancy-based HVAC control means using real signals about whether a space is in use, how many people are there, or how usage is changing, and then adjusting HVAC operation accordingly. That can affect ventilation, fan speed, setpoints, schedules, and standby modes. It is part of the broader shift toward occupant-centric and adaptive building controls, and DOE says advanced building controls can reduce HVAC energy use significantly, while DOE-cited research estimates around 18% whole-building energy savings on average from occupancy-based ventilation controls.
It is more than motion detection
One of the biggest mistakes is to treat occupancy-based control as just “motion sensor = HVAC on.”
That is too simple for most real buildings.
Modern occupancy-based control can use different layers of information: presence sensors, people counters, area occupancy sensors, desk or seat occupancy, room-booking data, and HVAC feedback like CO2 or temperature. In practice, different spaces need different signals. A small meeting room may only need presence detection. A lobby or conference area may need actual people counting. A flexible office may benefit from area-level occupancy and booking context together. Commercial controls ecosystems now expose occupancy and people-count data through BACnet and APIs, and some field sensors also support MQTT, HTTP, RS485, DI, and DO, which makes them easier to bring into building controls.
The main occupancy technologies
In practice, occupancy intelligence usually comes from a mix of sensing approaches.
Presence and motion sensors are the simplest layer. They are useful for enclosed rooms where the main question is just whether the room is being used.
People counters add another level. These are especially useful at entrances, public areas, meeting rooms, shared spaces, and zones where actual headcount matters more than simple presence.
Area and desk-level occupancy sensors are useful in offices, coworking spaces, and flexible environments where usage can vary a lot across a floor.
Software context, like room booking or scheduled use, is also valuable, but it works best when it is verified by real sensor data instead of being trusted blindly.
Why LoRaWAN people counters are especially important
Why LoRaWAN people counters are especially importantThis is where the topic gets very practical for retrofit buildings.
LoRaWAN is designed for low-power end devices and is widely used in smart-building environments because it is relatively easy to deploy across existing buildings without major rewiring. That makes LoRaWAN people counters especially valuable when a building already has HVAC equipment or a BMS, but lacks real occupancy data at field level.
That is why LoRaWAN people counters matter so much in real projects. They make it much easier to add occupancy intelligence to entrances, lobbies, public areas, office zones, and event spaces without turning the project into a heavy infrastructure job. Current devices in this category increasingly support anonymous counting, regional analysis, line crossing, and zone-level tracking, which makes them useful not only for HVAC but also for cleaning, staffing, and space operations.
How occupancy-based HVAC control works
A good implementation usually follows a simple logic chain.
First, the building gathers occupancy data from one or more sources. That may be a motion sensor, a people counter, a desk occupancy sensor, or schedule data.
Second, that data is interpreted. Is the room occupied? How many people are present? Is this a short event or a sustained load?
Third, the control layer translates that into HVAC action. That could mean shifting a room from standby to occupied mode, increasing outdoor air, resetting setpoints, trimming airflow in low-use zones, or pre-conditioning a space before expected use.
Finally, the building checks whether the result is working through feedback like CO2, temperature, humidity, or comfort trends. This is important because occupancy tells you demand is changing, but it does not by itself confirm that conditions are good. ASHRAE’s ventilation framework supports dynamic reset strategies like demand control ventilation, and in some occupancy-standby scenarios allows airflow reduction and restoration based on occupancy detection.
How this connects to BMS and building controls
This part is important.
Occupancy sensors and people counters do not create value just by collecting data. They create value when their signals actually influence control logic.
A practical architecture is often:
sensor or people counter → LoRaWAN gateway / network layer → platform or rules engine → BMS / BACnet / HVAC action
That means the people-count or occupancy signal can trigger ventilation changes, switch a zone between standby and occupied modes, influence temperature setpoints, or support smarter scheduling. Modern controls ecosystems already expose occupancy and people-count points through BACnet and APIs, which makes this integration much more realistic than it used to be.
A short but important hotel example
Hotels are one of the clearest examples of why occupancy-based control should be more than a motion sensor.
In guest rooms, a very practical setup often combines a thermostat, a PIR occupancy sensor, and a door contact, sometimes with a balcony or window contact too. This is common in hotel energy-management approaches because motion alone can misread a sleeping guest as an empty room. Hotel EMS vendors describe exactly this broader pattern: PIR sensing supplemented by door and window signals to improve room-state detection and avoid waste.
A simple but smart guest-room logic looks like this:
- door opens and motion is detected soon after, so the room is treated as occupied
- no motion for a while does not immediately mean vacancy
- if there is no exit signal, the room can remain in an occupied or sleep-protected mode
- if the door opens and no return activity is detected, the room can move into setback
- if a balcony or window opens, cooling or heating can be limited to avoid obvious waste
That is the key lesson: in hospitality, the best control logic is often not the most complicated. It is the one that interprets simple signals correctly. This is also why occupancy-based control works differently across a hotel. Guest rooms often benefit from door-plus-presence logic, while meeting rooms, breakfast areas, lobbies, and event spaces benefit much more from real people counting and dynamic ventilation response. DOE research on hotel controls has also found meaningful HVAC savings potential in guest rooms from occupancy-based strategies.
What good practice looks like now
The best projects usually follow a few simple rules.
Do not use one occupancy signal for every type of space.
Do not trust schedules without sensor verification.
Do not use occupancy alone where ventilation quality matters.
Do combine occupancy with CO2 and thermal feedback in denser spaces.
Do use people counting where headcount actually changes the HVAC need.
And in retrofit buildings, do look seriously at LoRaWAN-based deployment because it lowers the barrier to adding this control layer across large portfolios.
Final thought
Occupancy-based HVAC control is really about one thing:
making HVAC respond to real use, not guessed use.
Sometimes that means a simple motion sensor in a meeting room. Sometimes it means a LoRaWAN people counter feeding a BMS rule for ventilation reset. And sometimes, especially in hotels, it means something as simple and as smart as combining a door sensor with occupancy sensing so the system does not mistake a sleeping guest for an empty room.
That is what makes the topic useful.
Not the buzzword.
The logic.
