Silvair Daylight Harvesting vs Photocell Control

An evidence-led guide to calibrated illuminance control, Day/Night state selection, commissioning, and fault diagnosis.

Use Silvair daylight harvesting when the objective is to maintain a calibrated illuminance target by continuously modulating electric light. Use the Silvair Photocell scenario when ambient light should move a zone between configured Day and Night states. Daylight harvesting needs workplane-reference calibration; Photocell uses threshold-based Day/Night state logic. In this article, “Photocell” means the Silvair Photocell control scenario, not a standalone line-voltage photocell switch.

Daylight Harvesting vs Photocell at a Glance

What Is Silvair Daylight Harvesting?

Silvair daylight harvesting is a closed-loop, continuously variable lighting strategy. It uses available daylight and calibrated sensor information to adjust electric light toward a required illuminance at a chosen reference surface. It does not mean that every point in a room is guaranteed to be at one exact lux value: uniformity remains dependent on luminaire layout, distribution, zoning, reflectances, and sensor field of view.

The three-layer control architecture

The architecture should be separated into three technical layers. First, an ambient light sensor reports Present Ambient Light Level. Second, a Basic Lightness Controller receives the sensor data and controls luminaire lightness. Third, the configured Silvair control profile determines whether the zone uses a daylight-harvesting loop or Photocell Day/Night logic. Bluetooth® Networked Lighting Control (NLC) defines the Ambient Light Sensor and Basic Lightness Controller profile interaction, including sensor calibration concepts such as Sensor Gain. Silvair scenario settings are still determined by compatible firmware and commissioning configuration.

Important scope: Bluetooth NLC Ambient Light Sensor Profile functionality was published in 2023, and Silvair explicitly introduced Bluetooth NLC compliance with Firmware 2.30 NLC. Do not assume that every earlier Silvair Bluetooth Mesh device implements an NLC profile. Confirm device qualification, firmware, controller support, sensor profile, and commissioning-tool support before specifying a Bluetooth NLC daylight sensor for either strategy. A Bluetooth NLC daylight sensor should be selected by verified capability, not by its product name alone.

A daylight zone normally needs at least one compatible Bluetooth Mesh or Bluetooth NLC ambient-light sensor, one or more compatible lighting controllers, an Occupancy sensing with daylight harvesting or Vacancy sensing with daylight harvesting control profile, and a light meter for site calibration. Bluetooth daylight harvesting describes the wireless transport and profile context; it does not remove the optical and commissioning requirements at the site. For that reason, Bluetooth daylight harvesting must still be tested against the actual reference surface and daylight condition.

What Is Silvair Photocell Control?

Silvair Photocell is a separate ambient-light-based control scenario. It performs threshold-based Day/Night state selection: ambient light below the configured Night threshold activates Night settings, while ambient light above the configured Day threshold activates Day settings. The selected states can be off, partially dimmed, or brighter; the strategy is not limited to simple ON/OFF switching.

For illustration only, not a Silvair default, code requirement, or universal design value, a project could set Night below 35 lx at 30% and Day above 70 lx at 0%. Actual thresholds and levels must be set from sensor location, ambient conditions, photometric design, local code, and project requirements. The practical question is not “how much electric light is needed to maintain a task target?” but “which configured ambient-condition state should govern this zone now?” That is the central daylight harvesting vs photocell distinction.

How Silvair Daylight Harvesting Calibration Works

Calibration connects a ceiling sensor reading to illuminance at the selected reference surface. In simplified form, the calibration relationship can be expressed as A = E_meter at reference surface / E_sensor. The Silvair App uses this relationship to convert the sensor value into an estimated illuminance at the reference surface. Bluetooth NLC expresses sensor calibration through Sensor Gain; do not treat that profile field and the site calibration coefficient as unrelated concepts. They both support a measurement that is meaningful to the control decision.

Calibration conditions and the ±8% control tolerance

Silvair SN-209 calls for the light meter to be placed on the reference surface directly below the selected sensor. Interior finishes, furniture, and major equipment should be substantially complete; windows and skylights should not be covered; daylight should be normal and reasonably stable; and adjacent-area luminaires should be off. The sensor must not be obstructed. The measured illuminance should reach at least 75% of the configured target and never be below 100 lx; the best condition is a measurement close to the target configured in the Zone control profile.

