Bluetooth NLC is the first full-stack standard for wireless lighting control, covering standardization across the radio, protocol, and device layers. Leveraging the unique capabilities of Bluetooth Mesh, it enables multi-vendor interoperability and positions itself as the global wireless standard for commercial and industrial lighting markets.

Bluetooth NLC also addresses standard compliance issues that have caused confusion in recent years. It serves as a clear distinguisher between fully standard-compliant solutions and proprietary systems that only use Bluetooth radio to a limited extent.

Bluetooth NLC Profiles define standards for specific device types, including Ambient Light Sensor, Basic Lightness Controller, Basic Scene Selector, Dimming Control, Energy Monitor, and Occupancy Sensor. These application profiles operate on top of Bluetooth Mesh, each with its own set of performance parameters and supported models.

The profiles enforce certain optional features that have been part of Mesh 1.0 since its release in 2017. By making these requirements stricter, Bluetooth NLC Profiles help improve both interoperability and performance.

• First full-stack standard: Provides a comprehensive solution for wireless lighting control.

• Cross-vendor interoperability: Ensures compatibility through standardization at the device layer.

• Clarifies Bluetooth Mesh compliance: Addresses market confusion by distinguishing fully standard-compliant solutions from those that only use Bluetooth to a limited extent but are still labeled as Bluetooth Mesh.

• Better market recognition: Helps standard-compliant products stand out.

• Facilitated project specification: NLC Profiles ensure compliance with the Bluetooth Mesh standard, guaranteeing state-of-the-art wireless performance.

• Lower cost and faster innovation: Supports quicker development cycles and reduced costs.

• Wider product range: Expands the variety of products available on the market.

• Bottom line: A globally interoperable ecosystem, faster mass adoption, increased market opportunities, and additional revenue models.

Silvair views Bluetooth NLC as a significant milestone in the development of a global, interoperable standard for wireless lighting control. Interoperability has always been our goal, and we firmly believe that it is the key to achieving mass adoption. We see Bluetooth NLC as the final piece needed to reach this goal.

Silvair believes that Bluetooth NLC will unlock the full potential of Bluetooth Mesh in lighting applications. That's why we are committed to supporting the Bluetooth NLC standard in our solutions. We will make sure that all future Silvair Firmware releases comply with Bluetooth NLC Profile Specifications, and that our Commissioning Tools can work with any Bluetooth NLC-compliant devices.

