A Silvair control profile is a zone-level configuration that combines one lighting control scenario with the settings available for that scenario. Silvair lighting control strategies include manual control, occupancy and vacancy sensing, daylight harvesting, photocell control, multiple scenes, central control, and central control for dual output. The selected profile defines intended levels, timeouts, fades, trims, overrides, and power-up behavior for compatible devices in that zone.
Use this sequence: required lighting behavior → zone → scenario → profile parameters → assigned profile → commissioned and tested devices. In short: Zone → Control Profile (Scenario + Settings) → Commissioned Devices → Verified Lighting Behavior. This page compares Silvair lighting control strategies; dedicated pages cover deeper design and commissioning.
What Is a Silvair Control Profile?
A Silvair control profile is a zone-level configuration that combines one control scenario with the settings available for that scenario. Once assigned to a zone, it defines the intended behavior of compatible luminaires, sensors, and controls in that zone. The selected scenario and its available settings together form the profile, which is the core of Silvair lighting control strategies.
The selected scenario establishes the logic—for example, manual activation, automatic occupancy response, or light-level control based on daylight. Its settings determine levels, delays, fades, trims, power-up behavior, and overrides. One profile may be shared by several zones. If its settings change, every zone using that shared profile may be affected; a zone that needs a different behavior should use a separate or saved-as-new profile.
Illustrative example only—not universal Silvair defaults: two zones may use occupancy sensing, while Zone A is configured for 100% Occupied, 30% Prolonged, and 0% Vacant, and Zone B for 80%, 20%, and 10%. The scenario is the same; the profiles differ because their settings differ. Actual values must follow the space use, lighting design, applicable energy rules, and current device documentation; this is fundamental to Silvair lighting control strategies.
Silvair Control Profiles vs Bluetooth NLC Device Profiles
The terms describe two different things. Silvair control profiles are zone configurations in Silvair commissioning tools: they answer, “How should this zone operate?” A Bluetooth NLC device profile is a Bluetooth SIG-defined device role with interoperability requirements: it answers, “What role does this product play in a Bluetooth NLC system, and what models and behaviors must it support?”
Bluetooth NLC device profiles include Basic Lightness Controller, Occupancy Sensor, Ambient Light Sensor, Basic Scene Selector, Dimming Control, and Energy Monitor roles. Bluetooth NLC lighting strategies do not derive their multi-vendor interoperability from the Silvair zone profile. That interoperability comes from the Bluetooth NLC full-stack standard—radio, communication, and device layers—and the qualification of the relevant devices. The zone profile then configures the intended behavior of the actual compatible devices. Bluetooth SIG NLC overview
Complete List of Silvair Control Scenarios
The table compares the principal scenario families. Silvair lighting control strategies integrate Silvair control scenarios; Silvair central controls, Silvair dual output control, and Bluetooth NLC lighting strategies require role validation.
| Scenario | Initial activation | Required input | Main behavior | Typical application |
| Manual control | Manual | Manual control input | User selects on, off, dim, or scene behavior | Spaces needing direct, predictable operation |
| Occupancy sensing | Automatic | Compatible occupancy sensor | Detect occupancy, then reduce or switch off after vacancy | Convenience-focused rooms and circulation areas |
| Vacancy sensing | Manual | Manual input + occupancy sensor | Manual ON; automatic reduction or OFF after vacancy | Areas where unwanted automatic ON should be avoided |
| Occupancy + daylight harvesting | Automatic control state | Occupancy sensor + light sensor + controller | Occupancy logic with closed-loop daylight response | Daylit spaces requiring automatic activation |
| Vacancy + daylight harvesting | Manual | Manual input + occupancy sensor + light sensor + controller | Manual ON with daylight response and vacancy reduction | Daylit spaces needing user-initiated activation |
| Photocell | Scenario-dependent | Ambient light sensor | Threshold-based Day/Night response or preset state | Exterior or threshold-driven lighting behavior |
| Multiple scenes | Manual or configured behavior | Scene-capable control input | Recall up to four configured scene behaviors | Flexible rooms with distinct operating modes |
| Central control | Scenario-dependent | Central controller and relevant inputs | Controller calculates the zone lighting decision | Coordinated zone-level behavior |
| Central control for dual output | Scenario-dependent | Central and local control roles | One group central, another local | Zones requiring two control approaches |
Silvair control scenarios determine which inputs and parameter sets are relevant. These Silvair control scenarios do not prove every selected device supports every possible feature; confirm the controller, firmware, sensor, switch, and luminaire capabilities.
Manual Control, Occupancy Sensing, and Vacancy Sensing
Silvair manual controls use user input as the primary trigger. These Silvair manual controls do not require an occupancy sensor. A compatible manual control can request on, off, dim, or scene behavior, while the profile can set default level, fade time, trim limits, power-up behavior, and scene settings. Manual control is appropriate where direct operation and predictable local behavior are more important than automatic activation.
Occupancy sensing automatically activates the control state when occupancy is detected. It subsequently follows configured Occupied, Prolonged, and Vacant behavior. A wall switch can be used for manual override, but automatic recovery depends on the manual override timeout and vacancy conditions. Vacancy sensing differs at the first step: a manual initial ON action is required, after which occupancy information can still drive automatic dimming or switch-off when the area becomes vacant.
Silvair manual controls and vacancy sensing should not be described as compatible with any arbitrary Bluetooth wall switch. Silvair documentation commonly addresses Bluetooth EnOcean wall switches; a compatible nearby device acts as an EnOcean adapter that receives and converts the signal. Device selection and switch assignment must be verified for the specific project. These distinctions help choose Silvair lighting control strategies without turning this page into an installation guide; they also clarify why Silvair manual controls remain a distinct strategy.
Daylight Harvesting vs Photocell Control
Daylight harvesting and the Photocell scenario both use ambient-light information, but their control logic is different. Daylight harvesting is a closed-loop control method: a compatible light sensor monitors the zone’s light condition, sends measurements to the zone controller, and the controller adjusts luminaire output to maintain the configured work-plane illuminance. A daylight-harvesting zone needs compatible sensing and control devices; commissioning uses a lux meter, and replacement of a sensor requires recalibration.
Silvair’s daylight-harvesting guidance includes practical constraints: during calibration, measured work-plane illuminance should be at least 75% of the target and not below 100 lx. The sensor should be located above the controlled work plane and protected from direct sun, highly reflective surfaces, and interference from adjacent lighting. See SN-209 Silvair Daylight Harvesting and the current Silvair product documents.
Photocell control is primarily threshold-based. It responds when ambient light crosses Day/Night thresholds by selecting preset states or levels and may be combined with occupancy conditions. It is not a simplified form of daylight harvesting: the scenarios use different parameters and should be calibrated and tested differently. In occupancy sensing with daylight harvesting, occupancy automatically activates the control state; electric lighting may nevertheless remain at 0% when daylight is sufficient and no minimum-light setting applies. These Bluetooth NLC lighting strategies should therefore be evaluated by their intended response, not just by their sensor type. Bluetooth NLC lighting strategies also require validation against the selected device roles.
Multiple Scenes and Scheduling
The Multiple scenes scenario supports up to four customized scenes. Depending on the specific functionality, a scene may be configured as static, automatic, or automatic with daylight harvesting. This is useful when one zone needs distinct functional states—for example, presentation, cleaning, collaboration, or daylight-responsive working modes.
Multiple scenes should be described separately from scheduling. A scene defines a recallable control behavior; scheduling defines time-based invocation or system behavior and belongs in a dedicated Scenes and Scheduling page. In this comparison page, the key question is whether the zone needs a small set of deliberate, selectable behaviors. The selected scenario determines which settings are exposed in the profile and which inputs can recall them.
Central Control and Central Control for Dual Output
The Central control scenario calculates the zone lighting decision in a central light controller. Sensors and switches provide inputs, the controller evaluates the logic, and luminaires receive the output decision. “Central” describes where the decision is calculated; it does not automatically mean cloud control, a BACnet gateway, a hub-and-spoke topology, or BMS connection.
The Central control for dual output scenario is a hybrid control arrangement: one group is controlled centrally and another group is controlled locally. “Dual output” in this name must not be interpreted as a two-channel 0–10 V driver, a tunable-white driver, or two electrical output circuits. It describes control behavior, not a wiring or driver specification.
The phrase Silvair central controls is sometimes used informally, but the scenario names above are more precise. Silvair central controls should be understood as a behavioral description, not a cloud-control product category. Likewise, Silvair dual output control should be read as the complete Central control for dual output scenario. Silvair dual output control describes coordinated central/local behavior rather than electrical outputs. Both Silvair central controls and Silvair dual output control require validation of controller roles, device firmware, and architecture.
Occupied, Prolonged, and Vacant States
Occupancy-related Silvair lighting control strategies use a state sequence rather than a simple ON/OFF rule:
Occupied → after Occupied timeout → Prolonged → after Prolonged timeout → Vacant → next trigger returns the zone to its configured behavior
The Occupied state remains active while occupancy is detected and for the configured Occupied timeout after the most recent detection. Each new occupancy event resets that timeout. Prolonged is an intermediate state; it is typically, but not necessarily, set to a lower light level. After the Prolonged timeout, the zone enters Vacant. Vacant may be 0% or a non-zero background level and remains in effect until a new applicable trigger occurs.
This sequence helps a project retain orientation lighting, apply high-low behavior, or avoid an abrupt transition to darkness. It does not imply any universal timing or level values. Actual settings belong in the selected profile and must be evaluated for the space.
Scenario-Specific Control Profile Parameters
Parameter availability depends on the chosen scenario. The table below prevents the mistaken assumption that every profile exposes the same settings.
| Scenario family | Typical available parameters |
| Manual control | Default light level, fade time, low-/high-end trim, power-up behavior, Scene A/B |
| Occupancy / vacancy | Occupied, Prolonged, and Vacant levels and fades; Occupied and Prolonged timeouts; manual override timeout; trims; power-up behavior; Scene A/B |
| Daylight-harvesting variants | Applicable occupancy/vacancy parameters plus daylight-control settings and, where available, a separate “Keep light above minimum value” setting |
| Photocell | Day/Night threshold, associated default or occupancy level, occupancy timeout, fade time, trims, and power-up behavior |
| Multiple scenes | Up to four customizable static, automatic, or automatic-with-daylight-harvesting scene behaviors |
| Central control | Default light level, fade time, trims, power-up behavior, Scene A/B, and scenario-specific control logic |
Important: low-end trim is not an always-on minimum. It limits the normal dimming range, but a luminaire may still be manually switched off, set to 0% in the app, or turned off by applicable automatic control. “Keep light above minimum value” is a separate daylight-harvesting setting and should not be conflated with low-end trim. Consult SN-200 Silvair Commissioning and SN-211 Silvair Lighting Control for current parameter and software details.
How Silvair Control Profiles Are Assigned and Commissioned
Create a Project, Area, and Zone in the Silvair Web App; select or create a profile; choose its scenario and parameters; then add compatible luminaires, sensors, and controllers with the Silvair Mobile App. Send the configuration, resolve Configuration Required status, assign compatible EnOcean switches, calibrate daylight-harvesting or Photocell zones, and test Auto, Off, scenes, occupancy, daylight response, and the commissioning report.
A profile can serve multiple zones. Treat edits to shared Silvair control profiles as a controlled change because they may alter all linked zones. Button labels and exact workflow steps can change between releases, so current guides should govern the field process.
What a Control Profile Does Not Define
A profile defines intended zone behavior. It does not by itself define Bluetooth Mesh relay/proxy planning, Zone linking, scheduling, energy-monitoring roles, gateway or BACnet/BMS configuration, the luminaire’s DALI/D4i/1–10 V/UART interface, firmware-supported capability, sensor coverage, sensor mounting, or calibration quality. Final performance also depends on compatible equipment, configuration, switch assignment, and validated sensing.
How to Choose the Right Silvair Lighting Control Strategy
Select Silvair lighting control strategies from the required user experience. These Silvair lighting control strategies should be chosen before final device selection. Choose Manual control when direct user control is sufficient. Choose Occupancy sensing when automatic activation is desired; choose Vacancy sensing when users should initiate light while vacancy still drives automatic reduction. Choose daylight-harvesting variants when the zone requires closed-loop electric-light adjustment as daylight changes. Choose Photocell when threshold-based Day/Night behavior is the objective. Choose Multiple scenes when distinct operating modes must be recalled.
Choose Central control when the project requires a controller to calculate the zone decision. Choose Central control for dual output when centrally and locally controlled device groups need to coexist. Before finalizing a profile, ask: automatic or manual ON? Is a Prolonged state required? Can vacant output be non-zero? Is daylight harvesting or threshold-based photocell behavior intended? Which manual overrides and return-to-auto conditions are acceptable? Which devices are verified to support the required roles?
How to Specify FY LIGHTING Fixtures for a Silvair-Controlled Project
A dimmable driver alone does not make a fixture Silvair-ready. For an FY LIGHTING fixture to participate in a Silvair-controlled project, the project must verify the compatible Bluetooth NLC/Silvair controller or module, model-specific firmware, NLC qualification status where applicable, driver interface, dimming range, sensor and switch support, and the intended zone behavior.
FY LIGHTING can evaluate fixture types, zone boundaries, control interfaces, and project requirements to identify a suitable matching approach. Compatibility and certification claims should be made only against the relevant model numbers and current technical documents; no fixture should be represented as compatible with all Silvair devices or every Bluetooth Mesh product without supporting evidence.
Technical Sources
- Bluetooth SIG — Bluetooth® Networked Lighting Control
- Bluetooth SIG — Occupancy Sensor NLC Profile v1.0
- Silvair — Product Documents: SN-200, SN-209, SN-211
- SN-209 Daylight Harvestingand SN-211 Lighting Control. Check current revisions before specification.
FAQ
What is the difference between a Silvair control profile and a Bluetooth NLC device profile?
A Silvair control profile is a zone-level scenario-plus-settings configuration that determines intended behavior in that zone. A Bluetooth NLC device profile is a Bluetooth SIG device role and interoperability requirement. The former configures a zone; the latter defines what a qualified device role must support.
Does changing a shared Silvair control profile affect multiple zones?
Yes. A single profile may be assigned to more than one zone, so changing its parameters can affect every zone that uses it. If one zone needs different behavior, create or save a separate profile before changing its settings.
Can the Vacant light level be higher than 0%?
Yes. Vacant can be a non-zero background level when the application needs orientation or low-level illumination. It remains active until the next applicable trigger returns the zone to its configured behavior.
Does low-end trim prevent a luminaire from switching off?
No. Low-end trim limits the normal dimming range, but it does not necessarily stop a luminaire from being manually switched off, set to 0% in the app, or turned off by an applicable automatic scenario.
What is the difference between daylight harvesting and the Photocell scenario?
Daylight harvesting uses closed-loop adjustment to maintain a configured work-plane condition as daylight changes. Photocell behavior is primarily threshold-based: it reacts to Day/Night light levels by selecting preset states or outputs. Their parameters, calibration, and intended responses differ.
Does the Central control scenario require a cloud gateway?
No. In Silvair terminology, Central control identifies where the zone lighting decision is calculated. It does not inherently require cloud control, a gateway, BACnet integration, or a hub-and-spoke topology.
Is Central control for dual output the same as a dual-channel driver?
No. The Central control for dual output scenario describes one centrally controlled group and one locally controlled group. It should not be interpreted as a two-channel driver, tunable-white driver, or two electrical output circuits.
Can different devices in one zone support different parts of a control profile?
A profile can express intended zone behavior, but actual results depend on the roles and capabilities of the compatible luminaires, controllers, sensors, and switches in that zone. Verify model-specific documentation, firmware, qualification status, and commissioning results before relying on a feature.
English