Silvair vs Casambi: Which Wireless Lighting Control System Is Better?

A technical, project-selection comparison for commercial wireless lighting control

For a Silvair vs Casambi decision, neither platform is universally better. Silvair is generally the stronger fit when Bluetooth NLC qualification, standardized device profiles, and a standards-based multi-vendor strategy are central to the specification. Casambi is generally the stronger fit when the project depends on a broad Casambi Ready ecosystem, established retrofit modules, and the Casambi App or Casambi Pro workflow. The final decision should be based on qualified device availability, network size, existing driver interfaces, commissioning responsibilities, BMS integration, cloud policy, and replacement requirements.

Silvair vs Casambi at a Glance

This wireless lighting control comparison starts with the practical boundary: both systems can provide local wireless controls, but they establish compatibility, project tooling, and building integration in different ways. A Casambi vs Silvair procurement review should therefore compare the exact products and lifecycle responsibilities—not only the brand names. For Silvair vs Casambi, this is the first decision gate.

Bluetooth Mesh, Bluetooth NLC and Casambi Mesh Explained

Silvair and the Bluetooth NLC stack

Bluetooth Mesh provides the standardized networking, provisioning, security, messaging, and device-model foundation. Bluetooth NLC builds on that foundation by defining application-level profiles for common lighting-control device roles. Therefore, a product that supports Bluetooth Mesh is not automatically a Bluetooth NLC-qualified product. Bluetooth SIG describes NLC as a full-stack lighting-control standard: Bluetooth LE at the radio layer, Bluetooth Mesh at the communication layer, and NLC Profiles at the device layer.

The first six formal profiles are Basic Lightness Controller NLC Profile, Occupancy Sensor NLC Profile, Ambient Light Sensor NLC Profile, Basic Scene Selector NLC Profile, Dimming Control NLC Profile, and Energy Monitoring NLC Profile. They make device roles more explicit for luminaires, sensors, scene selectors, dimmers, and energy-reporting equipment. They are not a promise that every Bluetooth Mesh device implements every profile or feature.

Official source: Bluetooth SIG, Bluetooth NLC full-stack announcement and NLC specifications — https://www.bluetooth.com/press/bluetooth-sig-completes-full-stack-standard-for-networked-lighting-control/

Casambi and its unified technology environment

Casambi uses Bluetooth Low Energy radio technology and Casambi Mesh, but compatibility is delivered through the Casambi technology environment: compatible hardware, common firmware, Casambi Ready product requirements, and Casambi commissioning tools. In Bluetooth NLC vs Casambi terms, the choice is not simply “standards versus no interoperability.” It is standards-based interoperability through specified profiles versus interoperability within a multi-vendor platform under a common technology environment.

A Bluetooth Mesh vs Casambi comparison also needs this distinction. Bluetooth Mesh is a standards-based networking foundation; Casambi Mesh is part of a complete Casambi platform. A Bluetooth Mesh device is not automatically a Casambi device, and a Bluetooth NLC-qualified product is not automatically ready for every Silvair service or workflow. This Bluetooth Mesh vs Casambi distinction should be recorded in the specification. It also makes the wireless lighting control comparison more accurate.

Interoperability and Product Qualification

Silvair versus Casambi should be evaluated at the product level. For Silvair, verify the required NLC Profile version, Bluetooth qualification, implemented features, firmware requirements, and support in the intended commissioning workflow. Bluetooth NLC qualification improves application-level interoperability, but it does not remove the need to verify connected services, firmware-update arrangements, or manufacturer-specific tools.

For Casambi, verify that a product is Casambi Ready or otherwise supported by the intended module; then confirm the required control functions, firmware generation, and compatibility with the target network. In a Casambi vs Silvair tender, “Bluetooth compatible” is not an adequate purchasing criterion for either option. The useful question is whether the documented device role and feature set match the project schedule of requirements. A Silvair vs Casambi tender should capture that evidence as a submittal requirement.

Network Size and Scalability

Casambi publishes a maximum of 127 devices for one Classic network and 250 devices for one Evolution network. Classic and Evolution devices cannot be mixed in a single network; larger installations can be arranged as multiple networks within a Site. These are published limits, not a substitute for RF, traffic, sensor, and commissioning design. The practical capacity should be reviewed below the theoretical maximum where high traffic or many sensing functions are expected.

