Silvair Commercial Lighting Control for Offices and Buildings

Quick answer: Silvair commercial lighting control is a Bluetooth NLC-based distributed lighting control platform. Local luminaires, sensors and wall controls communicate over Bluetooth Mesh; basic lighting control can operate without a gateway, while selected monitoring, remote services and BMS integrations require gateway infrastructure. HVAC Integration and BACnet integration are separate technical paths.

Commercial Lighting Control Requirements for Offices and Buildings

Offices need more than an automatic ON/OFF circuit. Private offices, open-plan work areas, meeting rooms, corridors, reception areas and shared spaces have different occupancy patterns, daylight conditions and user expectations. A useful control sequence combines occupancy or vacancy response, dimming, scenes, schedules, flexible zoning and manual override. These are the building blocks of commercial building lighting controls and smart office lighting. Plug loads, energy data, occupancy data, HVAC coordination and BMS integration can be added when the project requires them.

Silvair commercial lighting control is the lighting-control layer in that wider building strategy. It is not a complete building automation system. The value comes from applying the right sequence to each space while keeping the fixture, driver, sensor, wall control and network architecture compatible. In practical silvair office lighting, the control layer follows how people use the building rather than treating every room alike.

How a Silvair Office Lighting Control System Is Architected

Silvair commercial lighting control is a distributed Bluetooth NLC platform. A luminaire or LED driver is paired with a Bluetooth NLC controller; occupancy and ambient-light sensors provide inputs; wall controls provide local commands; and the devices communicate over Bluetooth Mesh. This is the architecture behind silvair office lighting and bluetooth mesh commercial lighting. Bluetooth NLC is the standardized lighting-control and profile layer, while Bluetooth Mesh is the underlying networking technology. They are related, but they are not interchangeable terms.

Basic local lighting control can operate without a gateway. An optional Silvair Gateway adds selected monitoring, remote services, gateway scheduling and external integrations. This is a key boundary when specifying silvair commercial lighting control. HVAC Integration and BACnet BMS integration are separate branches: the first provides NLC occupancy information to a compatible thermostat; the second converts selected lighting data and commands into BACnet objects for a BMS.

Architecture at a glance

Luminaire / LED Driver → Bluetooth NLC Controller → Occupancy or ALS Sensors + Wall Controls → Bluetooth Mesh Network → Optional Silvair Gateway → Monitoring / API / Cloud Services

Separate branches: Bluetooth NLC HVAC Integration → compatible thermostat; Silvair BACnet Gateway → BACnet BMS objects. The branches should not be treated as one combined protocol path.

Bluetooth NLC Profiles Used in Office Projects

Profiles define device behavior and interoperability. A project may use only a subset of them, depending on the selected controller, sensor and service configuration.

Lighting Strategies by Office Space

The following are design examples, not fixed Silvair defaults. In silvair office lighting, the designer documents the intended sequence before selecting hardware. Silvair allows the designer to configure the control profiles, levels, timeouts, scenes and links that suit the project. The recommended sequence should be checked against the energy code, lighting design and occupant needs. A smart office lighting sequence should be judged by comfort as well as energy performance.

Recommended Control Strategy by Office Space

A space-specific sequence avoids forcing a whole floor to behave as one room.

Panel, Downlight and Linear Fixture Integration

Panels, recessed downlights, suspended linear luminaires, recessed linear products and surface-mounted commercial fixtures can be integrated when the chosen controller and driver arrangement supports the required profiles. The controller may be fixture-integrated, combined with a sensor, built into a smart driver, or installed externally beside a compatible dimmable driver.

Silvair supports Bluetooth NLC-to-DALI interface paths, including DALI Part 341, and Silvair Firmware has DALI and 1–10 V integration paths. Specific 0–10 V capability depends on the selected controller and driver product. A DALI or 0–10 V label by itself does not prove Silvair compatibility. Dimming protocol compatibility is not the same as Bluetooth NLC qualification. An LED driver that supports DALI or 0–10 V does not automatically make the complete luminaire Bluetooth NLC qualified; the actual NLC device must support the required profile and complete the applicable Bluetooth SIG qualification process.

For a retrofit, check fixture clearance, controller power, driver compatibility, dim-to-off behavior, sensor position, metal obstructions and the wireless path. This is central to office wireless lighting control. For a new fixture, the controller and sensor can be designed into the luminaire from the beginning, supporting office wireless lighting control without assuming that every existing fixture is qualified.

Occupancy, Vacancy and Zone Linking

