{"id":19976,"date":"2026-01-09T02:45:19","date_gmt":"2026-01-09T02:45:19","guid":{"rendered":"https:\/\/staging.rayzeek.com\/uncategorized\/stair-motion-3way-feel"},"modified":"2026-01-09T02:46:09","modified_gmt":"2026-01-09T02:46:09","slug":"stair-motion-3way-feel","status":"publish","type":"post","link":"https:\/\/staging.rayzeek.com\/uk\/%d0%b1%d0%bb%d0%be%d0%b3\/stair-motion-3way-feel","title":{"rendered":"Multi\u2011Location Stair Motion Control With Rayzeek PIR Switches: How to Make It Feel Like a Normal 3\u2011Way"},"content":{"rendered":"

Stairs are where \u201cmostly works\u201d becomes a problem. People hit them half-awake at 6:30 a.m., carrying laundry, holding a baby, balancing coffee, stepping into a landing turn where the light changes and their body changes direction. If the light hesitates or times out there, it isn\u2019t just an \u201cannoying quirk.\u201d It\u2019s the exact moment people get angry\u2014or worse, stop trusting the stairs entirely.<\/p>

A lot of ugly stair stories start the same way: someone has a normal 3\u2011way (two locations controlling one light) and tries to \u201cjust replace one switch with a motion sensor.\u201d In real houses\u2014split-level half-landings, narrow townhome stairs, finished basements\u2014that often buys a new kind of surprise. One end feels dead, the light goes out mid\u2011flight, or the system only works if you walk exactly how the sensor wants you to.<\/p>

Make it feel like a dumb 3\u2011way.<\/p>

That\u2019s the standard this guide uses. Not \u201cmaximum automation.\u201d Not \u201cbest range on the box.\u201d Normal behavior first; PIR and settings are just implementation details.<\/p>

Define \u201cNormal 3\u2011Way Feel\u201d Before Touching Settings<\/h2>

In a stairwell, \u201cnormal\u201d is a behavioral contract, not a wiring diagram. The contract is simple enough that a tired homeowner can understand it in a minute, and strict enough to prevent the most common failures. A good multi-location PIR setup should feel like this:<\/p>

From either end, a person can get light without thinking about it. From either end, a person can shut it off if they want it off. If someone pauses on the landing\u2014because a kid is ahead of them, or they\u2019re turning a laundry basket, or unlocking a door\u2014the light doesn\u2019t punish them with darkness. And if something in the system fails, it should bias toward \u201clight stays on,\u201d not \u201cstairs go black.\u201d<\/p>

Those aren\u2019t preferences; they\u2019re risk priorities. Mid\u2011stair darkness is the worst outcome. Flicker or \u201cdisco\u201d behavior is next, because it teaches people the stairs are unpredictable. A light staying on a little long is usually forgiven, especially in winter when dark mornings in places like the Pacific Northwest are exactly when stair complaints spike.<\/p>

There\u2019s a common adjacent problem that shows up early: people don’t hate motion sensing. They hate light spill. Bedroom doors opening to a stairwell, nursery light bleeding under a door, a basement stair that lights up a whole lower level. That\u2019s real, and it tempts people into the shortest possible timeout. But timeout is not the first knob to touch. If the system can\u2019t see a person reliably at the top step and the landing turn, shaving seconds off the delay turns a visibility problem into a safety problem. Spill gets handled, but only after the system\u2019s \u201cnormal feel\u201d is established.<\/p>

Under the hood, the clean way to think about any multi-location motion setup is: detection \u2192 decision \u2192 light<\/strong>. \u201cDetection\u201d is who saw motion and when. \u201cDecision\u201d is who decided the circuit should be on or off and on what timer. \u201cLight\u201d is the actual load response. Most stair failures are a mismatch between those layers\u2014usually multiple devices making decisions without agreeing on the same timer or the same definition of \u201cstill occupied.\u201d<\/p>

The Practical Spine: Placement + One \u201cDecider\u201d<\/h2>

Mara Kline\u2014an electrician who gets called when stairs become a callback\u2014has a blunt bias here: sensor placement beats sensor spec sheets. In a Ballard townhouse, the problem wasn\u2019t a cheap PIR \u201cbeing cheap.\u201d The problem was what the PIR could see: a narrow stairwell, a mirrored bifold closet door near the base, a forced-air register, and a hanging coat that moved just enough. Glossy surfaces made the sensor\u2019s world noisy. Rotate the sensor a few degrees to change what it \u201cwatches,\u201d and the so-called haunted triggers go away without swapping brands.<\/p>

That story matters because stairs are almost never clean, straight test corridors. Picture a split-level in Kent, WA: a half-landing turn that breaks line-of-sight, a 3\u2011gang box at the top of the stairs because remodels stack controls where they fit, and a morning walk test in January where the light looks fine until it cuts out exactly at the turn. The datasheet coverage diagram doesn\u2019t show that moment. The person turning their body on the landing does.<\/p>

So placement starts with geometry and approach vectors, not marketing range. A straight run with clear sightlines is forgiving; an L\u2011turn, U\u2011turn, or half\u2011landing is not. People approach stairs from angles: from a hallway, a kitchen, a basement door, a bedroom doorway. They don\u2019t enter like a technician walking squarely into the sensor\u2019s centerline. They hug rails. They pivot. They carry objects that block a PIR\u2019s view of the body\u2019s motion.<\/p>

For a stairwell that must feel normal, first detection has to happen before the first step on both ends, and it has to keep happening through the \u201cquiet\u201d moments: the landing pause, the turn, the moment someone slows down for the last step. On a half\u2011landing, a sensor aimed from the very top often creates a blind moment at the turn. The person\u2019s movement becomes lateral relative to the sensor, and the sensor\u2019s view gets cut by the wall or the landing geometry. The usual fix is not buying a magical \u201c360\u00b0\u201d unit. It\u2019s moving the sensing point to where the human is actually visible: often a landing wall, sometimes lower than people expect, sometimes offset so the sensor sees the approach path instead of staring down the flight.<\/p>

Looking For Motion-Activated Energy-Saving Solutions?<\/h3>

Contact us for complete PIR motion sensors, motion-activated energy-saving products, motion sensor switches, and Occupancy\/Vacancy commercial solutions.<\/p>

Send an Email<\/p><\/a><\/div><\/div>

Contact Form<\/p><\/a><\/div><\/div>

Chat Online<\/p><\/a><\/div><\/div><\/div><\/div>

Now, the adjacent demand signal that wastes a lot of money: \u201cthe sensor is bad; it turns on by itself at night.\u201d That\u2019s the phrase that sends people shopping. In practice, false triggers are often environmental. Mirrors, HVAC vents, a door that swings into the sensor\u2019s view, glossy paint, glass railings\u2014even a heat register and a hanging coat can look like motion to a PIR depending on aim and the field of view. The right response is a quick environment audit\u2014what changed at 2 a.m., what moves, what reflects\u2014and then a placement\/aim adjustment. Brand-swapping without changing what the sensor sees is how a \u201cbad sensor\u201d becomes three bad sensors.<\/p>

Once placement is sane, the next spine piece is control roles. In multi-location stair control, two devices making independent decisions is where the \u201cdisco stairwell\u201d is born. In Tacoma, a property manager\u2019s complaint log and tenant emails had the same words over and over: \u201cflicker,\u201d \u201cunpredictable,\u201d \u201cit goes off when I stop.\u201d The on\u2011site reality was not mysterious. Multiple devices were retriggering each other, and timers were short enough that a pause on the landing created a dark gap. The maintenance tech kept \u201ctuning sensitivity\u201d like it was one device misbehaving. It wasn\u2019t. It was multiple decision-makers disagreeing about when \u201coccupied\u201d ends.<\/p>

That\u2019s why Mara pushes a one\u2011decider principle<\/strong>. One device (or one control point) should be the decision authority for on\/off timing. Other devices, if used, must behave in a subordinate, predictable way. The exact implementation depends on the specific Rayzeek model and how it supports multi-location wiring or companion controls, but the behavioral requirement is consistent: the household should never have to learn that \u201cthe top sensor wins unless the bottom one already timed out\u201d or any other invisible rule. If the only way the system makes sense is a hidden rule, it will generate angry texts and return visits.<\/p>

A simple timeline makes the problem obvious. At time zero, someone enters from the bottom, triggers PIR A, and the light turns on. The person reaches the landing, slows, pivots, and their motion is smaller. PIR A\u2019s timer is counting down. PIR B (near the top) may or may not see the person during that pivot depending on aim and geometry. If PIR B is also allowed to decide off timing independently, it can shut the circuit off while PIR A thinks it\u2019s still in charge, or it can retrigger in bursts if it\u2019s seeing only fragments of motion. The human experience is flicker: light on, light off, light on again as they step, or darkness when they\u2019re \u201cstill\u201d but not absent.<\/p>

Rayzeek PIR switches can be part of a clean solution here, but only if the setup remains explainable and testable. Because Rayzeek models and revisions can differ in how they label multi-location behavior, mode options, and time delay names, the safest approach is to treat the manual as authoritative for terminals and mode labels, while the house is authoritative for the actual outcome. Nobody cares if the installer picked the right menu item. They care if they can force the light on from both ends, if it stays on through a landing pause, and if it turns off without surprising anyone.<\/p>

Practically, stair archetypes guide placement decisions:<\/p>