1. Go to the login page of your Silvair web app or Silvair mobile app.

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 the ELT (emergency lighting testing) reports, and download commissioning reports.

The Silvair mobile app is used on site to send the configuration created in the Silvair web app and stored in the cloud to the devices after the devices have been installed and powered up. The mobile app can also be used to test the light behavior, adjust some parameters on site, and troubleshoot issues.

• A Silvair account created in the Silvair web app or Silvair mobile app.

• 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:

• has more than approximately 200 devices,

• at least some devices are placed along a straight line,

• distances between devices are large,

• uses a daylight harvesting scenario,

• has a gateway.

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 8000–10000 devices.

A project can be divided into areas for better clarity and easier navigation. For example, an area can be a room, a floor, or a whole site, or a part of a floor, site, or building. 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 cannot communicate with them, it should be set up as a separate project.

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

You can create as many areas as you want.

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 that you use at least four areas with no more than approximately 200 devices in each area. Make sure that all devices in each area are in range of the Bluetooth mesh network.

No. A gateway is required only 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 luminaires in the zone operate according to the control profile set up for the zone.

You can create up to approximately 2000 zones.

You can add up to approximately 200 devices. 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).

Provisioning is 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 the device does not flash a few times after power on, it means that the device has been provisioned.

Do 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. But 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 one second. After the reset is complete, the status LED will flash every 0.3 seconds.

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

Configuring is sending a predefined set of parameters to the device so that it works 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 settings values. If you set a different scenario for a profile, different settings may be available.

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

1. In the Silvair mobile 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, on the bottom of the login page, click the current language and select a new language. 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 have created a zone but not assigned a profile to it. In the Silvair web app, click the zone and select a profile. The “+” sign will disappear.

Because there are some 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 there is no “Update” option 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 correct check boxes and click “Revoke access”.

Note that access cannot 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 you transfer 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 one zone. For example, an occupancy sensor or a wall switch in one zone can trigger the light to come 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 which 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 set up to act as a relay automatically 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. But this approach will not always work, for example if some devices are placed along a straight line, especially if the distance between devices 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. The connection allows the 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 auto proxy.

A device set up to act 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, or project version 202004 or earlier). In this case, the static proxy function will be set up in some of the devices automatically when they are added to a zone.

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

An EnOcean adapter is a function assigned to a device which 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, changes 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 an auto proxy and as an EnOcean adapter at a 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 at a time as a static proxy and as a relay because this will reduce the performance of the device.

Do not also use a device as an EnOcean adapter and at a time as a static proxy or a relay. If you combine these functions, there will be issues with the reception of packets from the EnOcean switch. Thus, the devices in the mesh network may not respond as intended when the switch is pressed.

1. In the Silvair mobile app, 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 comes on at the correct level.

The 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 when 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.

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:

1. In the Silvair mobile app, 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.

Continue as described in SN-208 OTA firmware update for provisioned devices.

No. The device name will stay 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. The energy profile must be created manually for each type of luminaire in the project by measuring the power in watts (W) for several light levels and entering it into the Silvair web app.

For information about how to create an energy profile, see SN-206 Energy monitoring – calculation.

Open the project and click Energy use. For energy savings calculations to be available, each zone must have an energy profile assigned as described in SN-206 Energy monitoring – calculation. Also, the “Energy monitoring” tab must be configured in the project settings as described in SN-222 Silvair Energy Monitoring Service.

The energy monitoring data for that period will use an interpolation between the last data point before the power failure and the first data point after the power is restored.

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

There is no mechanism to store any data on the gateway, so data is lost on power loss. But gaps in the data will be interpolated between the last data point before the power failure and the first point after the power is restored.

There is no mechanism to store any data on the gateway, so data is lost on power loss.

If the gateway stops working, energy data for that period is lost. But gaps in the data will be interpolated between the last data point before the gateway stopped working and the first point after it started working again.

If the gateway stops working, occupancy data for that period is lost, even if the sensors are still working.

The gateway does not store any energy data locally, so if the internet connection goes down the data will be lost. However, gaps in the data will be interpolated between the last data point before the connection went down and the first point after the connection is restored.

The gateway does not store any occupancy data locally, so if the internet connection goes down the data will be lost.

Go to the Silvair web app and configure a profile with a Multiple scenes / Scheduling scenario. Then, create events that specify in which zone, at what time, and on which day(s) a scene from this scenario will be recalled.

There are two types of scheduling: gateway scheduling and in-node scheduling. The gateway scheduling requires a gateway to be added to the network. In the in-node scheduling, the scheduling is done by the devices themselves (but only for project versions 202101 or later, where all the devices added to the project use firmware version 2.20.2 or later).

For more information, see SN-201 Silvair Scheduling.

If the event settings have not changed, the gateway will behave in the same way as before the loss of power or internet connection.

If in the meantime the event settings have changed, as soon as the power / internet connection is restored, the Silvair gateway will read the new configuration from the cloud and apply it at the right time.

If the Silvair Gateway is powered on but the internet connection is down, scheduling will work with the last configuration that the gateway obtained from the cloud. The configuration is downloaded and stored in memory. It will work for at least one week.

If the Silvair Gateway is restarted (turned off/on) while the internet connection is down, scheduling will not work, because the gateway will lose time. The time will be restored after the gateway reconnects to the internet. The gateway will then be able to trigger events according to the schedule.