Silvair allows the designer to configure occupied, standby or prolonged, and vacant lighting states, together with timeout and fade behavior. Occupancy control can raise light when motion is detected; vacancy control uses manual ON with automatic OFF. The choice is a project decision, not a universal Silvair default. Meeting rooms, private offices and training rooms are common vacancy examples, while open offices and circulation areas often use occupancy sequences. This gives commercial building lighting controls a space-specific basis rather than one floor-wide rule.

Zone Linking can share occupancy behavior and manual-switch behavior between related zones. It supports uni-directional and bi-directional linking. Linking can occur only between zones in the same Silvair Area; different Areas cannot be linked. This makes it possible for a meeting room to influence an adjacent corridor, or for two corridor sections to respond together, without turning an entire floor into one oversized zone.

Engineering note: avoid creating excessive manual-control link relationships. Silvair guidance indicates that a zone should not be controlled by more than approximately 28 other zones through manual linking, because excessive relationships can consume RPL resources. Treat that value as a planning recommendation, not a universal device limit.

Daylight Harvesting and Calibration

Silvair uses closed-loop daylight harvesting. An ambient-light sensor continuously measures the indoor condition and sends measurements to the relevant zone controllers, which adjust luminaire output to maintain a user-defined light level as daylight changes. This is different from a simple open-loop photocell threshold.

The workflow requires calibration. A commissioning technician uses a light meter at the target workplane, records the actual lux value, and enters that value in the commissioning app. Installing an ALS alone does not complete daylight harvesting. Perimeter offices, glazed meeting rooms, atriums and lobbies may need separate daylight zones because the illuminance near a window is not the same as the illuminance deeper in the floor plate. Occupancy and manual control should remain coordinated with the daylight loop.

Scenes, Wall Controls and Scheduling

Bluetooth NLC wall controls can provide ON/OFF, dim up, dim down and scene recall. Office scenes may include Work, Meeting, Presentation, Video Conference, Collaboration, Cleaning and After Hours. Scenes can set different levels in several zones, while manual dimming handles conditions that an automatic sequence cannot predict.

In-node scheduling is stored in network devices and can operate without a gateway or continuous internet connection when the devices and project meet the required conditions. Silvair API documentation identifies Firmware 2.20 or newer and Project Version 202101 or newer for in-node scheduling. Changing an in-node schedule requires onsite reconfiguration through the mobile app, and the cited technical material does not support holiday exceptions. Gateway Scheduling is a different service and requires gateway infrastructure.

When Is a Silvair Gateway Required?

A gateway is not required for every lighting function. The service requirement depends on the control method and the project configuration. For silvair commercial lighting control, local operation and connected services should be specified separately.

Plug Load Control for Offices

Bluetooth NLC occupancy information alone cannot switch a receptacle. Plug-load control requires a compatible relay or other device capable of controlling receptacles, plus compliant electrical design. A sensor, schedule or wall control provides the trigger; Bluetooth NLC logic commands the relay; the relay switches selected nonessential loads.

Suitable examples may include selected workstation receptacles, monitors, printers or task equipment. Critical IT, life-safety and continuously powered loads require separate engineering decisions. Silvair should not be presented as a reason to switch every office outlet.

Energy Monitoring: Data Mechanism and Limits

Silvair Energy Monitoring uses a luminaire energy profile together with actual light levels. This makes silvair commercial lighting control measurable by zone rather than judged only by a building-wide estimate. The system calculates lighting energy from the configured power behavior at different levels, processes level changes at approximately 60-second intervals, and organizes the result into 15-minute blocks that can be viewed by zone or Area. This supports comparisons between floors, tenant spaces, meeting rooms and common areas.

There are important limits. Luminaires used for Energy Monitoring within one zone must be the same type and use the same energy profile. The service does not support tunable-white luminaires in the cited technical guidance, and it requires a Silvair Gateway. A gateway serving more than approximately 200 devices may affect energy-data accuracy; this is a data-quality consideration, not a statement that the whole Silvair network has a 200-device maximum.

Occupancy Monitoring and Space-Use Data

Occupancy Monitoring is different from local occupancy lighting. Local control changes light behavior; Occupancy Monitoring collects sensor-detected zone use for space planning, meeting-room utilization and facility decisions. Sensor status is reported by minute and aggregated in the cloud into 15-minute periods. If any sensor in a zone detects motion during a minute, that zone is treated as occupied for that minute.

