Windows discussions and local services.
Discussion options
Wired Contacts or Wireless Sensors for HVAC Window Rules?
I’m weighing wired magnetic contacts against wireless window sensors for an HVAC rule: if a window stays open, pause heating or cooling, then resume only after all monitored windows are closed.
The practical choice seems to depend on the installation:
- For a few accessible windows, wired contacts may be worth the cable. They don’t depend on batteries or wireless connectivity, and the HVAC rule can be based on a more predictable signal.
- For finished walls, upper-floor windows, or several openings spread around the house, wireless sensors are much easier to install and can usually feed a hub or alarm system that the automation platform already understands.
- For hard-to-reach windows, I’d also want to distinguish a simple open/closed sensor from an automatic opener. An opener adds another failure point and shouldn’t be assumed to provide reliable position feedback unless the control system explicitly supports it.
The part I’m not clear about is fail-safe behavior. If a wireless sensor loses power or drops off the hub, should the automation treat that as “window open,” disable the HVAC rule, or simply ignore the missing device? Treating every communication fault as an open window could waste energy, but treating it as closed could defeat the reason for the automation.
Before choosing, I’d check:
1. How many windows need monitoring, and whether they’re casement, sliding, double-hung, or otherwise difficult to wire.
2. Whether the thermostat or HVAC controller accepts an external contact, or whether the hub is only sending an automation command.
3. Whether the system can require the window to remain open for a delay, such as several minutes, to avoid shutting down HVAC because someone briefly opened a window.
4. What happens if the hub, sensor, or network is unavailable.
5. Whether the rule can resume heating or cooling only when every required sensor reports closed, rather than when just one window closes.
For a whole-home HVAC rule, I’m leaning toward wired contacts where wiring is practical and wireless sensors only where installation would be disruptive. Is there a sensible hybrid approach, such as wired contacts on the main accessible windows and wireless sensors for the awkward openings, without creating inconsistent fail-safe behavior?
Join the conversation
Share your experience or ask a follow-up question.
4 replies
The fail-safe question seems easier to manage if “window closed” requires more than the last open/closed value. Could the rule also require every sensor to have reported a healthy status within a defined interval?
For example:
- Any sensor currently reporting open keeps HVAC paused.
- All sensors reporting closed, with recent check-ins, allows HVAC to resume.
- A sensor that goes stale triggers a separate alert or fallback mode, rather than being silently treated as open or closed.
That would avoid wasting energy indefinitely because of one missed wireless update, while still preventing the system from assuming everything is fine when a sensor has lost power or connectivity. The interval probably needs to account for the sensor’s normal reporting behavior, since some devices only transmit when their state changes.
The “recent check-in” condition should also apply after a hub or controller restart. Otherwise, it may restore the last cached closed states and resume HVAC before the sensors have actually checked in.
A practical sequence could be:
- On startup, put the HVAC rule into a paused or unknown state.
- Wait until every monitored sensor reports a fresh, valid open/closed state.
- Resume only if all of those fresh states are closed.
- If a sensor never checks in, keep the HVAC paused and raise a separate fault alert.
I’d qualify this for systems where pausing HVAC for an extended outage is a concern. A maximum hold time or manual override might be useful, but it should be clearly indicated rather than silently treating missing sensors as closed.
If a maximum hold time or manual override is added, should the override expire automatically rather than leaving the HVAC rule bypassed indefinitely? I’d also want it to require an explicit acknowledgment of the sensor fault before resuming, especially after a controller restart or a sensor that never checks in.
A bounded override could allow heating or cooling during a prolonged wireless outage, but it should show which windows are unverified, record when the override began, and return to the paused state after a set period. Would you make that timeout short enough to limit risk, or configurable by season and HVAC type?
An override should not quietly return to “paused” when its timer expires. If HVAC is going to stop because sensor status is still unknown, that needs a prominent alert rather than an unnoticed mode change.
A safer compromise is an expiring override that requires explicit reauthorization to continue. The system could:
- show the unverified windows and the override start time;
- log who or what reauthorized it;
- require confirmation again when the timeout expires;
- pause the HVAC rule at expiration if nobody confirms, while making that state obvious.
The timeout could be configurable by season and equipment. A short period may make sense for cooling in mild weather, while a longer, clearly bounded period could be appropriate when loss of heat risks frozen pipes. The important part is that neither bypassing the sensor fault nor pausing afterward happens silently.