“Continuous” means continuously variable control, not a command for every one-lux fluctuation. SN-209 indicates that a zone may not change output when the estimated reference-surface illuminance differs from target by roughly ±8%. This deadband limits distracting small corrections. Recalibrate after sensor replacement or relocation, major layout or furniture changes, repainting or reflectance changes, added or removed luminaires, or material luminaire depreciation.

How Photocell Calibration Differs

Both strategies require commissioning and selection of the correct sensor. The difference is the calibration objective. For daylight harvesting, select the sensor, measure illuminance at the workplane reference surface with a light meter, enter that lux value, and calibrate. For Photocell, select the correct sensor and run Calibrate, but no workplane light-meter lux value is entered. The resulting statement for a specification table is: “Sensor calibration required; no workplane lux entry.”

This distinction matters because a Bluetooth NLC daylight sensor is not automatically usable for both scenarios just because it reports lux. The installed device, Silvair firmware, lighting controller, enabled control profile, and commissioning tools must all support the selected scenario. The Bluetooth NLC daylight sensor must also be commissioned into the intended zone relationship. Confirm this combination before design freeze or field commissioning.

How Photocell Day and Night Thresholds Work

Separate Day and Night thresholds create hysteresis. Below the Night threshold, the Night state is selected; above the Day threshold, the Day state is selected; between the thresholds, the current state can remain unchanged. This reduces unwanted oscillation from clouds, temporary shadows, reflected light, or vehicle headlights. The transition occurs only after the relevant threshold condition persists for the defined delay period. The duration should be verified against the commissioned profile; this article does not assign an unsupported fixed 60-second value.

Typical parameters include Day and Night default levels, occupied level, occupancy timeout, fade time, manual-override timeout, and power-up behavior. These shape how the selected state behaves, but the fundamental mechanism remains threshold-based Day/Night state selection. Photocell lighting control is a strong fit for exterior areas, parking zones, entrances, circulation routes, and dusk-to-dawn applications where a task-plane target is not the primary objective. Effective Photocell lighting control depends on a sensor view that represents the required ambient condition.

How Occupancy and Scheduling Work with Both Strategies

Occupancy determines whether or how a zone is being used; ambient-light logic determines its daylight response. With Silvair daylight harvesting, occupancy can activate the zone and the loop then modulates electric output toward the calibrated target. With Photocell, ambient light first selects Day or Night state, after which occupancy can raise, reduce, or time out light within that state. For illustration only, a Night state might maintain a standby level and rise on occupancy; its actual percentages are a project decision, not fixed Silvair values.

Do not assume every strategy can be layered with in-node scheduling. Silvair FAQ guidance states that the current Photocell scenario cannot directly use in-node scheduling. Where time-based behavior is needed, configure an appropriate Multiple Scenes/Scheduling profile instead. Verify the profile combination during project design, especially where occupancy, scene control, and manual overrides are also required.

What Is a Reversed Photocell and When Is It Used?

A reversed Photocell is not reverse sensor wiring. It is a strategy in which the configured Day-state level is intentionally higher than the Night-state level. For illustration only, not a Silvair default, code requirement, or universal design value, Day above 70 lx could be 100% while Night below 35 lx could be 0%. The parameters should be set from the actual site conditions.

Entrance, exit, tunnel, parking-garage, and covered-to-outdoor transition zones are application-design examples rather than Silvair mandates. In bright exterior conditions, added transition-zone light can reduce the visual contrast between a darker interior and the exterior. At night, the additional daytime level may not be required. This is a deliberate form of Photocell lighting control, not a different sensor type. The ambient light sensor lighting control function remains the same; the configured Day and Night levels create the reversed response.

Where Should Ambient Light Sensors Be Positioned?

For daylight harvesting, the sensor should be vertically above the selected reference surface and should monitor reflected composite light from the surface covered by the controlled luminaires in that zone. It should not receive direct luminaire output or direct sun, and it should avoid strong reflective surfaces and obstructions. It should monitor only the surface covered by the controlled luminaires of its own zone. These principles make the measurement representative without implying that a sensor must look directly at lamps.

For Photocell, place the sensor where it reliably represents the ambient condition that should trigger Day/Night state selection. Avoid local direct light, headlamps, shadows, reflections, obstructions, and unrelated sources that would dominate the reading. The same ambient light sensor lighting control hardware may have different placement priorities in the two scenarios because the controlled objective differs. Good ambient light sensor lighting control design begins with the control objective rather than the sensor label.

