Dimming and occupancy control can reduce unnecessary lighting, but neither feature should be assumed from the words “low bay.” The result depends on the actual luminaire, driver, control interface, sensor, mounting position and programmed sequence. Define the required behavior first, then verify that the selected equipment can deliver it.
This guide helps facility engineers, controls contractors and operations teams turn a low bay lighting control idea into a testable plan. You will learn what to document, how to check compatibility, how to divide zones, and how to commission the system under realistic working conditions.
Define the Required Behavior
The first step is to describe what the lights should do in the space. Do not start by choosing a sensor or a dimming protocol. Start with operating hours, activities and the light levels people need for those activities.
Identify Where Control Is Useful
Walk through the facility by activity rather than by room name. A storage aisle, a packing bench and a circulation route may all be in one open building, but they do not have the same occupancy pattern or visual task.
Record the normal schedule for each area. Note regular shifts, occasional access, cleaning, maintenance, loading, breaks and after-hours work. Also identify locations where people may remain still for several minutes. A person reading a label, inspecting a part or working at a bench may not provide the same movement signal as someone walking through an aisle.
Control is most useful where lighting demand changes with use. A low bay area that is occupied continuously may gain little from aggressive occupancy-based reduction. A storage or circulation area with intermittent access may have more opportunity, provided the reduced level remains suitable for safe movement and the control response is reliable.
The practical output is an activity map. It should show where people work, how often they enter, what they need to see, and which areas may need a manual or scheduled override.
Describe the Intended States
Write the desired operating states in plain language before selecting components. A sequence-of-operation table can prevent a vague requirement such as “add sensors” from becoming an untestable installation.
| State | Trigger or condition | Intended light behavior | Information to confirm |
| Occupied | Representative movement or an approved schedule | Operate at the project-approved working level | Required light level, response time and maximum operating level |
| Unoccupied | No qualifying activity for the approved delay | Reduce or switch off only if the space remains suitable for the intended use | Reduction level, delay and restart behavior |
| Manual override | Authorized local or central command | Hold the approved level for the defined period or until released | Access, timeout and priority over automatic control |
| Fault or communication loss | A documented equipment or control fault | Follow the approved fallback state | Safe default, alarm path and responsibility for correction |
The table describes behavior, not technology. “Occupied” may be detected by a sensor, a schedule, a manual command or a combination. Keeping the behavior separate from the technology makes later changes easier to evaluate.
Do not set a low level only because it saves energy. The approved level should reflect the actual work, visibility needs, facility policy and any applicable project requirements. Where emergency lighting or life-safety functions are involved, the normal control sequence must not be treated as proof of compliance. That interaction requires the responsible electrical or life-safety specialist to verify the design and applicable requirements.
Verify Luminaire and Driver Compatibility
A control plan is only valid when the installed luminaire and driver support the intended commands. A fixture category, wattage or product photograph cannot establish dimming compatibility.
Identify the Actual Control Interface
Collect the exact luminaire model, power configuration, driver information, wiring diagram, installation instructions and control documentation. If the building contains mixed fixtures, record each relevant configuration instead of treating the whole room as one product.
Look for the actual interface and its electrical requirements. The documentation may identify a dimming input, a sensor connection, a relay function, a digital bus or another control method. It may also specify polarity, cable limits, compatible accessories, addressing, maximum connected devices and whether the control input is isolated from the supply circuit.
Do not infer that a 0–10 V interface, if present, provides independent control of multiple functions. Overall dimming is not the same as separate control of color temperature, spectrum or other channels. For a conventional low bay installation, the important question is simpler: what command does this exact driver accept, over what range, and with what response?
If the existing fixture documentation is missing, pause the design at compatibility review. A proposed sensor may be electrically suitable in general but still fail to control the installed driver. Photographing labels and tracing the actual wiring is more useful than selecting a device from the luminaire category alone.
Establish Supported Operating Limits
Record the documented operating limits before writing settings. These may include the minimum dimming level, startup behavior, response delay, turn-on level, control voltage range, power-on default and accessory requirements.
The minimum command is not automatically the minimum useful light level. A driver may accept a low command while the resulting light output, stability or visual performance is unsuitable for the space. Conversely, a project may approve a reduced level only for a particular activity or time period.
Build a compatibility record with three columns: documented capability, project requirement and verification method. Mark each item as confirmed, project-specific or still requiring supplier or specialist confirmation. This prevents a control schedule from quietly turning an assumption into a specification.
A project-specific FY LIGHTING configuration can be reviewed against the required control behavior when the team has the exact model, driver, input voltage, wiring arrangement and intended sensor or control method. FY LIGHTING’s current low-bay product information includes the HBH tri-proof low bay family, with 20/30/53/70/100 W versions, IP65 protection, chainable configurations and optional emergency versions. Those published facts do not by themselves confirm a dimming interface or occupancy-control compatibility. The control function must remain tied to the exact configuration and project documentation.
Assess Occupancy Detection in the Installed Position
A sensor detects activity from its installed position, not from the product category. The right question is whether the proposed sensor can detect representative activity in the actual space without creating unacceptable missed or unwanted responses.
Use the Documented Mounting and Coverage Information
Start with the sensor’s documentation for mounting height, orientation, detection pattern, coverage conditions and limitations. Do not invent a coverage radius from a generic product description, and do not assume that a sensor mounted on a luminaire sees the same area as a sensor mounted on a wall or structure.
Compare the documented coverage with a plan of the low bay area. Show the luminaire or sensor positions, aisles, workstations, doorways, partitions, equipment and likely paths of travel. Identify positions where a person may be working without crossing the strongest part of the detection pattern.
Coverage is not a single number that guarantees a result. The sensor model, lens, mounting height, angle, temperature, obstructions and type of movement can all affect the outcome. The proposed installation should therefore be tested in representative positions rather than approved from a catalog value alone.
Account for Obstructions and Movement
Racks, partitions, conveyors, machines, stored goods and raised vehicles can block or alter detection. A clear test in an empty room may not represent the operating facility. Include normal equipment and representative storage conditions in the review.
Movement also matters. A person walking through an aisle may be easy to detect, while someone sorting small parts at a bench may move only within a limited area. Cleaning staff, forklift operators, inspectors and maintenance workers may follow different paths and schedules.
List the responses that must not occur. These may include lights turning off while a worker is reading a label, lights activating because of activity in an adjacent zone, or a vehicle being missed behind a stored load. The commissioning test should reproduce those conditions and record the result.
If the sensor cannot reliably detect the required activity from the proposed position, changing the timeout may not solve the problem. Repositioning, adding a sensor, changing the zone boundary or using another control method may be necessary.
Divide the Space Into Appropriate Control Zones
Control zones should follow real use and operating decisions, not simply the shape of the ceiling or the nearest electrical circuit.
Match Zones to Actual Use
A practical zone may contain one aisle, a group of similar workstations, a packing area or a circulation route. The correct boundary depends on who uses the area, when they use it and how the light should respond.
Keep areas with different requirements separate when a shared response would create a problem. For example, a packing bench may need a stable working level while an adjacent storage route has intermittent occupancy. One automatic state for both areas could leave the bench too dim or keep the route fully lit when it is unused.
Zone planning should also consider maintenance and future changes. A zone that is convenient to wire but difficult to troubleshoot may increase operating effort. Label each zone on the plan and connect it to the relevant luminaires, sensors, manual controls and sequence-of-operation row.
Avoid Conflicting Control Behavior
Neighboring zones should not fight each other. Define what happens when a person moves from one zone to another, when a manual override is active, and when a central schedule conflicts with a local occupancy command.
Decide whether adjacent zones should overlap briefly, whether a shared task requires both zones to respond, and which command has priority. Document the behavior for boundary areas such as doorways, cross-aisles and loading points.
Do not turn this article into a complete warehouse layout guide. The control question is narrower: does the zone arrangement make the required behavior predictable, understandable and testable? A zone plan and a sequence table are more useful than a long list of devices without operating logic.
Develop the Sequence of Operation
The sequence of operation converts the control concept into settings that can be checked during commissioning. It should state levels, delays, overrides and fallback behavior without exceeding the documented equipment limits.
Record Levels, Delays and Overrides
For each zone, record the occupied level, unoccupied level, delay, activation condition, manual override duration and return-to-automatic behavior. Mark whether each value is a project-approved setting, a manufacturer limit or a value still to be confirmed.
Avoid presenting one universal delay or dimming level as the correct answer. A storage aisle, a quality-inspection area and a maintenance route can need different behavior. The setting should be chosen against the activity map and then verified under normal operation.
A useful sequence table should allow a technician to answer five questions: what starts the response, what level is commanded, how quickly does it occur, what keeps it active, and what happens when the command ends? If the table cannot answer these questions, the system is not ready for commissioning.
Address Failure and Emergency Interaction
Define the response to sensor failure, control communication loss, driver failure, power restoration and manual override timeout. The fallback state should be approved by the responsible project team, not invented during installation.
Emergency lighting requires special attention. The presence of a battery option, sensor or control input does not by itself prove emergency compliance. Confirm the emergency function, duration, circuit arrangement, test method and applicable requirements for the exact equipment and market with qualified specialists.
Keep normal energy-control settings separate from emergency and life-safety verification. This makes the boundary clear and prevents a control schedule from being used as a substitute for a formal electrical review.
Commission the System Under Representative Conditions
Commissioning is the point where the planned behavior is compared with the installed system. A sensor that responds in an empty room has not yet demonstrated that it works during normal operations.
Test Coverage and Response
Before testing, confirm the installed model, wiring, sensor position, zone labels, programmed settings and any required control software. Use a test record that includes the date, zone, condition, expected response, actual response, adjustment and retest result.
Test each zone with representative movement and working positions. Include entry, travel, stopping, reading, sorting, inspection, cleaning and maintenance activities where relevant. Test transitions between neighboring zones and the effect of manual overrides.
Observe both detection and lighting response. Record whether the lights activate, reach the intended level, remain active for the approved period and return to the intended state. If a response depends on a documented driver range or control signal, verify that the installed values match the equipment information.
Test Unwanted or Missing Responses
A complete test looks for failures as well as successful activation. Stand still at representative work positions. Move behind typical obstructions. Enter from different directions. Test adjacent zones separately and together.
Record nuisance activation, delayed activation, premature reduction, missed movement, visible flicker, unstable output and incorrect zone response. Do not hide an adjustment inside a final pass statement. The record should show what changed and whether the retest resolved the issue.
A simple commissioning record can use this format:
| Test condition | Expected result | Actual result | Action and retest |
| Person enters from the main doorway | Entry zone responds within the approved response time | Record observation | Adjust only within documented limits; retest |
| Worker remains at a bench | Working light remains at the approved level | Record observation | Review coverage, position or sequence |
| Activity crosses a zone boundary | Neighboring zones follow the documented priority | Record observation | Correct zone logic or labels; retest |
| Manual override ends | System returns to automatic control as documented | Record observation | Verify timeout and return state |
The table is a record structure, not a claim that any project has passed these tests. Final acceptance should use the project’s approved criteria and responsible personnel.
Evaluate Operation Over Time
A control system can work at handover and become unsuitable after the facility changes. Review it as part of normal operations and maintenance.
Review Changes in Use
Recheck the sequence when racks move, partitions are added, equipment changes, workstations relocate or schedules expand. A new obstruction can change both sensor coverage and the usefulness of the original zone boundary.
Keep the zone plan, settings, wiring information and commissioning record together. When a fixture or sensor is replaced, compare the replacement’s exact documentation with the original control requirements. Do not assume a visually similar product has the same driver or interface.
A periodic review should ask whether people are still working in the same locations, whether lights are activating unnecessarily, whether tasks are being performed at reduced levels, and whether operators are using manual overrides as a workaround. Repeated overrides often indicate a planning or coverage problem rather than a need to remove all automatic control.
Assess Energy Effects With Evidence
Energy savings should be calculated from actual or justified operating states. Record fixture quantity, input power, operating hours, occupied and reduced-level periods, manual overrides and any changes in schedule. If measured energy data are available, compare equivalent operating periods and note changes in production or occupancy.
Do not promise a fixed saving percentage from the presence of sensors. A lightly occupied area may have more reduction opportunity than a continuously occupied work area, while frequent overrides may reduce the effect. The full economic method belongs in a separate lighting retrofit or ROI analysis; this control guide should provide the operating evidence needed for that analysis.
Conclusion: Make the Control Plan Testable
Low bay lighting dimming and occupancy controls should be planned from required behavior, not from a generic fixture category. Document where control is useful, define occupied and unoccupied states, verify the exact driver and interface, map sensor coverage, divide zones around real activities, and write a sequence that technicians can test.
Before approval, collect the exact equipment documents, sensor coverage information, zone plan, sequence-of-operation table and commissioning record. If any of these are missing, the project may not yet have enough evidence to claim that the installed control behavior is suitable.
Planning a low bay lighting project? Share the facility layout, working activities, installed or proposed luminaire model, driver information, mounting position, control method, emergency requirements and operating schedule with FY LIGHTING for a project-specific configuration review. Compatibility and final settings should be confirmed against the exact project equipment and applicable requirements.
FAQ
Can Every Low Bay Light Be Dimmed?
No. Dimming depends on the exact driver, control input, wiring and configuration. Confirm the model-specific documentation and supported operating limits before selecting a controller or programming a minimum level.
Can an Existing Fixture Accept an Occupancy Sensor?
Sometimes, but the fixture category alone cannot answer the question. Check the installed driver, available control interface, sensor power requirements, wiring arrangement and fallback behavior. If documentation is missing, verify the actual equipment before approving the change.
Does a Sensor’s Coverage Change With Its Mounting Position?
Yes. Mounting height, orientation, lens pattern, obstructions and the type of movement can change what the sensor detects. Use the documented coverage for the proposed position and test representative working activity after installation.
Why Should Control Zones Follow Working Activities?
Because different activities may need different light behavior. A packing bench may need stable working light while a nearby storage aisle is used intermittently. Separate zones can prevent one area’s occupancy pattern from creating an unsuitable response in another.
How Should Settings Be Checked After the Layout Changes?
Compare the new layout with the zone plan and sensor coverage information. Recheck movement paths, obstructions, work positions, delays, reduced levels and neighboring-zone behavior. Record adjustments and repeat the relevant commissioning tests.
English