If a floodlight stays off when you walk toward it, start with the response the system is supposed to provide. A motion detector can be operating while daylight permission prevents the lamp from turning on. An approach can also fall outside the useful detection pattern. Identify the sensor, operating mode and observed conditions before treating the symptom as a failed component.
What should make this floodlight turn on?
Motion, daylight and a command path
A motion-controlled light combines several decisions. The detector responds to activity, a daylight condition may permit or inhibit output, and a timer or operating mode determines how the light behaves afterward.
Identify which device makes those decisions. A camera recording movement does not automatically mean that its lighting output has received an enabled command. A solar or battery product can also have its own operating logic. Keep those systems separate from a conventional PIR-controlled floodlight.
Identify the system before choosing a control
Read the actual model's normal controls and indicators. A small photograph of a generic sensor cannot identify its reset sequence, load requirements or mode behavior.
The observations below concern normal, accessible operation. Damaged enclosures, water exposure, uncertain supply or internal faults require an appropriate service assessment. Do not bypass a sensor, open a powered fitting or probe wiring to force a response.

Separate the observed symptom from its possible causes
No response, continued light and intermittent behavior
Describe what happens before choosing a cause. “No response during a daytime approach” is a more useful account than “sensor broken.” It retains the time and condition that may explain the output.
Likewise, a light remaining on after someone leaves can involve a hold-time setting, continuing detected activity or another mode. Replacing a detector before distinguishing those possibilities can leave the original behavior unchanged.
One light and one control zone
Note which lights share the behavior. One affected fitting and a whole controlled group create different questions. Keep the observed group with the sensor identity rather than assuming every nearby light belongs to the same command path.
| Observed behavior | Normal condition to examine | Useful observation | When service is needed |
|---|---|---|---|
| No light during a daytime approach | Daylight permission and mode | Time, surroundings and active setting | Expected supported operation remains unexplained |
| Light stays on after departure | Hold time, activity or continuous mode | Whether the zone is actually vacant | Behavior persists outside the documented mode |
| Response differs by approach | Detection pattern and obstructions | Direction and route used | Physical assessment or changed placement is needed |
| Entire group changes together | Shared command or supply boundary | Which fittings are affected together | Electrical or system questions remain |
The detection pattern follows the sensor, not the illuminated patch
Movement across the PIR pattern
RAB's STL360 manual explains that its infrared sensor responds to temperature changes associated with movement within its protection pattern. It also describes movement across the pattern as more readily detected than movement directly toward the sensor.
Map the sensor field from its own position. The lamp optic defines a separate illuminated area.
RAB's manual also explains that detection becomes more dependent on larger movement with distance in its stated arrangement. Relate an observation to the actual approach and model pattern instead of interpreting a distant response as a fixed circular boundary. The light source and the detector can each cover a different part of the same entrance.
Obstructions and the actual approach path
Review the approach from the sensor's position. A parked vehicle or another solid obstruction can interrupt its view of a route that remains visibly illuminated from elsewhere.
Compare the desired approach with the applicable model drawing. Manufacturer range and mounting conditions belong to that model. There is no universal detection radius that follows from the floodlight's wattage or the size of the lit area.
If placement needs changing, treat that as a physical installation decision for the appropriate person. An observation about the route helps define that task; it does not establish a safe mounting position or a generic acceptance test.

Daylight permission can keep a motion-controlled light off
Motion detection and the photocell condition
In a night-only operating mode, movement during bright conditions may not call for light. A daytime approach therefore needs to be interpreted with the daylight setting and mode, rather than used alone as proof that the PIR is unresponsive.
The STL360 manual distinguishes night-only and 24-hour operation. STEINEL's XLED ONE S product information also lists twilight and time settings as separate functions. Their particular controls and conditions remain attached to their own products.
Nearby light changes what the sensor sees
The daylight input concerns light reaching the sensing area. A shaded position or a nearby light source can make that input differ from your general impression of the yard. RAB's manual discusses other lighting and reflected light in its explanations of sensor behavior.
Keep the observed surroundings with the symptom. A light that behaves differently at dusk, in full daylight and near another active fitting supplies useful information about the permission state. It still requires interpretation in the actual system.
For cycling or broader no-light problems, the floodlight service guide covers related supply, timing and photocell questions separately.
Time delay, sensitivity and mode change different behavior
Time after the zone is vacated
Read what starts the hold-time interval. The STL360 manual describes the time the lights remain on after its protection zone is vacated. Continued movement and a chosen operating mode can therefore matter when someone reports that the fitting has stayed on “too long.”
A timer value cannot be assessed without knowing whether the relevant event has ended. Keep the actual observation with the model's explanation.
For example, vehicles repeatedly crossing a detection zone can keep activity present. The interval after the zone is vacated has not necessarily begun just because one person has left. Describe continuing activity in the account before treating the duration as an unexplained timer failure.
Responsiveness, evening timer and manual mode
Sensitivity concerns the detector's response, while an evening timer or manual mode can keep light on for a different reason. These functions should not be mistaken for a brightness adjustment on the luminaire.
| Control or mode | Behavior it affects | What it does not establish | Record to retain |
|---|---|---|---|
| Hold time | Output following the documented vacancy condition | Whether a detected event has ended | Model's timing definition |
| Daylight permission | Conditions under which output is enabled | Whether the detector has failed | Actual mode and surroundings |
| Sensitivity | Detection response and relevant range | A different lamp lumen output | Applicable pattern and control description |
| Evening or manual mode | A supported continuous-light behavior | The same behavior on every sensor | Named product's mode instructions |