Why Is Silvair Daylight Harvesting Not Working Correctly?

Start with the relationship among sensor, zone, reference surface, and control profile. Common causes are selecting the wrong sensor; using a sensor in a different Zone; a blocked sensor field of view; direct sun or direct luminaire light on the sensor; mounting above a high-reflectance surface; insufficient daylight during calibration; a calibration measurement below 75% of target or below 100 lx; changed layout or reflectance; or luminaire light loss. These conditions can make a correct controller act on an unrepresentative measurement. They are frequent root causes when ambient light sensor lighting control behavior appears inconsistent.

If output appears to oscillate or to respond too slowly, also review the control deadband, fade settings, zone size, sensor view, and the magnitude of the daylight change. A change that does not exceed the roughly ±8% tolerance may legitimately produce no immediate adjustment. When diagnosing Bluetooth daylight harvesting, also verify device firmware and supported profile behavior rather than attributing every problem to wireless connectivity. A Bluetooth daylight harvesting fault can be optical, calibration-related, profile-related, or device-related.

Should You Use Daylight Harvesting or Photocell Control?

Choose daylight harvesting when

• A calibrated illuminance target at a reference surface is needed.
• Daylight contribution changes across the operating day.
• Continuous dimming is preferred to Day/Night state selection.
• Workplane conditions and electric-light savings are priorities.
• The project can support representative sensor placement and light-meter calibration.

Typical fits include offices, classrooms, daylight-facing perimeter zones, skylit warehouses, and manufacturing spaces. Silvair daylight harvesting is the appropriate choice when the electric contribution must adapt continuously to available daylight, while accepting that a calibrated reference point is not a guarantee of identical lux everywhere in the zone.

Choose Photocell when

• The essential decision is whether ambient conditions are bright or dark.
• Dusk-to-dawn or Day/Night state behavior is required.
• Outdoor or transition-area lighting should respond to ambient conditions.
• Defined states are sufficient, including off, dimmed, or higher-output states.
• Occupancy should modify a selected Night or Day state.

Use reversed Photocell when the desired design response is higher light in bright daytime conditions and lower light at night. The best strategy is objective-led: select a calibrated closed loop for a maintained reference-surface target, and select threshold-based state logic for a Day/Night operating decision. This keeps Photocell lighting control aligned with the intended application rather than treating it as generic switching.

FAQ

Is Silvair daylight harvesting the same as Photocell control?

No. The former modulates electric light toward a calibrated reference-surface target; the latter selects configured Day or Night states from ambient-light thresholds. The daylight harvesting vs photocell difference is continuous closed-loop regulation versus threshold-based state selection.

Does Silvair daylight harvesting require a light meter?

Yes. A light meter is used at the selected reference surface during calibration to enter the workplane illuminance value.

Does Silvair Photocell require calibration?

Yes. The correct sensor is selected and Calibrate is run, but a workplane light-meter lux value is not entered for the Photocell scenario.

Can the same ambient light sensor support both strategies?

Possibly, but only after confirming sensor qualification, Silvair firmware, controller capability, supported profile, and commissioning-tool support. Lux reporting alone is insufficient.

Does daylight harvesting maintain 500 lx everywhere in the zone?

No. It estimates and controls a selected reference surface. Distribution, zoning, luminaire photometry, reflectances, and sensor view determine conditions elsewhere.

Why must calibration reach 75% of target and at least 100 lx?

Those conditions improve the validity of the measurement relationship. Calibration near the configured target under representative conditions reduces error.

What does the ±8% daylight-control tolerance mean?

A small difference around the target may not produce an output change. It is a practical deadband, so continuous control does not mean reacting to every 1 lx variation.

Can occupancy sensing work with both strategies?

Yes. Occupancy can control use-state behavior; daylight harvesting then adjusts output continuously, while Photocell applies occupancy behavior within the selected Day or Night state.

Can in-node scheduling be combined with a Silvair Photocell scenario?

Not directly in the current Photocell scenario. Use an appropriate Multiple Scenes/Scheduling profile if time-based behavior is required, and verify compatibility in commissioning.

When should a Silvair daylight sensor be recalibrated?

After sensor replacement or movement, significant layout or reflectance changes, repainting, luminaire additions/removals, or material lumen depreciation.