The Silvair gateway reads event configuration stored in the cloud every 4–6 minutes. Changes to an event start time will be applied in the mesh network a few minutes later.

Note that if the start time of an event is changed 4–6 minutes before the new start time, the update may not be read by the gateway in time. Thus, the event may not be triggered until the next start time of the event.

INS is a feature that allows you to set up events that recall preconfigured scenes at the right times without having to use a gateway, in contrast to gateway scheduling.

• In INS, the Silvair mobile app is used to send the event configuration to the devices during commissioning.

• Events in INS can be scheduled in local time, but not in astronomical time based on sunrise and sunset like in gateway scheduling.

• INS is subject to a time drift, while in gateway scheduling events are triggered according to the gateway time.

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

An RTC is a hardware device that has a clock and keeps the gradual time drift to a minimum to make sure that the scheduling is accurate. 

When a device with a battery and an RTC is added to a zone, the Silvair app checks if it is more accurate than any of the other RTC devices with a battery that have been added before. If this new device is more accurate, it will be then set up as the time authority and all the other devices will sync their time with it.

The TA is a function assigned to one device which makes it act as the source of the current time that is shared with the other devices in the network. At the start, the Silvair app sets the first device as a TA. When each next device is added to a zone, it can become the new TA if it has a battery and a more accurate real-time clock.

No. However, we recommend that you have a device with a battery in the network to act as the source of time during a power outage. We also recommend that this device has an RTC to keep the time drift to a minimum and make sure that the scheduling is accurate. If there is no RTC, you can keep time drift to a minimum by periodically using the mobile app to sync the time between the mobile device and the mesh network.

No, because only one device can act as a 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. If you use manual control to override a schedule, the luminaires will stay at the set value until the start of the next scheduled event.

No. Two times a year, after each time change, you will have to use the mobile app to sync the time between the mobile device and the mesh network.

When you are on site and in range of the network, open the Silvair mobile app and go to your projects.

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

No. The app cannot find devices with a battery.

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 the devices will receive the current time.

The network receives the current time from the mobile app when a device is set up to act as a time authority automatically by the app or manually. The time is then kept by this device (with an RTC and a battery, if available) and all the other devices sync their time with it.

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

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

If the power outage is longer than the battery capacity, or there is no battery-powered device in the network, all devices in the network will lose time and the scheduling will not work. To restore time in the network in such a case, use the Silvair mobile app and sync the time between the mobile device and the mesh network.

We recommend that you manually set up a device to act as a time authority (TA) only if the required device (for example, one with a battery and an RTC) has not been set up automatically by the app.

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

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

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

4. Go to the area with the device that was previously set up as a TA. If there is no zone alert in the area, search in different 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 up as the time authority,

• the project timezone is changed and then the time authority is reconfigured,

• time is synced manually from the mobile app. 

Yes. You can use over-the-air update (OTAU) to update devices with firmware versions 2.19 and earlier. To be able to update firmware, OTAU must be made available by Silvair at the manufacturer’s request for devices used in the project.

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. Use over-the-air update (OTAU) to update the firmware of all your devices.

2. Remove all devices from the project.

3. Add devices to the project again.

Then, 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 will not be able to trigger scheduled events, propagate time through the network, or participate in the time recovery process. This can also cause problems with syncing time for devices with the latest firmware.

Only 100% mesh quality ensures that the INS will work correctly. We also recommend keeping 100% quality for all mesh lighting control networks, even if they do not use INS.

If the project has only one area, do a standard mesh quality test to make sure that 100% connectivity is maintained in that area. If there are two or more areas, do the mesh quality test for each area independently to make sure that 100% connectivity is maintained in each area.

Also, 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 does not 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 these events will be visible in a given space. When you create events, make sure that they are set up 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 Silvair solution is based on emergency lighting testing (ELT) that is carried out 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.

The mobile app is used to collect the 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 tests 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 done at the same time for all zones.

A duration test checks if the backup battery provides power for the required period of emergency operation which cannot be less than 60 minutes. It should be done separately in at least two groups of zones so 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 separately at intervals of one week.

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

One. You must define the zones so that there is only one emergency luminaire per zone. 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 so 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 will have an “Emergency” label.

1. In the Silvair mobile app, 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 carry out and tap “Start test”.

1. Open the Silvair mobile app.

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

3. Tap “Collect test results”.

4. Tap the area you want to collect test results from.

5. Move to the area to be able 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 test results they replace the previous results in the ELT report.

Only the current test results are shown in the ELT report. The previous test results are overwritten each time the results are collected.

You can view the ELT report in the Silvair web app. The report shows the area and zone where each device can be found. You can find the zone on the floor or site plan in the web app or mobile app.

No. However, we recommend that you have a device with a battery in the network to act as the source of time during a power outage. We also recommend that this device has an RTC to keep the time drift to a minimum and make sure that the scheduling is accurate. If there is no RTC, you can keep time drift to a minimum by periodically using the mobile app to sync the time between the mobile device and the mesh network.

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

One reason may be that the area does not include a timekeeping device with a fully charged battery so devices in the network do not know the correct time. To make sure that the tests are carried out 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 cannot 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.