What Is Silvair Lighting Control and How Does It Work?

What Is Silvair Lighting Control?

What is Silvair lighting control? Silvair is a wireless lighting-control technology provider that supplies Bluetooth NLC and qualified Bluetooth Mesh firmware, commissioning tools, and optional connected services for compatible lighting and control products. It is aimed at commercial and industrial installations where lighting needs to respond to occupancy, daylight, user input, and operational rules.

Silvair is not a luminaire brand and does not directly regulate every LED load by itself. Manufacturers can embed its firmware and technology in LED drivers, fixture controllers, sensors, and switches, while a project team uses Silvair Commissioning tools to plan, configure, test, and verify the installation. The toolset includes web-based planning and mobile on-site workflows.

A useful distinction is product generation and scope. A market may contain qualified Bluetooth Mesh products, newer Bluetooth NLC products, Silvair-enabled hardware, and products that are electrically compatible with a selected controller. Those descriptions are not interchangeable. Silvair also groups offerings across Bluetooth NLC, Bluetooth Mesh, DALI/D4i, and DLC NLC categories; the exact product documentation determines what a device supports.

How Are Bluetooth LE, Bluetooth Mesh, and Bluetooth NLC Different?

Silvair lighting control rests on several technical layers, each with a different job. Bluetooth Low Energy provides the 2.4 GHz wireless communication foundation. Bluetooth Mesh Protocol provides network addressing, security, message transport, multi-hop relaying, and network communication. Bluetooth NLC Profiles define standardized lighting-device roles, functions, and expected behaviors. Silvair firmware and tools implement and manage these capabilities on supported hardware.

Bluetooth NLC is therefore not merely a few lighting behaviors added to a generic radio link. It is a networked-lighting-control standard spanning wireless communication, mesh networking, and standardized device roles. This is why a normal Bluetooth product is not automatically a Bluetooth Mesh product, and a Bluetooth Mesh product is not automatically a Bluetooth NLC product.

For technical background, see the Bluetooth SIG overview of Networked Lighting Control and Silvair’s Bluetooth standard resources: https://www.bluetooth.com/learn-about-bluetooth/use-cases/lighting-control/ and https://silvair.com/support/pub/bluetooth-standard-resources/.

For readers comparing standards, what is Silvair lighting control is a firmware-and-tools implementation layer above the Bluetooth communication and profile standards.

What Components Make Up a Silvair Lighting System?

A Silvair lighting system usually combines luminaires or LED controllers, occupancy sensors, ambient-light sensors, wall controls, firmware-enabled devices, and commissioning tools. A gateway and cloud-connected services are optional additions rather than mandatory parts of every project.

The NLC profile approach makes device roles more concrete. The following examples explain the purpose of common standardized roles; availability always depends on the selected product, firmware, and qualification status.

This role-based view helps explain how Silvair NLC lighting can support interoperability: devices need the relevant qualified role and function, not merely the same wireless label.

Silvair lighting systems can be specified with distinct device roles when the product documentation confirms the required functions.

Silvair NLC lighting requires confirmation of the relevant qualified profiles and the functions that the selected products implement.

Silvair NLC lighting provides a profile-based approach to lighting roles, but project teams must still validate the full bill of materials.

How Does Silvair Lighting Control Work Step by Step?

In a basic installation, hardware is installed, planned into logical areas and zones, added securely to the mesh network, configured with control behavior, and then tested. During normal use, a sensor, switch, or scheduled event sends a message; the selected luminaires or controllers respond locally according to their configuration.

Provisioning and configuration are different stages. Provisioning securely adds an unconfigured device to a Bluetooth Mesh network, creating a network node. Configuration then writes the relevant addresses, models, keys, subscriptions, and control settings to that node. A sensor does not need a fixed point-to-point link to every light. It can publish to a group address, and luminaires that subscribe to that address respond.

Example: Occupancy sensor detects movement → the sensor publishes a mesh message for its zone → the zone controller or subscribed luminaires interpret the configured occupancy rule → the luminaires turn on or raise output → after the configured vacant period, they dim or switch off. What is Silvair lighting control in this example? It is a local, configured response shared by the network rather than a manual command to each fixture.

Bluetooth Mesh messages can travel by broadcast and multi-hop relay. Relay nodes can forward messages, TTL limits the number of hops, and caching helps prevent indefinite repetition of the same message. Multiple possible paths can improve reliability, but adding relays indiscriminately can increase traffic and interference. This is a practical overview, not a substitute for a project network design.

In operational terms, what is Silvair lighting control is the result of secure network admission followed by configured local messages and device responses.

How Are Projects, Areas, Zones, and Control Profiles Organized?

