The Problem Starts at the Thermostat

A Sabbath mode thermostat is a control that runs heating or cooling from a schedule fixed in advance, instead of reacting in real time to the person in the room. That distinction is the whole product. A conventional thermostat is a closed loop: the sensor measures, the controller decides, the compressor or furnace runs. Most of the time that is good engineering. On Shabbat it creates a difficulty, because a person walking into a room raises its temperature, closes a window, or turns on an oven — and thereby indirectly commands the equipment.

The engineering answer is not to disable the sensor. It is to remove the sensor from the causal chain. In Sabbath mode the controller switches to a schedule set before Shabbat and makes decisions only at fixed, pre-determined moments. The same principle governs the whole product family described in Sabbath mode on appliances.

Four Operating Modes Worth Offering

  • Continuous fixed cycle. The compressor or blower runs on a rigid duty cycle with no reference to temperature. Simplest to implement, least efficient, and genuinely useful during an extreme heat wave or cold snap.
  • Time-stepped profile. A profile committed before Shabbat: high capacity in the afternoon, low overnight. In practice this is what most users select, and it is the mode worth optimizing first.
  • Cyclic operation with delayed sampling. The controller reads temperature only at widely spaced fixed instants, so there is no immediate causal link between a person's presence and equipment starting. This structure leans on the reasoning in grama mechanisms and indirect-action engineering and always requires rabbinic review of the specific implementation.
  • Off. A completely legitimate mode, provided the transition into it happens on its own at a time set in advance.

Everything Else That Has to Go Quiet

A modern HVAC system is saturated with feedback that responds to the user: a confirmation beep on every remote press, a temperature readout on the indoor unit, status LEDs, a louver motor that aims the airflow, and a "follow me" mode that tracks where the remote is sitting. In Sabbath mode all of it is suppressed.

The most stubborn detail is the infrared or radio receiver. It keeps accepting commands even when the system is supposed to be locked, so the firmware must ignore them deliberately and completely — not merely "usually." That is an architectural requirement, not a polish item, and it is the single thing most often caught during halachic review. Displays deserve the same discipline: freeze or blank them rather than letting a temperature number tick.

Climate Control Is More Than the Compressor

A motorized shade or blind that closes at a fixed hour saves more energy than most equipment upgrades and reduces the cooling load outright. In a Shabbat product the shade runs from the same time controller and specifically without a sun sensor that reacts to live conditions. The controller architecture is the one described in Shabbat timers and time controllers.

The Institutional Case Is a Different Product

Hotels, senior living communities, yeshivas, and schools change the picture completely: dozens of zones, a central building management system, and staff who are not necessarily observant. Three capabilities matter there that no residential product needs.

  • Group scheduling that moves every zone into Sabbath mode together, on time, without a technician walking the building.
  • Panel lockout in guest rooms so an occupant cannot change a setting mid-Shabbat.
  • A separate staff override path for genuine emergencies, logged and physically distinct from the guest interface.

Coordinating that many nodes is a networking problem before it is a thermal one. Mesh protocols suit the job well — the trade-offs are laid out in Zigbee vs Z-Wave for a smart home product — and interoperability with mainstream US smart-home ecosystems is worth designing for, as covered in Matter protocol firmware development.

Yom Tov Is Not Shabbat

On festivals some activities are permitted that are not permitted on Shabbat, and that changes the product definition. You may need an intermediate mode where certain actions are allowed and others are not, plus support for two- and three-day sequences when a festival runs adjacent to Shabbat. Continuous-run duration also becomes a reliability question: equipment that cycles for seventy-two hours without a service touch needs different thermal and relay margins than a residential unit that gets a weekly reset.

Where the Opportunity Sits

Major HVAC manufacturers largely do not build for this market, which leaves room for focused products: an external controller that overlays an existing system, a protocol bridge that translates one manufacturer's serial interface, or an institutional panel that manages a whole building. All three demand real communication-protocol work, real controller selection, and — most of all — real familiarity with the community that uses the product. Field observation in actual homes and institutions is worth more than any specification document.

Whole-home versions of this thinking are covered in Shabbat-compatible home automation, and the building-scale version in synagogue automation.

Building a Sabbath Mode Control Product

Projects House develops controls for the observant market from requirements through electronics, firmware, enclosure, and prototypes, with halachic review folded into the schedule rather than bolted on at the end. Tell us what system you want to control through our contact form and we will map the feasible path.