Standard Occupancy Monitoring data is retained for up to approximately three months. Higher-frequency or near-real-time requirements need the Monitoring API. The data describes sensor-detected zone occupancy, not person identification or employee tracking. A gateway and the relevant connected service are required.

HVAC Integration and BACnet BMS Integration

Bluetooth NLC HVAC Integration can provide occupancy information directly from NLC sensors to a compatible HVAC thermostat. The Bluetooth SIG has adopted the HVAC Integration NLC Profile 1.0, and Silvair has a qualified implementation. This path can avoid an additional gateway or independent network for the occupancy handoff, but it does not mean Silvair directly controls every AHU, VAV box, chiller or plant device.

BACnet integration is a different architecture. The Silvair BACnet Gateway converts selected Bluetooth NLC information into BACnet objects for a BMS. In a connected-building design, silvair commercial lighting control remains the lighting layer while the BMS manages its supervisory role. Examples include Group Occupancy Status, Group Energy Use, Group Ambient Light Level, Group Light Level Set or Status, Group Scene Recall, Group Health Status and Device Health Status. The gateway is BACnet Testing Laboratories certified and uses an on-premise architecture, so BMS communication does not depend on the cloud.

Multi-Floor Office Network Planning

For a complex installation, Silvair guidance commonly recommends planning each Area around approximately 200 devices, but this is not a hard maximum. Actual network performance depends on sensor count, message frequency, building materials, device placement, network topology and the control sequences selected. Area design should follow the building and operational boundaries rather than an arbitrary device count. This matters when commercial building lighting controls span several floors.

Plan Areas and Zones before installation, reserve practical wireless paths, and avoid creating unnecessary link relationships. A multi-floor project may use separate Areas by floor or operational section, with carefully selected links inside each Area. This keeps bluetooth mesh commercial lighting organized without treating it as the lighting-control profile itself. Monitoring capacity and network planning are related but not identical: the approximate 200-device planning recommendation and the gateway energy-data accuracy consideration must not be merged into one false system limit.

Office Retrofit vs New Construction

A retrofit begins with existing driver interfaces, available fixture space, existing wall controls, sensor locations, metal obstructions and the wireless path. This is where bluetooth NLC office lighting and office wireless lighting control decisions must be checked against the existing installation. The same bluetooth NLC office lighting check applies when replacing only part of a floor. DALI, 1–10 V or 0–10 V capability must be checked against the selected controller; the existing protocol does not automatically qualify the fixture.

New construction can plan fixture-integrated controllers or sensors, Area and Zone topology, daylight zones, wall-control locations and gateway services together. That approach can support bluetooth mesh commercial lighting while keeping the Bluetooth NLC profile layer explicit. In both cases, the control sequence should be documented before products are approved.

Commissioning Workflow

A practical commissioning workflow is: (1) create the project in the Web App; (2) upload the floor plan; (3) create Areas and Zones; (4) choose control profiles and parameters; (5) use the mobile app onsite to add luminaires, sensors and switches; (6) calibrate light sensors with a meter; and (7) test, optimize and hand over the configured system. The commissioning record should include device types, driver interfaces, profiles, schedules, links, gateway services and final settings.

Engineering Checklist for a Commercial Office

Before procurement, verify: luminaire type; driver protocol; controller type; sensor type; wall controls; Area and Zone topology; daylight zones; Zone Linking; gateway requirements; monitoring services; HVAC or BMS interface; energy-code sequence; commissioning responsibilities; and handover data. A silvair commercial lighting control review should record each item. Silvair provides control strategies that can be configured to support applicable ASHRAE 90.1, IECC and California Title 24 requirements, but final compliance depends on the project design, devices, settings and jurisdiction. It should never be described as automatic code compliance.

Conclusion and Specification Checklist

A sound office specification connects four decisions: fixture and driver compatibility, the control sequence for each space, the sensor and wall-control plan, and the need for gateway or integration services. Confirm these items before describing a product as compatible. Silvair commercial lighting control is strongest when the project documents what operates locally, what requires a gateway, how Areas and Zones are separated, and how commissioning will verify the result. That is the practical foundation of smart office lighting.

For a quotation or design review, provide the fixture type, driver interface, floor-plan zones, daylight conditions, occupancy strategy, monitoring requirements and HVAC or BMS target. That information allows the controller, sensor, relay and gateway architecture to be checked against the actual building instead of relying on a generic compatibility claim. It also lets the team compare bluetooth NLC office lighting with bluetooth NLC office lighting requirements for the proposed fixtures, and distinguish bluetooth mesh commercial lighting from the NLC profile layer. The specification should use silvair commercial lighting control, silvair office lighting, office wireless lighting control, commercial building lighting controls and smart office lighting only when each term matches the documented system.

