A System Nobody Is Allowed to Turn Off

Security is the one category where the observant customer cannot simply do without the product for a day. A house or a synagogue that disarms every Friday evening and stays open until Saturday night has advertised a weekly window to anyone paying attention. So the system stays armed, and the engineering question becomes how a person moves through a protected building for 25 hours without operating anything electrical.

This is a harder problem than a Shabbat mode on an appliance, because an alarm panel is specifically built to respond to human presence. Nearly every sensor in it exists to detect a person doing something. The solutions are real but they are architectural, not a menu option bolted on at the end.

Motion Detectors: The Component That Causes the Trouble

A passive infrared detector sees a person walk through a hallway, switches its output, lights its walk-test indicator, and sends an event to the panel. Every one of those is a change caused directly and inevitably by the user, which is exactly the pattern the halacha treats as prohibited even when nothing was intended.

Four approaches are in production use, in rough order of preference:

  • Perimeter-only mode. The panel bypasses all interior motion zones on a schedule and relies on door and window contacts, glass-break sensors, and exterior detection. Nobody inside triggers anything, and the building is still protected against entry. This is the cleanest answer and the one most installers should reach for first.
  • Zone layout that keeps detectors out of Shabbat traffic. Plan coverage at design time around the rooms and hallways that stay in use, rather than blanket-covering the interior and bypassing half of it later.
  • Suppression of every downstream result. Where a detector must stay live, disable its LED, mute the panel chime, suppress the keypad display change, and suppress the app notification. What matters to a reviewer is whether a user action produces a perceptible result, so a detector whose every output is invisible is treated differently from one that beeps.
  • Indirect-action circuits. Panels intended for this market can run a periodic scan in which the sensor state is sampled on a fixed interval rather than reported the instant it changes, so no action of the user directly closes anything. That family of techniques is covered in grama mechanisms for Shabbat-compliant products.

Arming and Disarming Without a Keypad

Entering a code on a keypad is out. So is a fob, a phone app, and a smart lock. The answer is that arming happens before Shabbat starts and disarming happens after it ends, on a schedule the panel runs itself.

That places a real requirement on the product: the schedule has to follow sunset, not a fixed clock time, and it has to follow the sunset at the installed location on that week's date. A panel that arms at 6:00 PM every Friday is useless in June and dangerous in December. The panel needs an on-board halachic time engine or a scheduler fed by one, plus a documented behavior after a power outage that leaves it in the safe state rather than disarmed. The same scheduling backbone is described in Shabbat timers and time controllers.

Entry delays need the same treatment. A delay that expects a code within 30 seconds is a trap, so in scheduled mode an authorized door should be bypassed rather than start a countdown.

What Happens When the Alarm Is Real

Here the halacha is not restrictive at all. A genuine threat to life permits any action, and no engineer should design around the assumption that an occupant will hesitate. What the product must avoid is a design that requires a person to act for the system to behave correctly.

Concretely: the siren should time out and reset on its own after the interval local ordinance allows, rather than sounding until somebody silences it. Central station notification must be fully automatic on both paths. Any emergency unlock or egress release must be fail-safe hardware, not an app action. And the post-alarm state should be recoverable without a technician visit, because nobody is calling one until Saturday night.

Communications, Supervision, and the Central Station

Dual-path reporting over cellular and IP with a supervision heartbeat is standard practice and matters more here than usual, since a communications failure on Friday afternoon will not be noticed by an occupant who cannot look at the panel. Set the supervision interval so the monitoring center, not the homeowner, catches the fault, and make sure a comms trouble condition does not itself produce a beeping keypad in an occupied house for 25 hours.

Battery backup deserves the same thought. Size standby for a full Shabbat plus margin, because a Friday evening outage cannot be answered by plugging in a generator. The broader standards landscape for residential protection products, including the false-alarm-reduction practices municipalities now fine for, is covered in home safety product development.

Cameras Inside the System

Cameras are usually easier than motion sensors, because a camera that records continuously is doing something the user did not cause. The problems are the features layered on top: motion-triggered recording, doorbell chimes, push notifications, visible infrared illuminators that switch on when someone approaches, and status LEDs that change color.

A Shabbat mode for a camera product therefore means continuous recording with event triggering disabled, notifications and chimes suppressed, illuminators either always on or always off rather than switched by presence, and indicator LEDs frozen. The same reasoning governs the institutional systems discussed in remote kosher supervision technology, where cameras run continuously and humans review later.

Advice for a Developer Entering This Market

Treat Shabbat mode as a scheduling and suppression layer over an unmodified security core, never as a reduction in protection. Write down, sensor by sensor, what a user action causes and what result becomes perceptible, because that table is what a certifying authority will ask for and it is the fastest way to find the two or three features that actually need redesign. Then decide early whether you are selling to households or to institutions, since hotels, schools, and care facilities have staff on site and a different rulebook, as laid out in Shabbat technology for hotels and institutions. Plan several months for review and at least one firmware revision, following the process in halachic certification for products.

Reviewing Your Panel or Sensor Line

Projects House works with security manufacturers and integrators on Shabbat-compatible configurations: mapping user actions to electrical results, designing the scheduling and suppression layer, and preparing the technical package a certifying body reviews. Send your panel architecture and sensor list through the contact form.