Read a reset or override instruction in its own context
A mode command is model-specific
Some products use an ordinary switch action as a mode command. Others provide different normal controls. A sequence described as a reset for one device can have another meaning on a different sensor.
Use the instruction for the identified product and the intended state. A generic instruction to cycle power rapidly can obscure which mode was selected. Repeating an unexplained sequence also makes the original symptom harder to describe.
Access inside the housing changes the task
Keep normal external controls separate from internal service. Finding an unfamiliar button or compartment is not a reason to open a powered enclosure. If the supported user route is unclear, stop at identification and use the appropriate service channel.
External mode selection follows its documented normal operation. Electrical assessment or a changed installation belongs to a competent person. Neither a successful reset nor a brief flash establishes that every underlying condition has been checked.
Work through one daytime non-response account
The known model mode
Use the STL360 manual's description of Auto operation with night-only daylight permission. Now assume an observer approaches in bright daylight, after the startup period, and the controlled light stays off. This is a hypothetical observation for reading the record, not a reported customer fault or a new field test.
The observed time and approach
The account gives a mode, daylight condition and output state. It does not establish whether the detector failed. Under the documented night-only arrangement, the lack of daytime output is consistent with the permission state.
If the actual brief requires motion response during daytime as well, the night-only state is the mismatch to address through the product's supported operating modes. Changing the lamp or assuming a driver fault would address a different question.
The supported next conclusion
The immediate conclusion is specific: review the intended daylight operating state before ordering replacement hardware. If the required documented state is already in use and the behavior remains unexplained, preserve that observation for service.
An approach-path question can then be considered independently. Its geometry should not be confused with daylight permission. Keeping those two questions separate helps the next person assess the actual symptom without being handed a premature diagnosis.

Decide what a service visit needs to resolve
Useful observations without opening the fitting
Retain the model, the affected lights, the normal setting or mode and the conditions under which the behavior occurred. Photographs from an accessible position can show the approach and surrounding obstructions.
These observations give the service task a starting point. They are not a substitute for electrical measurements or an instruction for the observer to make them.
The LED load and sensor interface need their own records
For a replacement combination, keep the actual load category with the control rating. The read STL360 manual names incandescent and fluorescent load entries. Those entries do not establish a new LED or FL20 pairing.
| Question remaining | Observation already available | Appropriate next route | Unproven conclusion to avoid |
|---|---|---|---|
| Is the intended mode active? | Time, surroundings and normal settings | Applicable operating instructions | Sensor failure from one observation |
| Is the approach within useful detection? | Route and visible obstructions | Model-pattern and physical assessment | Lamp beam equals detection field |
| Does the proposed load/control combination have support? | Actual product identities | Matching interface and load records | A generic amp rating approves every LED load |
| Is an internal or supply problem present? | Affected group and visible condition | Competent service assessment | A specific failed part without assessment |
Return to the intended lighting behavior
A service account should state the expected response, active mode and actual approach. Those details help distinguish normal operating behavior from an unresolved service question.
After the appropriate service or operating review, relate the outcome to the intended task again. A light simply being on is a different observation from the required motion-controlled response. Keep any unresolved control or electrical question explicit.
For a broader change in how lighting groups receive commands, the floodlight system-planning article explains those relationships. It complements the normal-state review here without turning it into a generic wiring or reset procedure.