Bluetooth Mesh has an address space of up to 32,767 elements, but that protocol figure is not a recommended Silvair project size, and an element is not necessarily one physical device. A Bluetooth NLC vs Casambi evaluation should size a Silvair project using current platform documentation, device composition, message traffic, relay settings, RF conditions, and project-specific guidance. Do not translate the Bluetooth Mesh address space into a claim that a Silvair project will support 32,767 luminaires. A second Bluetooth NLC vs Casambi check is whether the chosen tools and devices are supported at the intended scale. That evidence belongs in every Silvair vs Casambi network-design review.

Official source: Casambi Support, maximum size of one Casambi network — https://support.casambi.com/support/solutions/articles/12000061374-what-is-the-maximum-size-of-one-casambi-network-

Lighting Control Functions

Both platforms can deliver common outcomes such as on/off control, dimming, occupancy response, daylight-linked control, scenes, groups, scheduling, and manual controls. However, not every capability is standardized or present in every installation. Tunable white, energy monitoring, D4i data, advanced scheduling, remote access, and analytics depend on selected hardware, firmware, device profiles, drivers, gateways, and service configuration.

This is particularly important for energy data. The Energy Monitoring NLC Profile describes a defined device role, but an installed product still needs the relevant hardware and implemented features. Likewise, tunable white is not one of the six first-wave NLC Profiles. A Silvair or Casambi project should specify each desired behavior against the chosen luminaire, driver, sensor, controller, and service layer. This is also the right approach to a Bluetooth NLC vs Casambi feature review and to a wireless lighting control comparison of advanced functions.

DALI, 0–10V and Driver Integration

Separate the three architecture layers

Silvair states that its lighting-control firmware can be integrated into a component through UART, DALI, or 1–10V interfaces. Other outputs, including 0–10V or PWM, should only be claimed when the selected controller’s current datasheet supports them. In a Silvair vs Casambi comparison, this component-level interface should not be treated as the same architectural category as a multi-device DALI controller.

Casambi offers modules for several driver and load interfaces and also offers Salvador for multi-device DALI control. Salvador variants may support 16, 32, or 64 DALI drivers; the selected model must be checked. Salvador is for Casambi Evolution networks. It counts as one Casambi node, and each addressed DALI driver also counts toward the network total. Casambi documentation also distinguishes connected DALI control gear from DALI switches and sensors, which are not directly connected to Salvador. This makes node accounting and exact model selection material to the design.

Official source: Casambi Support, Salvador Design Guide — https://support.casambi.com/support/solutions/articles/12000103586-casambi-design-guide-salvador

Commissioning and App Workflow

Silvair’s process separates project preparation from site activity: the cloud-based Silvair Web App is used for initial project planning and configuration preparation, while the Mobile App is used to add devices, deliver configuration, test operation, and hand over the site. Basic local lighting operation after commissioning normally does not require the internet, but that is different from claiming that every project-setup step is offline.

Casambi App is used for configuration and everyday control. Casambi Pro is not merely a set of advanced switches inside the standard app: it is a professional workflow for larger or repetitive projects, using Windows for offline planning, floor plans, space templates, and batch configuration, and iOS/iPad for on-site pairing and commissioning. Pro networks use Evolution firmware; configurations created through Pro should not be assumed editable in the standard Casambi App, and Pro does not replicate every standard-app function. For a Casambi vs Silvair rollout, assign planning, pairing, testing, ownership transfer, and documentation responsibilities before installation.

Official source: Silvair Commissioning Apps — https://silvair.com/solutions/wireless-lighting-control/app

Gateway, Cloud, API and BMS Integration

Neither platform normally requires an internet connection for basic local lighting operation after commissioning. However, their complete workflows differ. Silvair uses a cloud-based Web App for initial preparation and a mobile app on site; Casambi cloud, remote access, and API functions depend on the selected gateway and network configuration. A Bluetooth Mesh vs Casambi selection should explicitly separate local runtime, project setup, remote service, API, and BMS requirements.

Silvair provides a BACnet Gateway for Bluetooth NLC-to-BACnet BMS integration and describes it as an on-premise route. Casambi currently labels its Cloud API as a beta service; its developer materials identify REST API and WebSocket interfaces. Treat either option as a project-specific integration architecture: confirm gateway scope, data points, cloud dependence, credentials, network segmentation, and the operating owner before procurement.

Official source: Silvair BMS integration / BACnet Gateway — https://silvair.com/solutions/bms-integration/

Official source: Casambi Developer Site (Beta) — https://developer.casambi.com

Security and Lifecycle Management