Silvair Commissioning organizes a project in layers. A Project represents an independent lighting installation and corresponding Bluetooth Mesh network. An Area is a physical part of that project, such as a floor, a parking zone, or a building section. A Zone is a group of luminaires, sensors, and controls inside an Area. A Control Profile is the control logic assigned to that Zone, while a Scenario defines how the zone responds to occupancy, daylight, manual input, or scheduled events.

This structure helps a designer translate a building layout into usable lighting behavior. A car park may be one Area with aisle and bay Zones; each Zone can receive a different profile and scenario. Silvair lighting systems therefore organize behavior by the needs of a space, not only by individual fixture identity.

The formal commissioning workflow is commonly framed as Planning, Implementation, and Verification. Planning uses the web workflow to define the project; field implementation adds and configures devices through a mobile workflow; verification includes sensor calibration where applicable, functional testing, and reporting. It should be performed by an appropriately trained project team rather than treated as a casual app setup.

For a facilities team, what is Silvair lighting control is a structured Project, Area, Zone, and Control Profile model that reflects the building’s spaces.

Silvair lighting systems support project-level organization through Areas, Zones, and Control Profiles.

Which Lighting Functions Operate Locally?

Core local behavior can operate inside the lighting network without a gateway for each command. The precise functions depend on the selected devices, firmware, and Control Profile; no luminaire should be assumed to provide all functions by default.

Silvair smart lighting is best understood as configurable local behavior, not as a promise that every device includes every sensing, scene, scheduling, or color-control capability.

Silvair smart lighting should be evaluated by the actual control profile and hardware capabilities, not by a generic smart-building label.

How does Silvair work with manual control? A supported switch or dimmer publishes a configured command that the assigned zone can use locally.

Silvair smart lighting can combine sensing and user input only where the selected devices and assigned profiles provide those functions.

When Does Silvair Need a Gateway or Internet Connection?

Normal local lighting operation does not depend on Wi-Fi or an Internet connection. Switch control, dimming, scenes, occupancy response, daylight harvesting, zone logic, and in-node schedules can run locally once the system is configured. A gateway extends the system for selected connected, monitoring, remote, or integration functions.

Internet access during commissioning is a separate issue from local runtime. Silvair’s web planning and mobile commissioning workflow use connected services, and field mobile devices need Internet access for the official workflow. Silvair wireless lighting can keep executing its configured local rules if the Internet later goes down, but cloud monitoring, remote services, and selected gateway functions cannot.

For a specification team, what is Silvair lighting control is not a generic compatibility claim; it is a documented set of qualified roles, interfaces, and functions.

Silvair Bluetooth lighting combines the selected hardware interface with a standards-based wireless control layer.

Silvair Bluetooth lighting is not the same thing as any consumer Bluetooth light because the project needs the relevant mesh and lighting-control capabilities.

How Does Silvair Support Interoperability and Device Compatibility?

Interoperability is a specification question, not an automatic consequence of Bluetooth. A generic Bluetooth device is not necessarily Mesh-enabled. A Mesh device may not implement Bluetooth NLC Profiles. A device using Silvair firmware does not by itself prove that the complete luminaire has completed Bluetooth NLC product qualification.

For multi-manufacturer projects, confirm that the required devices are qualified for the relevant NLC Profiles and that their roles and supported functions match the design. Also verify dimming interfaces, sensor capabilities, firmware versions, intended controller/driver combination, and any required commissioning features. Silvair Bluetooth lighting should be specified from product documentation, not inferred from a marketing label.

The physical LED-control method is also hardware-specific. The wireless layer may be paired with an integrated Silvair-enabled LED driver, fixture controller, 0–10 V controller, PWM controller, DALI or D4i interface, or another approved control arrangement. Support for one interface must not be assumed to mean support for all interfaces.

What Affects Silvair Mesh Network Reliability?

Reliability depends on planning, placement, and the installed environment. As a design principle, each device should ideally be in direct wireless range of at least two other devices. Antenna orientation and mounting position influence coverage. Lift shafts, metal shelving, thick walls, and long linear layouts deserve specific review because they can obstruct or reshape the wireless path.

Sparse networks may need additional relay coverage, while dense linear networks can become less efficient if too many nodes relay traffic. Projects with roughly more than 200 devices, long straight layouts, large device spacing, or daylight-harvesting requirements should receive complex-project planning. That reference point is a planning trigger, not a maximum Silvair system size.

After commissioning, a mesh-quality test should be part of verification. These checks are more useful than generic claims about range because actual performance is shaped by the building, the selected hardware, and the final device locations. Silvair wireless lighting needs the same disciplined site thinking as any professional wireless control system.

How does Silvair work in a larger project? It uses planned network organization, configured group behavior, and verification rather than fixed one-to-one sensor wiring.

