High bay sensors and smart lighting controls reduce unnecessary operating time by adjusting fixtures to occupancy, daylight, schedules, and project-defined overrides. They work well only when the detection method, lens pattern, mounting height, driver, dimming interface, zones, and sequence of operation are matched. A sensor is not a universal energy-saving accessory; it is one part of a tested control system.
This guide explains how to select and commission high bay light sensors for warehouses, factories, production areas, and other high-ceiling spaces. It focuses on control behavior and project decisions rather than on wiring details, emergency-lighting design, or a single “best” sensor technology.
Quick Answer: What Makes High Bay Sensors Work?
A reliable high bay lighting control system follows five steps: define the occupied and unoccupied conditions, select a sensor whose detection pattern suits the mounting height and obstructions, match it to the LED driver and dimming method, divide the space into useful zones, and document the sequence before commissioning. PIR can be effective where line of sight is clear; microwave can help in some obstructed layouts but may create cross-zone triggers. Daylight and emergency behavior must be tested separately.
There is no universal mounting height, timeout, wattage, or detection-distance recommendation. The correct settings depend on ceiling height, rack geometry, motion speed, partitions, vehicle traffic, skylights, required light levels, voltage, driver interface, emergency equipment, and local requirements.
A practical decision path is: map the space, identify occupancy patterns, compare detection options, define the sequence, verify component compatibility, calculate a realistic operating-hour scenario, then perform a representative walk test and record the final settings.
Occupancy and Vacancy Control
Occupancy control turns lights on or raises their output when activity is detected. Vacancy control normally requires a manual or scheduled start, then uses sensors to reduce or switch off lighting after the area becomes unoccupied. The choice affects user experience, false activations, and how the facility responds after a power interruption or control fault.
Start With Zones, Not Individual Sensors
A zone is a group of fixtures that responds to a common control rule. In an open warehouse, zones may follow aisles, loading areas, packing stations, or daylight gradients. In a factory, useful zones may follow production cells, inspection areas, storage aisles, and maintenance routes.
A zone that is too large can waste energy because one person keeps an entire floor at full output. A zone that is too small can create distracting light patches, excessive hardware, and difficult commissioning. The best boundary is usually the smallest practical area that shares a similar occupancy pattern, required light level, and emergency behavior.
Record these inputs before selecting a sensor:
- mounting height and fixture arrangement;
- rack height, aisle width, partitions, equipment, and moving obstructions;
- typical motion type, including walking, forklift travel, seated work, and slow inspection;
- expected occupied hours and periods of intermittent activity;
- daylight entry, skylight location, and areas that must remain continuously lit;
- manual override, scheduled operation, and failure-state requirements.
Detection, Delay, and Override Settings
A sensor needs more than an on/off rule. The sequence should define the occupied output, unoccupied output, time delay, fade rate, daylight response, manual override, and behavior after a control or communication failure. A short timeout may reduce operating hours but can cause nuisance dimming when workers move slowly or remain at a workstation. A long timeout improves continuity but reduces the potential saving.
Manual override should have a clear purpose and duration. For example, maintenance staff may need temporary full output, while a night-shift supervisor may need a local override without changing the permanent schedule. Every override should have a documented return condition so that fixtures do not remain at an unintended level indefinitely.
Sensor control also needs a failure state. If a sensor stops communicating, the system may need to hold a safe output, revert to a local control, or alert the facility team. The correct behavior depends on the application and emergency design; it should not be invented during installation.
PIR Versus Microwave Detection
PIR and microwave sensors detect motion through different mechanisms, so neither is automatically better for every high bay application. Selection should begin with the environment and the required detection boundary, not with a marketing label.
How the Two Technologies Differ
| Detection method | How it responds | Typical strength | Main risk in a high bay project | Best-fit starting condition |
| PIR | Detects changes in infrared energy across a field of view | Clear, predictable line-of-sight movement | May miss or respond slowly to small movements outside the lens pattern | Open areas with visible walking paths and limited obstructions |
| Microwave | Detects movement through changes in a radio-frequency field | Can respond to some movement where the visual path is partly obstructed | May detect motion beyond the intended zone or react to vibration and moving equipment | Layouts where the selected model’s range and cross-zone behavior are verified |
PIR performance depends strongly on lens pattern, mounting height, and the direction and size of movement. A person walking across detection segments may produce a different response from a person walking directly toward the sensor. Racking, machinery, and partitions can block the intended field of view.
Microwave performance depends on the specific sensor, its antenna pattern, installation position, and the materials and motion around it. Metal structures can reflect or shape the detection field. Fans, vibrating equipment, doors, vehicles, and movement in adjacent aisles can create false triggers. A nominal range from a generic product description is not enough to approve a design.
A Project Decision Matrix
Use the following matrix during design review. A selection should be rejected or held for testing when any critical evidence is missing.
| Decision question | PIR evidence to collect | Microwave evidence to collect |
| Can the sensor see the intended movement? | Lens pattern at the proposed height and fixture position | Antenna pattern and verified coverage at the proposed height |
| Are there obstructions? | Rack beams, equipment, partitions, and stored goods | Metal structures, doors, fans, vehicles, and reflective surfaces |
| Could adjacent areas trigger the zone? | Lens overlap and aisle sight lines | Cross-zone test under normal operating movement |
| Is slow or small motion important? | Detection test for the actual task and direction of travel | Detection test for the actual task, vibration, and background movement |
| What records are needed? | Model, lens, height, orientation, timeout, and walk-test result | Model, sensitivity/range setting, height, orientation, timeout, and false-trigger observations |
The decision record should state why the chosen technology fits the project and which assumptions still require a sample test. A product should not be ranked universally from one specification or one successful demonstration in a different building.
Daylight Harvesting in High Bay Spaces
Daylight harvesting reduces electric-light output when the measured daylight contribution is sufficient. It works best when the sensor location, controlled zone, setpoint, and dimming response reflect the actual daylight gradient.
A sensor placed near a skylight may measure much more light than the working plane deeper in the building. A sensor placed under a fixture may respond to the electric light it is controlling and create unstable feedback. The design should identify the reference area, shield the sensor from misleading direct light where appropriate, and calibrate the setpoint under representative sky and operating conditions.
Daylight and occupancy controls should be coordinated, not allowed to compete. For example, an empty aisle may be held at an unoccupied level even if daylight is available, while an occupied packing station may need a minimum working level despite a bright roof area. The sequence should define which rule has priority when occupancy, daylight, schedule, and manual override occur at the same time.
Daylight Commissioning Checks
Before acceptance, verify that:
- the sensor is installed in the intended reference zone;
- the controlled fixtures dim smoothly rather than stepping unpredictably;
- the occupied level remains adequate at the task area;
- the daylight setpoint is recorded with the time, sky condition, and electric-light state;
- skylight shadows, stored goods, seasonal sun angles, and cleaning conditions have been considered;
- the system returns to the defined state after the sensor is covered, disconnected, or unavailable.
Do not claim a fixed percentage of energy reduction from daylight harvesting without a measured baseline, operating schedule, setpoints, and field data.
Zoning and Grouping for Warehouses and Factories
Zoning determines whether the control system follows the real work pattern or merely divides a large room into arbitrary electrical groups. Open floors, rack aisles, production cells, and egress routes usually need different control behavior.
Match Zones to the Way the Space Operates
Open storage areas often need aisle-based control because workers and forklifts move along repeatable routes. A production cell may need a higher maintained level while adjacent storage can reduce output. Loading and inspection areas may require schedules or local overrides because activity is intermittent but safety-sensitive.
A useful zone plan records the fixture IDs, sensor IDs, physical boundary, normal output, unoccupied output, timeout, override rule, daylight relationship, and emergency interaction. This becomes the basis for commissioning and future troubleshooting.
Illustrative Operating-Hour Scenario
The following example is for planning logic only. It is not a promised saving or a universal warehouse schedule. Assume a facility has three control zones, each with 10 fixtures rated at 200 W. The baseline keeps all 30 fixtures at full output for 16 hours per day, 300 days per year. A proposed sequence keeps the occupied level at full output for 8 hours, reduces the unoccupied level to 30% for 4 hours, and turns the remaining 4 hours off.
| Item | Baseline | Proposed sequence |
| Installed fixtures | 30 × 200 W | 30 × 200 W |
| Full-output hours per day | 16 | 8 |
| Reduced-output hours per day | 0 | 4 at 30% |
| Off hours per day | 0 | 4 |
| Illustrative annual operating energy | 28,800 kWh | 16,560 kWh |
Calculation: baseline energy is 30 × 0.2 kW × 16 × 300 = 28,800 kWh. The proposed sequence is 30 × 0.2 kW × (8 + 4 × 0.30) × 300 = 16,560 kWh. The difference is 12,240 kWh in this simplified scenario.
The result changes if the fixtures do not dim linearly, if occupancy is longer than expected, if emergency circuits operate separately, or if the facility adds more frequent overrides. Before using the result for an investment decision, replace the assumptions with interval operating data, measured dimming behavior, electricity rates, maintenance requirements, and the actual driver configuration.
Sequence of Operation: Write the Rules Before Installation
A sequence of operation describes what the system should do in each relevant state. It converts a general request such as “use sensors to save energy” into testable behavior.
Example Sequence Template
| State | Trigger | Fixture response | Exit condition | Record for acceptance |
| Occupied | Valid motion or scheduled occupied period | Raise the assigned zone to the defined occupied level | No valid motion for the timeout period, subject to fade delay | Trigger point, response time, output level |
| Unoccupied | Timeout expires | Hold the defined reduced level or switch off | New valid motion, schedule change, or override | Timeout, fade behavior, zone boundary |
| Daylight available | Measured condition reaches the setpoint | Reduce electric output within the allowed occupied minimum | Daylight falls below the setpoint or occupancy changes | Setpoint, sensor location, dimming response |
| Manual override | Authorized local or scheduled command | Apply the documented temporary level | Timer, cancellation, or scheduled return | Override source, duration, return state |
| Control fault | Sensor, driver, gateway, or communication failure | Apply the approved fallback state and alert rule | Fault cleared and system revalidated | Failure simulation and recovery result |
| Emergency condition | Approved emergency signal or loss of normal supply | Follow the listed emergency sequence | Emergency system reset under authorized procedure | Emergency interaction test and records |
The exact levels and timeouts must come from the project brief, lighting design, local requirements, and component documentation. The table is a structure for agreement, not a universal setting.
Networked Control Considerations
A networked system can coordinate zones, schedules, sensor data, alarms, and performance records, but “smart” does not automatically mean compatible or secure. Confirm the complete control path: sensor, driver, dimming input, controller or gateway, software, power supply, communication method, and user permissions.
Ask the supplier or controls integrator to document:
- the supported protocol and whether it is native, gateway-based, or project-specific;
- device addressing, commissioning tools, firmware ownership, and backup procedures;
- who owns configuration data and how the facility can export it;
- what happens during network loss, gateway failure, sensor failure, or power restoration;
- user roles, password management, update responsibility, and remote-access boundaries;
- replacement strategy when a sensor, driver, gateway, or software component reaches end of life.
Do not describe Bluetooth, Zigbee, or another protocol as a standard FY feature unless the exact SKU and configuration confirm it. The same caution applies to app control, cloud dashboards, wireless grouping, and data logging.
Emergency Interaction
Normal occupancy and daylight controls must never block the approved emergency-lighting function. Emergency behavior is a system-level requirement involving the emergency driver, battery or supply, control input, fixture configuration, wiring, and local rules.
Review the exact emergency documentation for the selected components. Confirm whether the emergency fixture remains at a defined output, bypasses normal dimming, changes state after a power loss, and requires a dedicated control path. Test the transition from normal operation to emergency operation, the emergency duration or rated behavior, and the authorized reset procedure.
Do not transfer a stated emergency option from one FY series to another. The FY knowledge base confirms a 90-minute emergency and smart-sensor options for HBG as available options, while other series must be checked against their own current model documentation. A product-page option is not proof that every power, voltage, driver, or control configuration has the same emergency behavior.
FY LIGHTING Sensor and Custom Control Path
For a confirmed example, the HBG tri-proof high bay is listed with optional smart sensors and up to 90 minutes of emergency backup. Its current specification also lists 85/135/180/220/280 W options, 14,450–47,600 lm, 170 lm/W, IP65, 120° distribution, multiple input-voltage ranges, and a five-year warranty under the intended product environment. These facts apply to the listed HBG configuration and should be matched to the final SKU, driver, sensor, and emergency arrangement.
That example illustrates the correct buying path: first define the facility conditions and sequence, then ask FY LIGHTING or the project integrator to confirm the sensor lens, mounting height, driver interface, control behavior, and sample settings. Do not assume that a sensor option on HBG is standard across every FY high bay series, or that a listed control option confirms a particular network protocol.
FY LIGHTING can support project-specific zoning, layout review, DIALux/CAD simulation, samples, and engineering coordination. The useful project package should include the facility plan, mounting height, fixture schedule, occupancy pattern, daylight zones, input voltage, emergency conditions, required control behavior, and acceptance-test requirements. The final product and control configuration remain project-specific.
Commissioning and Acceptance
Commissioning is where a plausible design becomes a usable control system. Perform it under representative conditions, not only with an empty building and a single person standing beneath the sensor.
Pre-Work and Component Checks
Use qualified electrical and controls personnel, approved model documents, and the local safety procedure. Before energizing, verify the mounting structure, fixture orientation, sensor position, voltage, conductors, driver and dimming interface, cable entries, enclosure integrity, control addresses, and emergency components.
Do not invent wire colors, terminals, or hardware details from a generic diagram. Use the exact fixture, sensor, driver, and emergency documentation for the selected configuration.
Functional Test Matrix
| Test | Method | Acceptance evidence |
| Coverage walk test | Walk the intended paths at normal and slow speeds | Zone ID, trigger location, response time, missed areas |
| False-trigger observation | Observe adjacent aisles, doors, fans, vehicles, and vibration | Time-stamped observations and any sensitivity adjustment |
| Timeout test | Leave the zone and measure the transition to reduced or off output | Actual timeout, fade, and final output |
| Dimming test | Command each defined level and observe fixture response | Output state, smoothness, driver behavior, and fault result |
| Daylight test | Check the reference area under representative daylight conditions | Sensor position, setpoint, task-area result, and calibration record |
| Override test | Apply and release authorized manual or scheduled override | Source, duration, priority, and return state |
| Emergency test | Follow the approved emergency test procedure | Transition, emergency output, duration/rated behavior, reset |
| Documentation test | Compare physical layout with the control schedule | As-built drawing, device list, settings, and handover file |
Record the final sensor model, lens or range setting, mounting height, orientation, zone assignment, timeout, dimming levels, daylight setpoint, override rule, failure state, and emergency behavior. Retest after any change that affects coverage or control logic.
Common Failure Modes
The lights switch off while people are still working. The timeout may be too short, the lens may not cover the task, or the sensor may not detect slow movement. Test the actual activity before extending the timeout across the entire facility.
Adjacent aisles switch on together. The zone boundary may not match the detection field. Recheck sensor position, sensitivity, metal reflections, line of sight, and movement outside the intended area.
Daylight control hunts between levels. The sensor may be poorly located, the setpoint may not represent the task area, or occupancy and daylight rules may have conflicting priorities. Stabilize the sequence and recalibrate under representative conditions.
The control works in a demonstration but not on site. A sample room may not reproduce rack geometry, vibration, sky conditions, shift patterns, or emergency interfaces. Require a documented sample or pilot test when the environment is uncertain.
The specification says “sensor-ready,” but the installed system does not behave as expected. Sensor-ready may describe an option or interface, not a complete commissioned control network. Confirm the selected SKU, driver, sensor, configuration, and commissioning responsibility.
Conclusion and Project CTA
High bay light sensors work when detection, zones, drivers, dimming, daylight, emergency behavior, and commissioning are designed as one system. Start with the facility’s movement and lighting requirements, not with a universal sensor range or a generic energy-saving percentage. Then document the sequence, verify the exact interfaces, test representative conditions, and preserve the final settings for future maintenance.
Planning a warehouse or factory control project? Share the facility layout, mounting height, occupancy pattern, daylight zones, input voltage, emergency conditions, preferred sequence, and required acceptance tests with FY LIGHTING. The team can help narrow the suitable product family and project-specific sensor configuration before quotation.
FAQ
Do high bay lights need motion sensors?
No. Motion sensors are useful when occupancy varies by zone and the lighting system can respond safely and predictably. Areas with continuous work, strict minimum-light requirements, frequent overrides, or emergency constraints may need scheduled, manual, or hybrid control instead.
Are PIR or microwave sensors better for warehouses?
Neither is always better. PIR is often easier to bound where line of sight is clear. Microwave can suit some obstructed layouts but may detect movement beyond the intended zone or react to vibration and metal structures. Compare the exact sensor pattern, height, obstructions, and walk-test results.
What timeout should a high bay occupancy sensor use?
The timeout should reflect the slowest normal activity and the cost of nuisance shutoff. Start with the project’s work pattern, then test walking, forklift movement, inspection, and stationary tasks. Record the selected timeout and confirm the unoccupied output, fade behavior, and override rule.
Can daylight harvesting and occupancy control be used together?
Yes, but their priority must be defined. Occupancy can determine whether a zone is active, while daylight can trim output within the occupied range. The system should specify minimum occupied output, setpoints, overrides, and behavior when daylight or sensor data is unavailable.
Does the HBG high bay include a smart sensor as standard?
The current FY LIGHTING information lists a smart sensor as an option for HBG, not as a universal standard feature for every configuration. Confirm the final power, driver, sensor, control interface, emergency arrangement, and commissioning settings for the quoted SKU.
What information should be submitted for a sensor-control quotation?
Provide the facility plan, ceiling and mounting heights, rack or equipment layout, fixture locations, occupancy schedule, daylight openings, input voltage, emergency conditions, desired occupied and unoccupied levels, timeout preferences, network requirements, and acceptance-test criteria. A sample area or representative layout is useful when detection conditions are uncertain.
English