Security is not a one-line feature comparison. Bluetooth Mesh uses a security architecture with device, network, and application keys, and a project should define how provisioning, keys, credentials, access roles, and ownership transfer are managed. Ask the supplier how signed firmware updates, over-the-air update support, security advisories, and end-of-support replacements are handled for the exact device family.

For Casambi, request the current system-security documentation and confirm unique credentials, signed or automatic security updates where applicable, gateway and cloud access controls, and the support lifecycle of every component. For both platforms, gateways, cloud APIs, and BMS interfaces introduce additional attack surfaces. The maintainable choice is the one with a documented replacement route, preserved credentials, current firmware policy, and clear responsibility after handover.

Official source: Casambi System Security whitepaper — https://support.casambi.com/support/solutions/articles/12000103567-casambi-system-security-casambi-whitepaper

Retrofit vs New Construction

Both systems can reduce new control wiring in retrofit work. Review existing drivers, DALI or analogue interfaces, enclosure space, RF conditions, retained wall controls, sensors, BMS links, and phased-installation needs. Casambi may be attractive where the selected retrofit requires readily available modules across mixed driver interfaces. Silvair may be attractive where a Bluetooth NLC specification and standardized profile strategy are decisive.

New construction gives more freedom to align fixtures, controllers, sensors, gateways, and BMS architecture from the start. The better Silvair or Casambi choice then depends on the required profile or ecosystem, who will commission it, what data is needed, and how components will be replaced over the building lifecycle.

Which System Should You Choose?

The conclusion for Silvair vs Casambi is conditional rather than absolute. Silvair is generally the stronger fit when Bluetooth NLC qualification, standardized profiles, and a standards-based multi-vendor strategy are central to the specification. Casambi is generally the stronger fit when the project depends on a broad Casambi Ready ecosystem, established retrofit modules, and the Casambi App or Casambi Pro workflow. Decide with qualified device availability, network size, interfaces, commissioning ownership, BMS integration, cloud policy, and replacement planning. A Casambi vs Silvair final review should approve the documented architecture, not merely a feature list. The same principle applies when a client asks whether Silvair or Casambi is easier to support. This wireless lighting control comparison should result in a verified bill of materials.

FY LIGHTING Project Support

FY LIGHTING can develop commercial and industrial LED fixtures around the selected control architecture, including compatible driver interfaces, controller integration, sensor preparation, wiring design, and project-specific testing. Final compatibility should be confirmed against the exact Silvair-enabled or Casambi Ready component, firmware version, driver, and required control functions.

Frequently Asked Questions

Is Bluetooth Mesh the same as Bluetooth NLC?

No. Bluetooth Mesh is the standardized networking foundation. Bluetooth NLC builds on it with lighting-control profiles and device-role requirements. A Bluetooth Mesh product is not automatically a Bluetooth NLC-qualified product. This is the essential distinction in Bluetooth Mesh vs Casambi discussions.

How many devices can a Silvair or Casambi network support?

Casambi publishes limits of up to 127 devices for Classic and 250 for Evolution in one network; generations cannot be mixed. Bluetooth Mesh supports up to 32,767 elements as a protocol address-space limit, but that is not a recommended Silvair project size. Practical Silvair capacity must follow current platform guidance, traffic, RF, and device design. It is a central Silvair vs Casambi sizing question.

Can any Bluetooth NLC device be commissioned with Silvair?

Do not assume so. Verify the exact NLC Profile, qualification, firmware version, implemented features, and support in the intended Silvair commissioning tools and connected services.

What is the difference between Casambi Salvador and a DALI gateway?

Salvador is a Casambi Evolution multi-device DALI controller that brings addressed DALI drivers into a Casambi network. A BMS gateway is a separate architecture layer that exchanges information between a lighting network and building systems such as BACnet.

Can Casambi Pro projects be edited in the standard Casambi App?

Do not assume that they can. Casambi Pro is a separate professional planning and commissioning workflow using Evolution networks; project teams should confirm the current editing and handover rules before selecting the workflow.

Which system is better for BACnet BMS integration?

Silvair may be a simpler fit where direct Bluetooth NLC-to-BACnet integration is required because it offers a dedicated BACnet Gateway. The final choice still depends on the needed data points, on-premise versus cloud design, security policy, and owner support model. This should be specifically assessed in a Silvair vs Casambi BMS decision.

Which system is easier to maintain after a controller or luminaire replacement?

The easier system is the one with documented component compatibility, retained project credentials, replacement procedures, firmware policy, and available support. Confirm these items for the exact products, not only at platform level.