Silvair wireless lighting performance should be tested after installation because physical conditions affect the completed network.

Benefits, Limitations, and Specification Checks

The main benefits are less need for dedicated control wiring, configurable zones and lighting behavior, distributed local control, and a standards-oriented route to qualified multi-device systems. These benefits can be valuable in both new construction and retrofit projects, especially where adding control cable would be disruptive.

Important limitations remain. Wireless planning, product qualification, commissioning capability, physical environment, and optional connected infrastructure all affect the result. Standards do not eliminate the need to check a bill of materials. Silvair NLC lighting is appropriate when the design team can define the necessary roles, functions, and verification process.

Before specifying a luminaire or controller, check: the exact product category and qualification; required NLC device roles; supported occupancy, daylight, scene, and scheduling functions; driver or control interface; firmware version; commissioning-tool support; gateway or integration needs; and the site network plan. These checks prevent a nominally connected product from being selected for functions it cannot deliver.

Energy monitoring also needs careful interpretation. Silvair connected services can calculate lighting energy from rated power, changing dimming level, and an energy profile. Such a calculated value is not automatically a billing-grade meter reading. A device reporting actual energy under an Energy Monitor profile should be assessed against its own product specification.

For project selection, what is Silvair lighting control is a wireless-control option that should be matched to a specific space, control objective, and site plan.

Silvair wireless lighting is particularly relevant where routing new dedicated control wiring would be disruptive, but it still requires a sound mesh plan.

Where Is Silvair Lighting Control Used?

Silvair lighting systems are relevant in offices, retail spaces, warehouses, factories, industrial facilities, parking garages, educational buildings, healthcare and institutional facilities, and both retrofit and new-build projects. The appropriate use case is driven by the control objective rather than by building type alone.

An office may combine occupancy response, daylight harvesting, and manual user control. A warehouse may use occupancy-led aisle behavior. A parking garage may use zone-based movement response with high/low output. An industrial space may combine zoned control, sensing, and selected schedules. Silvair smart lighting can be useful where these strategies need to be configured digitally and maintained at a project level.

What is Silvair lighting control worth in a retrofit? It can reduce the need for new dedicated control wiring, but only after the hardware interface, network plan, installation conditions, and required functions have been confirmed.

Official Technical Resources

For current product, qualification, and implementation details, consult the official sources rather than relying on a general introduction: Silvair public documents: https://www.documents.silvair.com/support/pub/; Silvair product documents: https://silvair.com/support/product-documents/; Bluetooth SIG NLC overview: https://www.bluetooth.com/learn-about-bluetooth/use-cases/lighting-control/. Product capabilities, firmware support, and qualification status can change, so the relevant manufacturer documentation should be checked during specification.

How does Silvair work across a finished project? The documented project plan, configured device roles, and verification records provide the basis for consistent local behavior. How does Silvair work when a function is added later? The project team must confirm the selected hardware, profile support, firmware, and commissioning method before enabling it.

Silvair Bluetooth lighting should be reviewed as a complete fixture, controller, sensor, and software combination rather than as a radio feature alone.

Frequently Asked Questions

Is every Bluetooth Mesh light compatible with Silvair?

No. A Bluetooth Mesh product may not implement the necessary NLC Profiles, feature set, qualification, or firmware version. Confirm the exact luminaire, controller, and supported roles before selection.

Is Bluetooth NLC the same as Bluetooth Mesh?

No. Bluetooth Mesh provides the networking and message-transport foundation. Bluetooth NLC adds standardized lighting device roles and behaviors for networked lighting control.

Does local Silvair lighting continue to work if the Internet goes down?

Normally, yes. Configured local switching, sensing responses, zone logic, scenes, and in-node schedules can continue without Internet access. Cloud monitoring, remote access, and selected gateway functions cannot.

Is Internet access required during commissioning?

Yes, Internet access is used by the official Silvair planning and mobile commissioning workflow. This is different from the Internet requirements of normal local operation after the project is configured.

Does Silvair scheduling always require a gateway?

No. In-node scheduling can run locally without a gateway during normal operation. Gateway-based scheduling is a separate option used where the system architecture calls for it.

Can products from different manufacturers be used in one Silvair project?

Potentially, but only after verification. Check the required NLC Profiles, product qualification, device role, firmware, interface, and supported functions for each selected product.

Can Silvair work with 0–10 V or DALI LED drivers?

It can work through selected controller, driver, or fixture hardware that supports the relevant interface. Not every Silvair-enabled product supports every interface, so confirm the exact product documentation.

What should be verified before selecting a Silvair-compatible luminaire?

Verify qualification and product category, supported NLC roles, control functions, driver interface, firmware, commissioning support, network design, and any gateway or integration requirements.