Yes. A Silvair-based Bluetooth NLC retrofit can often upgrade an existing lighting system without installing a new dedicated control communication cable between luminaires, sensors, and switches. Existing power wiring must remain suitable, and local wiring may still be required between a Bluetooth NLC controller, LED driver, sensor, relay, or power supply. The practical objective is to retain sound luminaires and power infrastructure where possible while adding a wireless control layer.
This approach is useful in occupied offices, warehouses, schools, retail buildings, and production sites where opening finished ceilings or installing a new control bus would be disruptive. A wireless lighting retrofit is particularly valuable when work must be phased around occupancy. It is not a promise of zero electrical work, universal driver compatibility, or automatic wireless coverage. The project still requires a system audit, interface verification, RF planning, commissioning, and functional acceptance.
What a Silvair Retrofit Actually Adds
A Silvair lighting retrofit is best understood as a platform and ecosystem project, not the installation of one fixed Silvair controller. The Silvair-enabled ecosystem can include Bluetooth NLC-qualified controllers, sensor-controllers, LED drivers, converters, wall controls, and gateways from different manufacturers. The exact local interface depends on the selected qualified device and its documented driver interface; common examples include 0–10 V, 1–10 V, DALI, and PWM.
Bluetooth NLC is a full-stack wireless lighting control standard covering the radio, networking/protocol, and device-profile layers. NLC Profiles define standardized behavior for device roles such as lightness control, occupancy sensing, ambient-light sensing, scene selection, dimming control, and energy monitoring. This improves cross-vendor interoperability, but it does not mean that every Bluetooth Mesh product or every interface-labelled driver is automatically compatible.
The main benefit of a Bluetooth mesh lighting retrofit is that communication between networked devices can be wireless. Local electrical connections can still remain between a qualified controller and driver, a sensor-controller and luminaire, or a controller and power supply. Therefore, “retrofit lighting without control wiring” means avoiding a new dedicated communication network, not eliminating every conductor or code-required electrical task.
Bluetooth NLC-Compatible Hardware Roles
| NLC device role | Retrofit relevance | Verify before installation |
| Basic Lightness Controller | Controls a luminaire or group | Driver interface and dimming range |
| Occupancy Sensor | Adds occupancy or vacancy behavior | Detection pattern and mounting height |
| Ambient Light Sensor | Enables daylight control | Position and calibration procedure |
| Basic Scene Selector | Provides scene recall | Zone assignment and control authority |
| Dimming Control | Provides manual dimming | Supported command and local interface |
| Energy Monitor | Measures or estimates energy use | Hardware, profile, and service requirements |
Use Bluetooth NLC-qualified devices and verify each selected component against the manufacturer’s documented interfaces and functions. That discipline keeps a Silvair lighting retrofit interoperable without implying universal compatibility.
Existing System Audit and Retrofit Decision
The first step in a Silvair lighting retrofit is to document the installed system. Record each fixture’s type, quantity, location, mounting method, accessibility, condition, and intended outcome. Identify the LED driver manufacturer and model, input voltage, dimming interface, minimum output, dim-to-off behavior, auxiliary power, and available space for an external or integrated controller.
Also map wall switches, occupancy sensors, photocells, time clocks, relays, existing DALI or 0–10 V controls, BMS connections, permanent power, switched circuits, junction boxes, local disconnects, and emergency circuits. A legacy control wire should not be removed merely because the new network is wireless; it may still be useful for a local connection.
Six Retrofit Outcomes
| Outcome | When it applies |
| Retain fixture and driver | Both physical condition and driver interface are suitable |
| Replace driver | Fixture is sound but the driver cannot provide required control |
| Add external controller | Adequate accessible space exists near the fixture |
| Add integrated controller | The fixture can safely accommodate the qualified device |
| Replace complete luminaire | Fixture, driver, thermal, or access conditions are unsuitable |
| Exclude from project | The location is unsafe, incompatible, or outside scope |
Existing System to Retrofit Path
| Existing condition | Can fixture remain? | Recommended path | New local wiring likely? | Main verification |
| Compatible 0–10 V driver | Usually | Add qualified NLC analog controller | Controller-to-driver connection | Minimum level, polarity, dim-to-off |
| Compatible DALI driver | Often | Use an NLC-to-DALI controller or converter | Local DALI bus and power as required | DALI function and bus configuration |
| Non-dimmable driver | Sometimes | Replace driver or complete luminaire | Driver replacement wiring | Electrical and thermal suitability |
| No controller space | Possibly | External controller or replacement fixture | Enclosure and local connection | Temperature, rating, service access |
| Legacy switched power | Usually | Rework power architecture | Permanent power may be required | Controller remains energized |
| Emergency circuit | Case-specific | Keep required emergency function separate | Code-required wiring | Authority and emergency compliance |
This table turns the audit into a decision rather than an assumption that every existing LED fixture can accept wireless control. It is a practical starting point for a Silvair lighting retrofit.
0–10 V and DALI Wireless Retrofit Paths
For a Silvair lighting retrofit, the selected path should follow the existing driver and the required control behavior.
0–10 V and 1–10 V Compatibility Checklist
A typical 0–10 V wireless retrofit is:
Qualified Bluetooth NLC controller → 0–10 V or 1–10 V output → compatible LED driver → retained luminaire.
Bluetooth mesh replaces network-level communication, while the controller still sends the local analog signal to the driver. Use this checklist before specifying the path:
| Check | Question |
| Existing driver interface | Is it 0–10 V or 1–10 V, and is the interface documented? |
| Minimum dim level | What light level is actually achievable? |
| Dim-to-off | Does the driver turn off, or is a relay needed? |
| Sink/source requirements | Does the controller match the driver’s electrical behavior? |
| Relay requirement | Is a separate switching device required? |
| Controller supply | Where will the controller obtain suitable power? |
| Enclosure space | Is the mounting location safe and accessible? |
| Local wiring | What conductors are required between controller and driver? |
Do not assume that two analog drivers behave alike in a 0-10v wireless retrofit. Test low-level dimming, off behavior, power-cycle recovery, and response when communication is temporarily unavailable. Repeat this validation on every 0-10v wireless retrofit path.
DALI and Bluetooth NLC-to-DALI
A modern DALI wireless retrofit may use:
Bluetooth NLC network → Bluetooth NLC-to-DALI controller or converter → DALI bus → compatible DALI driver.
Silvair’s newer NLC work includes support for the Bluetooth NLC-to-DALI standardized interface associated with DALI Part 341, which is relevant to a DALI wireless retrofit. This is more precise than describing the hardware simply as a “DALI controller.” The selected device may translate Bluetooth NLC commands to the local DALI interface, but the complete solution still depends on the manufacturer’s documented implementation.
Verify the Bluetooth NLC/DALI controller or converter, DALI driver compatibility, required DALI functionality, bus power and configuration, addressing, dimming range, off behavior, and project architecture. Having a DALI driver does not by itself make an installation ready for Silvair.
Controllers, Sensors, Wall Controls, and Power
This is the hardware decision point in a Bluetooth NLC retrofit and a typical wireless lighting retrofit.
A Bluetooth NLC retrofit may use a fixture controller, sensor-controller, separate occupancy sensor, ambient-light sensor, wireless wall control, relay, or gateway depending on the required function. Mounting decisions must consider electrical rating, temperature, enclosure, signal path, service access, and whether the controller remains powered.
Fixture-mounted sensing is suitable when the optical field covers the occupied area. In a wireless LED retrofit, this check is as important as the driver check. Separate sensors may be better in rooms with partitions, high ceilings, irregular layouts, or strong daylight gradients. Existing sensors should be retained, replaced, bypassed, or integrated only after reviewing detection coverage and false-trigger risk. A wireless LED retrofit should not copy an unsuitable legacy sensor layout. If a daylight zone changes, the sensor is relocated, or fixtures are replaced, recalibrate and revalidate the light sensor.
Wireless wall controls can provide ON/OFF, dimming, scene recall, and manual override without new cable between a wall station and every luminaire. This is a common reason to choose a wireless lighting retrofit. A switch can control its assigned Zone, and zone linking can extend that command to related Zones where the sequence of operations requires it.
Why Existing Switched Power Can Cause Problems in a Bluetooth NLC Retrofit
Power distribution and control communication should be planned separately. Branch circuits, luminaire feeds, junction boxes, and suitable local wiring may remain in service, but many networked controllers need continuous power. This is a central decision in a retrofit lighting without control wiring project. If a legacy wall switch removes mains power, the controller can go offline and stop responding to occupancy, manual, or scheduled commands. A retrofit lighting without control wiring design must therefore review the power circuit.
Identify permanent power, switched power, local disconnects, and emergency arrangements before commissioning. Emergency lighting and code-required switching must be evaluated separately by the responsible electrical professional.
Project, Area, Zone, and Mesh Planning
A Bluetooth mesh lighting retrofit adds planning work even when it removes new control cabling.
A Bluetooth mesh lighting retrofit still requires an RF design. Concrete walls, metal ceilings, metal luminaires, equipment, racks, long corridors, and high mounting positions can affect relay paths. Divide the site using both physical geometry and required control behavior.
- Project:one separate Bluetooth mesh network.
- Area:a physical or management region within the Project; devices in the same Area should be able to communicate with one another.
- Zone:a group of devices within an Area that shares a control profile or behavior.
- Device:an individual luminaire, sensor, switch, relay, proxy, or other network participant.
A Project can scale to approximately 8,000–10,000 devices and about 2,000 Zones according to current Silvair planning information. Approximately 200 devices per Area is an engineering planning reference, not a protocol hard limit and not the same as a 200-device Project limit.
When Does a Silvair Retrofit Need More Detailed Mesh Planning?
Treat an installation as complex when the Project exceeds roughly 200 devices, devices form long straight lines, distances approach more than about 60% of practical radio range, daylight harvesting is used, or gateways and connected services are added. These conditions do not automatically make the design impossible; they require more deliberate Area boundaries, relay review, and testing.
In dense grid layouts, do not add relays blindly. Silvair guidance commonly recommends keeping relay devices to around 10% of the devices in an Area, although sparse, outdoor, or long-distance layouts may require more. More relays do not automatically make a network more reliable because they can increase mesh traffic.
A relay forwards mesh messages, and a proxy mainly allows a smartphone or tablet to communicate with the Bluetooth Mesh network through Bluetooth LE. Static proxy and auto proxy behavior should be considered separately. Avoid casually enabling static proxy and relay on the same device; the combination can reduce performance, and companion-switch assignments require the same commissioning care. A relay forwards traffic only within its own Area, so Areas must reflect real RF connectivity rather than being arbitrary administrative folders.
Mesh Quality Acceptance
Perform the Silvair Mesh Quality Test independently for every Area and target 100% connectivity before final acceptance, especially when in-node scheduling is used. Test after representative devices are installed, not only from a theoretical floor plan.
Phased Deployment and Silvair Commissioning Workflow
A phased Silvair lighting retrofit is the safest way to standardize a complex site.
A phased Silvair lighting retrofit reduces the cost of discovering incompatibility after hundreds of devices are installed.
- Pilot Area:test drivers, controllers, sensor coverage, wall controls, mesh behavior, dimming, occupancy, and power recovery.
- Repeatable standard:document the controller, mounting method, driver interface, sensor, Zone profile, labels, and workflow.
- Area-by-Area installation:deploy by floor, tenant, production zone, building wing, or maintenance window.
- Optimization:adjust Zone boundaries, occupancy settings, daylight calibration, scenes, schedules, and relay placement.
Silvair’s practical workflow separates planning from field implementation. The Web App is used for Project setup, floor plans, Zones, control profiles, and parameters. The Mobile App is used on site to discover and add luminaires and sensors, add switches, calibrate light sensors, and test behavior.
Commissioning includes provisioning and configuration. Provisioning adds a device to the network and Zone and provides the required network address and security information. Configuration applies the selected profiles, parameters, relationships, and control behavior. A device appearing in software is not proof that the lighting sequence works.
Scheduling and Gateway Options
In-node scheduling stores and executes schedules in mesh devices and can operate without a gateway. Gateway scheduling uses a Silvair Gateway for centralized or connected scheduling. Local occupancy, vacancy, manual control, scenes, zone linking, and daylight functions do not automatically require a gateway.
When Is a Silvair Gateway Required?
A gateway may be required for gateway scheduling, energy monitoring, occupancy monitoring, remote emergency lighting test monitoring, remote control, automated demand response, or other connected services. The scope should be decided before installation because a gateway can introduce additional network, configuration, and service requirements.
Functions Retained or Added After Retrofit
| Function | Availability after retrofit |
| Manual control | Depends on wall control and profile |
| Timer switch | Depends on configured device behavior |
| Occupancy or vacancy | Depends on sensor coverage and parameters |
| Daylight control | Depends on ambient-light sensor and calibration |
| Scheduling | In-node or gateway-based, depending on design |
| Scenes | Depends on scene selector and Zone configuration |
| Zone linking | Depends on control narrative and profiles |
| High/low-end trim | Depends on driver and controller support |
| Power-up behavior | Depends on device configuration and circuit design |
These functions should be specified as project behavior, not assumed from the word “wireless.”
Commissioning, Acceptance, and Handover
A retrofit lighting without control wiring project still needs formal testing and documentation.
Test manual ON/OFF, dimming, occupancy, vacancy, sensor timeout, daylight response, scenes, scheduling, zone linking, difficult RF locations, and power-cycle recovery. Confirm the selected driver responds correctly through its 0–10 V, 1–10 V, or DALI interface. Compare actual behavior with the approved control narrative.
Retrofit Acceptance Checklist
- Driver and controller compatibility verified.
- Permanent power and switched circuits confirmed.
- Controller mounting, temperature, and service access accepted.
- Sensor coverage and daylight calibration verified.
- Device, Area, and Zone assignments checked.
- Silvair Mesh Quality Test reaches 100% for every Area.
- ON/OFF, dimming, occupancy, and daylight behavior tested.
- Power-cycle and communication recovery tested.
- Scheduling and gateway scope documented.
- Commissioning Report completed and handed over.
The Commissioning Report should record the Project, Areas, Zones, devices, profiles, zone linking, scheduling, energy monitoring, gateway scope, mesh quality, final parameters, unresolved issues, and changes made during implementation. This turns testing into an auditable handover.
Short Retrofit Examples
- 0–10 V office:retain sound fixtures and drivers, add qualified NLC analog controllers, verify dim-to-off, and keep local controller-to-driver wiring.
- DALI warehouse:verify the DALI driver and bus, then use a qualified Bluetooth NLC-to-DALI solution rather than assuming any DALI device will work.
- Non-dimmable fixture:replace the driver if the fixture is suitable, or replace the complete luminaire.
- Wall switch cuts mains power:rework the power architecture so the mesh controller remains energized while manual control is handled through a qualified wall control.
FAQ
Does a Silvair retrofit require a gateway?
A gateway is not automatically required for a Bluetooth mesh lighting retrofit.
No. Local occupancy, vacancy, manual control, scenes, zone linking, daylight control, and in-node scheduling can operate without a gateway when the selected devices support them. A gateway may be needed for gateway scheduling, remote control, energy monitoring, occupancy monitoring, remote emergency lighting test monitoring, or automated demand response.
Can Silvair scheduling work without an internet connection?
Yes, when in-node scheduling is selected and supported by the commissioned devices. The schedule is stored and executed in mesh devices. Gateway scheduling is a different architecture and is used when centralized or connected services are required.
Can existing 0–10 V control wiring be reused?
This question is central to a 0–10 V wireless retrofit and an 0-10v wireless retrofit. Existing conductors may be reusable only for the local interface. A second 0-10v wireless retrofit should not be specified until polarity and driver requirements are checked.
Often, but only after inspection. Existing conductors may be reused for a local controller-to-driver connection if their condition, polarity, routing, voltage, and installation method are suitable. Wireless communication does not make an unsuitable conductor acceptable.
Can Bluetooth NLC and DALI be used together?
A DALI wireless retrofit is possible when both sides of the interface are qualified.
Yes. A qualified Bluetooth NLC-to-DALI controller or converter can provide the wireless network layer while DALI remains the local driver interface. Verify the selected device, DALI driver, required functions, bus power, configuration, and dimming/off behavior.
What if an existing wall switch removes controller power?
This is a common failure mode in a Bluetooth NLC retrofit.
The controller can become unavailable to the mesh, so occupancy, schedules, and remote commands may fail. Review permanent and switched circuits and redesign the power arrangement where necessary so the networked controller remains energized.
How do I verify mesh quality after retrofit?
The test is essential in a wireless lighting retrofit and should be repeated after material layout changes.
Run the Silvair Mesh Quality Test independently for every Area after representative devices are installed. Target 100% connectivity before acceptance, then investigate weak paths, relay placement, Area boundaries, and obstructions rather than relying on theoretical radio range.
Can every existing LED fixture be retained?
A wireless LED retrofit can preserve many suitable fixtures, but retention must be proven by the audit. The same principle applies to a second wireless LED retrofit in a different building.
No. Retention depends on fixture condition, driver interface, dimming behavior, controller space, thermal conditions, power architecture, and qualified device compatibility. The audit may lead to driver replacement, an external controller, a complete luminaire replacement, or exclusion.
Is every DALI driver compatible with Silvair?
No. A DALI label is not a compatibility certificate. Check the Bluetooth NLC/DALI controller or converter, driver functions, addressing, bus power, configuration, dimming range, off behavior, and the complete project architecture.
What should the final handover include?
The handover closes the Silvair lighting retrofit project.
Provide the Commissioning Report, device locations, Project/Area/Zone assignments, profiles, parameters, zone links, schedules, gateway scope, mesh quality results, sensor calibration records, unresolved issues, and approved changes. Acceptance should document behavior, not only software discovery.
Technical Sources
These references support the technical claims in this Silvair lighting retrofit article.
- Silvair Commissioning and product documentation: https://silvair.com/support/product-documents/
- Silvair FAQ and Bluetooth Mesh support: https://silvair.com/support/faq/
- Silvair Bluetooth NLC public documents: https://www.documents.silvair.com/support/pub/
- Silvair wireless lighting control and firmware information: https://silvair.com/solutions/wireless-lighting-control/firmware/
- Bluetooth SIG NLC resources: https://www.bluetooth.com/learn-about-bluetooth/feature-enhancements/networked-lighting-control/
English