The Silvair Firmware stack has already been qualified (https://silvair.com/blog/silvair-completes-bluetooth-nlc-qualification-becoming-worlds-first-certified-supplier-bluetooth-nlc-solutions), becoming the first officially certified Bluetooth NLC solution on the market.

Yes. Silvair Commissioning is open to any Bluetooth NLC-compliant third-party devices. However, depending on the scope of features implemented in a particular NLC device, additional technical requirements may apply. In addition to the technical requirements, certain commercial requirements must also be met before a device can enter the Silvair platform. We can provide detailed technical and commercial requirements under an NDA.

• Silvair blogpost (https://silvair.com/blog/bluetooth-sig-introduces-networked-lighting-control-nlc-profiles/)

• Bluetooth SIG press release (https://www.bluetooth.com/press/bluetooth-sig-completes-full-stack-standard-for-networked-lighting-control/)

• Bluetooth SIG blogpost (https://www.bluetooth.com/blog/introducing-bluetooth-nlc-a-milestone-in-the-interoperability-journey/)

• Bluetooth SIG blogpost (https://www.bluetooth.com/blog/the-benefits-of-bluetooth-networked-lighting-control/)

For each new device:

1. The manufacturer must contact Silvair Support to request firmware version 2.30 or later.

2. If the device hasn't previously passed Silvair’s component tests, it must pass these tests.

3. The manufacturer must qualify the device line as described in the Bluetooth NLC qualification guide.

If the device is already using an older version of Silvair firmware:

1. The manufacturer must qualify the device line as described in the Bluetooth NLC qualification guide.

2. The manufacturer must contact Silvair Support to request over-the-air update (OTAU) activation for the device line.

3. You can update the firmware as described in SN-208 OTA firmware update for provisioned devices.

No. The qualification is done for the entire device line.

1. Go to the login page of your Silvair web app or Silvair mobile app for iOS/iPadOS.

2. Use the “Don't remember your password?” option.

3. Enter your email and click “Send email” to request a password change.

4. Check your inbox (and spam folder) and click the link provided in the email.

5. Enter a new password and click “Change password”.

The Silvair web app is used to plan your project. In the web app, you can set up areas, zones, and control scenarios, link zones, and predefine scenes before anything is built on site. The web app can also be used to set up and use such services as scheduling or energy/occupancy monitoring, view ELT (emergency lighting testing) reports, and download commissioning reports.

The Silvair mobile app (for iOS/iPadOS or Android) is used on site to send the configuration created in the Silvair web app and stored in the cloud to the devices after they've been installed and powered up. The mobile app for iOS/iPadOS can also be used to test light behavior, adjust some parameters on site, and troubleshoot issues.

• A Silvair account created in the Silvair web app or Silvair mobile app for iOS/iPadOS.

• A lighting control plan based on the expected light behavior in each part of the project.

• SN-204 Silvair Commissioning quick start guide.

• SN-211 Silvair Lighting Control application note.

If your project is complex, see SN-213 Recommendations for complex lighting installations. A project is considered complex when it meets at least one of these criteria:

• There are more than approximately 200 devices.

• At least some devices are placed along a straight line.

• Distances between devices are longer than 60% of the radio range of the devices.

• The daylight harvesting scenario is used.

• A gateway is used with energy/occupancy monitoring, scheduling, or automated demand response.

A project is a separate lighting installation created in the Silvair app. It can be as large as a whole building or site, or as small as a single room. Each project is a single Bluetooth mesh network that is separated from other such networks. A project can consist of multiple areas.

You can create as many projects as you want.

You can add 8,000–10,000 devices.

A project can be divided into areas for better clarity and easier navigation. Typically, an area is a floor, but it can also be a part of a big floor, or even a part of a building, such as a parking lot. All devices in an area must be in range of the Bluetooth mesh network and each area must be connected to other areas. Areas can include a floor or site plan to help the user navigate the project.

If an area is separated from other areas in the project and can't communicate with them, it should be set up as a separate project.

No. If your project has fewer than approximately 200 devices, you can have all of them in one area.

You can create as many areas as you want, as long as the project does not exceed 2,000 zones.

No. We do not recommend this. For an area where each device is a sensor-controller, 350 devices is too many. In this case we recommend using at least four areas with no more than approximately 200 devices in each area. Make sure that all devices in each area are within range of the Bluetooth mesh network.

No. 200 devices is an estimate. In some cases a network of more than 200 devices will work correctly without dividing it into smaller areas. But the correct function of a network depends on such factors as: types of sensors used, publishing frequency of sensor data, arrangement of devices, and environmental conditions (wall thickness, ceiling thickness, and construction material).

No. A gateway is only required when you use energy/occupancy monitoring, scheduling, or automated demand response in that area.

An area consists of zones that contain devices (luminaires, sensors, and switches) that have been commissioned using the Silvair mobile app. A zone can be a whole room or a part of it, or a separate space. All devices in the zone operate according to the control profile set up for the zone.

You can create up to approximately 2,000 zones.

You can add as many devices as you want, as long as there are not more than 200 devices in the whole area.

Provisioning is the process of adding a device to a zone. During provisioning, the device receives a unique address and network key, and the device key is calculated. If a device is already provisioned to one zone, it must first be reset before it can be provisioned to a different zone.

Monitor the flashing of the status LED, or power the device off and on. If the LED flashes every two seconds, or if the device does not flash a few times after powering on, it means that the device has been provisioned.

Perform one of the following steps:

• If you know which zone the device has been added to, navigate to the zone in the Silvair mobile app. Then, tap next to the device name to make sure that this is the correct device. If the correct device flashes quickly, tap .

• Refer to the device datasheet for instructions about how to reset the device. In most cases, you need to press and hold a reset button for some time. Some devices have a switch that triggers a reset when a magnet is applied to them. When the reset is triggered, the status LED will flash every second. After the reset is complete, the status LED will flash every 0.3 seconds.

Commissioning is the process of provisioning and configuring a device. The device is usually configured immediately after provisioning.

Configuring is the process of sending a predefined set of parameters to the device so that it operates according to the control profile selected in the Silvair web app.

A control profile is a scenario with settings used to control a zone. For each zone, you can select one of the default profiles or assign a new profile with different setting values. If you set a different scenario for a profile, different settings may be available.

A scenario defines how the light behaves in a specific zone. If you set a different scenario for a profile, different settings may be available.

1. In the Silvair web app, go to the project and area.

2. Click a zone, expand the “Profile” list, and select “New profile”.

3. Enter a name for the profile, select a scenario based on the required light behavior, and click “Create”.

To change the language of the Silvair web app when you are not logged in, at the bottom of the login page, click the current language and select a new one. When you are logged in, click > Change language, and select a new language.

To change the language of the Silvair mobile app, change the system language of your mobile device.

1. In the Silvair web app, go to the area.

2. Right-click in the view, and select “Edit area”.

3. Click , open a JPEG, PNG, or PDF file, and click “Save”.

Because you've created a zone but haven't assigned a profile to it. In the Silvair web app, click the zone and select a profile. The ‘+’ sign will disappear.

Because there are issues in the zone that require your attention. In the Silvair web app, right-click the zone, select “Zone details”, and read the message under the “Alert” heading.

You must first remove all devices from all the zones in the area before you can remove the area itself in the web app.

1. In the Silvair mobile app, go to each zone and remove all the devices one by one.

2. In the Silvair web app, go to the project, and in the area field, click > Remove.

1. In the Silvair web app, go to your projects.

2. In the project field, click > Update > Update now.

1. In the Silvair web app, go to your projects.

2. In the project field, click .

If the “Update” option is not available, you already have the latest version.

In the Silvair web app, click > Release notes.

1. In the Silvair web app, go to the project and click “Collaborators”.

2. Select the appropriate check boxes and click “Revoke access”.

Note that access can't be revoked for a user who has the “Owner” role. There must always be one owner per project.

1. In the Silvair web app, go to the project and click “Collaborators”.

2. In the collaborator field, click > Change role.

3. Select “Owner” and click “Transfer”.

After transferring the owner role, you will no longer be able to fully manage the project, and your role will become “Manager”.

Zone linking is a feature that allows multiple zones to be controlled by a single zone. For example, an occupancy sensor or a wall switch in one zone can trigger the light to turn on in the linked zones.

No. Zone linking works only between zones in the same area.

1. In the Silvair mobile app, go to the project, area, and zone.

2. Tap ‘+’ and then tap the device you want to add.

If the slider is set to “Near”, only the nearest devices with a signal strength of up to -45 dBm will appear. If the slider is set to “All”, devices with a signal strength of up to -85 dBm will appear.

A relay is a function assigned to a device that allows it to send data packets further into the Bluetooth mesh network. A device in the mesh network is configured as a relay using the Silvair mobile app.

No. Relays in one area will only route traffic from devices in that area. In the following case, we recommend that you add the isolated device to the blue area.

Some devices are automatically set up to act as relays by the Silvair app. A device can also be manually set up as a relay in the mobile app.

By default, approximately 10% of devices are automatically set up as relays when they are added to a zone. However, this approach will not always work, such as when some devices are placed along a straight line, especially if the distance between them is long. For information about how to set up relays manually in these cases, see SN-213 Recommendations for complex lighting installations.

A proxy is a function assigned to a device that allows mobile devices, such as smartphones and tablets with the Silvair mobile app installed, to connect to it. This connection allows mobile devices to communicate with the Bluetooth mesh network and configure or control devices. Depending on the Silvair firmware version and the project version, a device can act as a static proxy or an auto proxy.

A device set up as a static proxy always allows the Silvair mobile app to communicate with the mesh network. The static proxy function is available only in devices that do not support the auto proxy function (firmware version 2.16 or earlier). In this case, the static proxy function will be automatically set up in some of the devices when they are added to a zone.

A device set up as an auto proxy acts as a proxy only on demand, when the Silvair mobile app within range wants to communicate with the mesh network. The auto proxy function requires Silvair firmware version 2.17 or later. If a device supports the auto proxy function, it will be automatically set up as an auto proxy when added to a zone.

An EnOcean adapter is a function assigned to a device that allows a Bluetooth EnOcean switch to communicate with a Bluetooth mesh network. A device that acts as an EnOcean adapter receives data packets from the EnOcean switch, converts them into mesh messages, and sends the messages into the mesh network. A device is set up as the adapter using the Silvair mobile app.

If your network supports the auto proxy function, you can use a device as both an auto proxy and an EnOcean adapter at the same time. You can also combine the auto proxy, EnOcean adapter, and time authority functions, as well as the auto proxy, relay, and time authority functions.

Do not use a device as both a static proxy and a relay at the same time, because this will reduce the performance of the device.

Also, do not also use a device as both an EnOcean adapter and a static proxy or a relay at the same time. If you combine these functions, there will be issues with receiving packets from the EnOcean switch. As a result, the devices in the mesh network may not respond as intended when the switch is pressed.

1. In the Silvair mobile app for iOS/iPadOS, go to the project, area, and zone.

2. On the "Test" tab, tap the On, Off, A scene, and B scene buttons to make sure that the luminaires behave as intended.

3. Use the sliders to make sure that the luminaires respond.

4. Tap Auto and walk around the zone to allow the sensor to detect motion, and make sure that the light turns on at the correct level.

A commissioning report includes details about the project, areas, zones, devices, control profiles, zone linking, scheduling, energy monitoring, gateways, mesh quality, and collaborators.

1. Open the project in the Silvair web app.

2. Click Report > Download.

If the required light level is not close to the luminaires' rating or if daylight harvesting is used, the lighting control will operate correctly. However, if the lumen depreciation is large, the required light level may not be achieved. In this case, try one of these steps:

• In the Silvair web app, go to the zone where the luminaires are added and click . Then, increase the Max. value for Low/high-end trim. If daylight harvesting is used, calibrate the light sensor again.

• Replace the luminaires. If daylight harvesting is used, calibrate the light sensor again.

1. In the Silvair mobile app for iOS/iPadOS, go to the zone.

2. On the "Settings" tab, tap "Motion sensitivity".

3. Tap a sensor with adjustable sensitivity.

4. Move the slider to the left to decrease sensitivity, and tap "Apply".

5. If decreased sensitivity does not resolve the issue, move the slider to the farthest left and tap "Apply" again.

6. Repeat steps 3, 4, and 5 for each sensor that you suspect is too sensitive.

To check the firmware version of all devices in the project:

1. In the Silvair web app, go to your project.

2. Click Report > Download to download the Commissioning report.

3. Open the report and search for “firmware version”.

To check the firmware version of a single device in the web app:

1. In the Silvair web app, go to the project and area.

2. Right-click the zone and select “Zone details”.

3. Move the cursor over the device name to see its firmware version.

To check the firmware version of a single device in the mobile app for iOS/iPadOS:

1. In the Silvair mobile app for iOS/iPadOS, go to the project, area, and zone.

2. On the “Devices” tab, tap the device and select “Diagnostic”.

3. Search for Element 0 - Silvair Debug Server > Full Firmware Version.

1. The manufacturer must qualify the device line as described in our Bluetooth NLC qualification guide.

2. The manufacturer must contact Silvair Support to request over-the-air update (OTAU) activation for the device line.

3. You can update the firmware as described in SN-208 OTA firmware update for provisioned devices.

No. The device name will remain the same as before OTAU.

No. The device name can be whatever you want.

An energy profile defines the power of the luminaires in the zone at a range of light levels and is used to calculate energy consumption and cost savings. You must manually create the energy profile for each type of luminaire in the project by measuring the power in watts (W) for several light levels and entering the data into the Silvair web app.

For information about how to create an energy profile, see SN-222 Silvair Energy Monitoring.

Open the project and click “Energy use”. To calculate energy savings, make sure that each zone has an energy profile assigned, and that the “Energy monitoring” tab is configured in the project settings, as described in SN-222 Silvair Energy Monitoring.

The data for that period will be interpolated between the last recorded data point before the power failure and the first recorded point after power is restored.

The data will show zero occupancy for that period. It will not show that the power was lost.

The gateway doesn't store any data, so data for that period is lost. However, gaps will be interpolated between the last recorded data point before the power failure and the first recorded point after power is restored.

The gateway does not store data, so data for that period is lost.

The devices don't store data, so data for that period is lost. However, gaps will be interpolated between the last recorded data point before the gateway stopped working and the first recorded point after it starts working again.

The devices don't store data, so data for that period is lost, even if the sensors are still operating.

The gateway doesn't store data, so data for that period is lost. However, gaps will be interpolated between the last recorded data point before the connection was lost and the first recorded point after the connection is restored.

The gateway does not store data, so data for that period is lost. 

1. Go to the Silvair web app and configure a profile with a Multiple scenes / Scheduling scenario.

2. Create events that specify the zone, time, and day(s) when a scene from this scenario will be recalled.

There are two types of scheduling:

• Gateway scheduling: Requires a gateway to be added to the network.

• In-node scheduling: Devices handle the scheduling themselves. This feature is available only for project versions 202101 or later, where all devices use firmware version 2.20.2 or later.

For more information, see SN-201 Silvair Scheduling.

If the event settings haven't changed, the gateway will continue to operate as it did before the power or internet loss.

If the event settings have changed during the outage, the gateway will update its configuration from the cloud as soon as the power or internet connection is restored and will apply the new settings at the appropriate time.

If the Silvair Gateway is powered on but the internet connection is down, scheduling will continue using the last configuration downloaded from the cloud. This configuration is stored in memory and will function for at least one week.

However, if the Silvair Gateway is restarted (turned off and on) while the internet connection is down, scheduling will stop because the gateway loses its time settings. Scheduling will resume after the gateway reconnects to the internet and the time is restored, allowing it to trigger events according to the schedule.

The Silvair gateway reads event configuration from the cloud every 4–6 minutes. Any changes to the event start time will be applied to the mesh network a few minutes later.

However, if the event start time is changed 4–6 minutes before the new start time, the gateway may not update in time, and the event may not be triggered until the next scheduled start time.

When the clock is moved back, such as from 2 AM to 1 AM, any events scheduled between 1 AM and 2 AM will be triggered twice because the hour repeats.

When the clock is moved forward, such as from 2 AM to 3 AM, the entire hour is skipped. In this case, only the last event scheduled within that skipped hour will be triggered at the new 3 AM.

In-node scheduling (INS) is a feature that allows you to set up events to recall preconfigured scenes at specific times without using a gateway, unlike gateway scheduling.

• With INS, the Silvair mobile app sends event configurations to the devices during commissioning.

• INS supports scheduling in local time but not in astronomical time (based on sunrise and sunset), which is available in gateway scheduling.

• INS may experience time drift, while gateway scheduling triggers events according to the gateway's time.

Time drift is the difference between real time and the time in the mesh network. In networks without a real-time clock (RTC), the drift can be up to 2 minutes per month. In networks with an RTC, it can be up to 30 seconds per month.

An RTC is a hardware device with a clock that minimizes time drift, ensuring accurate scheduling.

When a device with an RTC and a battery is added to a zone, the Silvair app checks its accuracy against other RTC devices with batteries that were added before. If the new device is more accurate, it becomes the time authority, and all other devices sync their time with it.

The TA is a function assigned to one device, making it the source of the current time shared with other devices in the network. Initially, the Silvair app configures the first device as the TA. When new devices are added to a zone, they can become the new TA if they have a battery and a more accurate real-time clock.

No, but we recommend having a battery-powered device in the network to act as a time source during power outages. We also recommend that this device have an RTC to minimize time drift and ensure accurate scheduling. If there is no RTC, you can minimize time drift by periodically syncing the time between the mobile device and the mesh network using the mobile app for iOS/iPadOS.

No, because only one device can act as the time authority at a time.

You can define up to 16 events. Each event can recall one of four scenes defined in a Multiple scenes / Scheduling scenario.

Yes. When you manually override a schedule, the luminaires will remain at the set value until the next scheduled event starts.

No. Two times a year, after each time change, you'll need to use the mobile app for iOS/iPadOS to sync the time between the mobile device and the mesh network.

When you're on site and within range of the network, open the Silvair mobile app for iOS/iPadOS and go to your projects.

In the project field, tap  > Time sync > Sync time.

No. Devices with a battery added to projects will appear the same as those without a battery. The app won’t show which devices have a battery and which don’t.

Yes. You can find the device in the Commissioning report. 

1. Open the project in the Silvair web app.

2. Click Report > Download.

3. Open the report and search for “time authority”.

If there is a relay in the zone, all devices will receive the current time.

The network receives the current time from the mobile app for iOS/iPadOS when a device is set as the time authority, either automatically by the app or manually. This device (with an RTC and a battery, if available) maintains the time, and all other devices sync with it.

No. If only some devices are powered down, their internal clocks will automatically sync with the rest of the network after power is restored.

If a device with a battery acts as the time authority, all other devices will sync their time with it after power is restored, and scheduling will work correctly.

If the power outage continues for more time than the battery can support, or there is no battery-powered device in the network, all devices will lose time, and scheduling will not work. In this case, use the Silvair mobile app for iOS/iPadOS to sync the time between the mobile device and the mesh network.

We recommend manually setting up a device as the time authority (TA) only if the required device, such as one with a battery and an RTC, wasn’t set automatically by the app.

1. In the Silvair mobile app for iOS/iPadOS, go to the project, area, and zone.

2. On the “Devices” tab, tap the device.

3. Tap the “Time Authority” toggle bar to set this device as the time authority.

4. Go to the area with the device previously set as the TA. If there's no zone alert in the area, check other areas. Then, tap Configure, to reconfigure the old TA.

For more information, see SN-201 Silvair Scheduling.

No. The time authority, and thus the network, receives the current time when:

• A device is set as the time authority.

• The project timezone is changed, and the time authority is reconfigured.

• Time is synced manually from the mobile app for iOS/iPadOS. 

Yes. You can use the Silvair mobile app for iOS/iPadOS to update devices with firmware versions 2.19 or earlier. Before the firmware can be updated, the manufacturer must contact Silvair Support to request over-the-air update (OTAU) activation for a specific line of devices.

Also, to use in-node scheduling, the project version must be 202101 or later. To update your project in the Silvair web app, go to your projects, and in the project field, click > Update > Update now.

1. The manufacturer of the devices used in your project must contact Silvair Support to request over-the-air update (OTAU) activation for those devices.

2. Use the Silvair mobile app for iOS/iPadOS to update the firmware of all devices through OTAU.

3. Remove all devices from the project.

4. Add devices to the project back again.

After that, you can start creating scheduling events.

Yes. INS will work correctly if all devices have firmware version 2.20.2 or later. INS can be used independently of gateway scheduling.

No. To use scheduling, you must configure a profile with a Multiple scenes / Scheduling scenario.

We strongly recommend that you update each device before using INS. Devices with firmware version 2.19 or earlier won't be able to trigger scheduled events, propagate time through the network, or participate in the time recovery process. This may also cause issues with syncing time for devices with the latest firmware.

Only 100% mesh quality ensures that INS will work correctly. We also recommend maintaining 100% quality for all mesh lighting control networks, even if they don't use INS.

If the project has only one area, use the Silvair mobile app for iOS/iPadOS to perform a standard mesh quality test to make sure that 100% connectivity is maintained in that area. If there are two or more areas, perform the mesh quality test for each area independently to make sure that 100% connectivity is maintained in each area.

Additionally, you can verify cross-area connectivity by starting the app in the area where the time authority is located and, while standing in that location, trying to control at least one device from each other area. The location of the time authority device can be found in the Commissioning report.

The manual event will override the scheduled event in the linked zone.

Zone linking doesn't affect in-node scheduling. Scheduled events will be triggered independently for each zone.

Both events will be triggered at the same time, but one will instantly overwrite the other. As a result, only one scene from one of the events will be visible in the space. When creating events, make sure they are set for different times.

Emergency lighting testing is a feature that allows regular testing of emergency luminaires that have been commissioned into a project using the Silvair app.

The emergency lighting testing (ELT) that is performed automatically by each device according to a schedule defined by the user in the Silvair web app. Tests can also be started manually for a specific device using the Silvair mobile app for iOS/iPadOS.

The mobile app for iOS/iPadOS is used to collect test results from all emergency devices in the project. The results are then sent to the cloud and can be viewed in the Silvair web app.

Both functional and duration tests can be scheduled.

A functional test checks the integrity of the circuits and the correct operation of the luminaire, switching device, and backup battery. It is performed at the same time for all zones.

A duration test checks if the backup battery provides power for the required period of emergency operation. It should be performed in at least two separate groups of zones to make sure that luminaires in adjacent zones are not tested at the same time. You can create up to four groups of zones and configure the test to start in each group at intervals of one week.

Emergency lighting testing complies with the IEC 62034 standard (automatic test systems for battery-powered emergency escape lighting), the DALI-2 Part 202 specification, and the Bluetooth Mesh standard.

Only one emergency luminaire can be added to a zone. You must define the zones so that each zone has only one emergency luminaire. If you add two or more emergency luminaires to a zone, they will be tested at the same time. If an emergency occurs during or shortly after the duration test, these luminaires will not be able to provide the emergency lighting function.

No. Create additional schedules for duration tests to make sure that luminaires in adjacent zones are tested at different times. If they are tested at the same time and an emergency occurs during or shortly after the duration test, they will not be able to provide the emergency lighting function.

In the list of devices, emergency devices are marked with an “Emergency” label.

1. In the Silvair mobile app for iOS/iPadOS, open the project, area, and zone.

2. On the “Devices” tab, tap the emergency device.

3. Tap .

4. Select the type of test you want to perform and tap “Start test”.

1. Open the Silvair mobile app for iOS/iPadOS.

2. Tap next to the project name and select “Emergency lighting”.

3. Tap “Collect test results”.

4. Select the area from which you want to collect test results.

5. Move to the area to collect the test results.

Go to the Silvair web app, open the project, and click “Emergency”.

The test results can be collected as often as you want. When you collect new results, they replace the previous results in the ELT report for each device that is available in the mesh network, powered on, and not damaged.

Only the current test results are shown in the ELT report. Each time test results are collected, the previous results for each device that is available in the mesh network, powered on, and not damaged are overwritten.

You can view the ELT report in the Silvair web app. The report shows the area and zone where each device is located. You can find the zone on the floor or site plan in the web app or mobile app. Also, if the “Last update” field of the ELT report does not change after the test results are collected, it means that the luminaire is unavailable in the mesh network, powered off, or damaged.

No, but we recommend having a device with a battery in the network to act as a time source during power outages. We also recommend that this device has an RTC to minimize time drift and ensure accurate scheduling. If there is no RTC, you can minimize time drift by periodically syncing the time between the mobile device and the mesh network using the mobile app for iOS/iPadOS.

Tests will be performed according to the user-defined intervals, but not at the correct time. To make sure that the tests are performed at the correct time, sync the time in the mesh network.

One reason may be that the area doesn’t include a timekeeping device with a fully charged battery, so devices in the network don’t know the correct time. To make sure that the tests are performed at the correct time, sync the time in the Bluetooth mesh network. Another reason may be that the tests were postponed.

A test can be postponed when it can't be started at the scheduled time because the battery was low or the luminaire was in a different state than normal. The devices will try to start a postponed test again every hour over the next 1–24 hours for a functional test, and every 24 hours over the next 1–4 days for a duration test.