The problem: Property managers choosing between runtime-based control and occupancy sensor systems have no objective, empirical comparison to work from — making it easy to overspend on a technically complex solution that delivers worse results in practice.
What this article covers: This paper compares runtime limits and occupancy sensors across five dimensions — accuracy, consistency of savings, guest experience, deployment complexity, and total cost of ownership — using empirical data from rental and hospitality environments to show why the advantage of runtime control is structural, not marginal.
The punchline: Over a three-year horizon, a 5-unit portfolio using occupancy sensors typically spends €1,200–2,500 more in hardware, maintenance, and replacement costs than the same portfolio using runtime control — while delivering less reliable energy savings and more frequent guest complaints.
Two approaches dominate the market for reducing AC energy waste in short-term rental and hospitality environments: occupancy detection systems and runtime-based control. This paper compares the two approaches across five dimensions: accuracy and reliability, consistency of energy savings, guest experience impact, deployment and operational complexity, and cost of ownership.
Runtime-based control outperforms occupancy detection across all five dimensions in the rental and hospitality context. Occupancy detection systems solve a harder problem with less reliable inputs; runtime control operates on the one variable with a direct, measurable relationship to energy consumption, which is why the advantage is structural rather than marginal.
Detecting occupancy before deciding whether to cool a room is logical but misplaced in rental environments. The goal is to prevent energy waste. Runtime control achieves that directly; occupancy detection attempts it indirectly, and introduces significant failure modes in doing so.
Occupancy-based systems use one or more sensing mechanisms to infer whether a room contains a person, then use that inference to control the AC. Common sensor types include passive infrared (PIR) motion detectors, door and window contact sensors, CO2 level monitors, and camera-based presence detection. More sophisticated systems combine multiple sensors and apply machine learning to reduce false positives.
The control logic is: if occupancy is detected, allow cooling; if not detected, reduce or stop cooling. The system reacts to the presence or absence of a person as the primary trigger for energy decisions.
Runtime-based systems set a maximum operating period for each AC cycle. The unit runs for a defined duration, then pauses automatically. If the occupant wants more cooling, they activate the unit again with the remote. The system does not require any information about who is in the room or whether anyone is present.
The control logic is: limit total operating time per cycle. Energy consumption, which scales directly with runtime, is capped regardless of occupant behaviour.
Rental environments are particularly demanding for occupancy detection. Guest behaviour is unpredictable and varies significantly across individual stays. Common failure modes for occupancy sensors in these conditions include:
Runtime control has no equivalent failure modes. Elapsed time is measured with near-perfect accuracy by any timer circuit. The system cannot mistake a sleeping guest for an empty room. It cannot be confused by an open window. It does not drift or require calibration.
The energy savings from occupancy detection systems are real on average but highly variable across individual stays and individual rooms. A guest who moves frequently and uses the full room will trigger frequent occupancy confirmations, reducing the system's ability to curtail runtime. A sensor positioned poorly will miss occupancy in parts of the room, causing premature shutoffs that guests override.
Runtime-based savings are structural and consistent. A 45-minute runtime limit applied to a unit that previously ran for 60 minutes per hour delivers approximately 25% runtime reduction on every cycle, regardless of guest behaviour, room configuration, or sensor placement. The saving is guaranteed by the mechanism itself rather than dependent on accurate sensing.
Guest satisfaction is the primary commercial constraint on any AC control system in a rental or hotel environment. A system that guests notice in a negative way creates complaints, bad reviews, and potential refund claims that far outweigh any energy savings it delivers.
Occupancy detection systems create two categories of guest-visible failure. The first is false shutoffs during active occupancy — the unit stops cooling while the guest is present, creating immediate discomfort and no intuitive explanation. The second is delayed recovery — after a false shutoff, the room must recool to the desired temperature, which takes time and creates a noticeable period of discomfort.
Runtime-based control is not perceptible to guests under normal occupancy patterns. A unit that runs for 45 minutes and then pauses in a room that has already reached a comfortable temperature will not be noticed. Guests who are actively in the room and want continuous cooling will re-activate the unit, which is a minor action comparable to adjusting the thermostat. Guests who leave the room — the source of most energy waste — simply stop re-activating the unit, which is the intended outcome.
| Factor | Occupancy sensors | Runtime control |
|---|---|---|
| Installation | Physical mounting, wiring or batteries, positioning | No physical installation required |
| Network requirements | WiFi or Zigbee/Z-Wave hub typically required | No network connection required |
| Calibration | Initial setup plus ongoing seasonal adjustment | One-time configuration, no ongoing adjustment |
| Maintenance | Battery replacement, sensor cleaning, firmware updates | No maintenance required |
| Failure mode | Guest-visible: cooling stops during active occupancy | Non-visible: unit pauses only when idle |
| Data and privacy | Occupancy data collected and stored | No data collected |
| Setup time per unit | 30 to 90 minutes per room | Under 2 minutes per unit |
Occupancy detection systems carry higher upfront costs than runtime control devices, compounded by ongoing maintenance costs that accumulate across a portfolio over time. A single sensor unit for one room typically costs more than a runtime control device, before accounting for installation labour, network infrastructure, and maintenance visits.
For a property manager operating 20 units across multiple properties, the total cost of ownership difference over a three-year period, including hardware, installation, maintenance, and the staff time to manage sensor alerts and overrides, favours runtime control by a wide margin. Runtime control eliminates most of these cost categories after the initial purchase.
The energy savings delivered by runtime control are also more predictable, allowing ROI to be calculated with confidence before purchase. Occupancy sensor savings depend on detection accuracy and guest behaviour patterns that vary property by property and season by season.
Voltvert in one sentence: Voltvert is a plug-and-play AC control device for holiday rental properties and hotels that reduces electricity costs by enforcing temperature limits and automated runtime shutoff — no WiFi, no app, and no changes to existing AC equipment required.
Runtime control in under two minutes per unit. No installation, no WiFi, no app.
Order now — €69