Technical References

Technical information reviewed for this article includes Silvair official documentation and product material: SN-211 Lighting Control; SN-209 Daylight Harvesting; SN-213 Recommendations for Complex Lighting Installations; SN-218 Occupancy Monitoring; SN-222 Energy Monitoring; SN-229 Bluetooth NLC Qualification Guide; SGW-102 Silvair Gateway; and SGW-104 Silvair BACnet Gateway. Product qualification and supported features should always be checked against the current manufacturer documentation.

FAQ

What is Silvair commercial lighting control?

Silvair commercial lighting control is a distributed Bluetooth NLC platform for coordinating compatible luminaires, sensors, controllers and wall controls. Bluetooth NLC defines the lighting behavior and profiles; Bluetooth Mesh provides the underlying network. The platform can support occupancy, vacancy, daylight, dimming, scenes, schedules, Zone Linking and selected connected services.

Does Silvair require a gateway in an office?

No, not for basic local Bluetooth NLC lighting control. Occupancy, vacancy, manual dimming, daylight harvesting, Zone Linking and qualifying in-node schedules can operate locally. Energy Monitoring, Occupancy Monitoring, remote services and Gateway Scheduling require a Silvair Gateway and the relevant service configuration.

Can Silvair work with existing 0–10 V fixtures?

It depends on the selected controller and driver. A 0–10 V interface is not sufficient by itself to establish Silvair compatibility. Confirm the controller’s supported interface, power, dimming range, required Bluetooth NLC Profiles and qualification status. Dimming protocol compatibility is not the same as Bluetooth NLC qualification.

Can Silvair integrate with DALI drivers?

Yes, compatible products can use Bluetooth NLC-to-DALI interface paths, including DALI Part 341, and Silvair Firmware includes DALI integration paths. However, a DALI driver or luminaire is not automatically Bluetooth NLC qualified. The complete controller and device combination must support the required profiles and qualification requirements.

How many devices can a Silvair Area contain?

Silvair guidance commonly recommends approximately 200 devices per Area for complex projects, but this is not a hard maximum. Sensor count, message frequency, building materials, placement and topology affect performance. Energy-data accuracy can also be affected when one gateway serves more than approximately 200 devices, which is a separate consideration.

Can zones in different Areas be linked?

No. Zone Linking must occur within the same Silvair Area. Zones in different Areas cannot be linked. Within one Area, linking can share occupancy behavior and manual-switch behavior in uni-directional or bi-directional arrangements.

Does Silvair daylight harvesting use closed-loop control?

Yes. Silvair daylight harvesting uses a closed-loop method: the ambient-light sensor measures indoor light, the measurement is sent to the relevant zone controllers, and luminaire output is adjusted toward a user-defined level. Commissioning requires calibration with a light meter at the target workplane.

Can Silvair occupancy sensors share data with HVAC?

Yes, when the sensor and thermostat support the Bluetooth NLC HVAC Integration Profile. The direct NLC path provides occupancy information to the compatible thermostat and is separate from BACnet BMS integration. It does not mean that Silvair directly controls every HVAC plant device.

What data can the Silvair BACnet Gateway expose?

Depending on configuration, the gateway can expose objects such as Group Occupancy Status, Group Energy Use, Group Ambient Light Level, Group Light Level Set or Status, Group Scene Recall, Group Health Status and Device Health Status. The gateway is BACnet Testing Laboratories certified and uses an on-premise architecture.

Can schedules operate without internet?

Yes, qualifying in-node schedules can operate without continuous internet or a gateway. The cited Silvair API material identifies Firmware 2.20 or newer and Project Version 202101 or newer for in-node scheduling. Reconfiguring the schedule requires onsite mobile-app commissioning, and holiday exceptions are not supported in the cited material.

Can Silvair control office receptacles?

Only through a compatible relay or other device capable of controlling receptacles, together with compliant electrical design. Bluetooth NLC occupancy information alone cannot switch a receptacle. Use the strategy only for appropriate nonessential loads, not critical IT, life-safety or continuously powered circuits.

Is Silvair a complete BMS?

No. Silvair is a lighting control and connected-services platform. A Silvair BACnet Gateway can connect selected lighting information and control functions to a BACnet BMS, while HVAC Integration can provide occupancy information to a compatible thermostat. Building automation, HVAC sequences and electrical compliance remain separate engineering responsibilities.