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”.

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

No. The device name can be whatever you want.

The 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 mobile app is used on site to send the configuration created in the 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 the following criteria:

• will have a gateway,

• will have more than approximately 200 devices,

• at least some devices will be placed along a straight line,

• distances between devices will be large,

• daylight harvesting scenario will be used.

A project is a separate lighting installation created in the Silvair Commissioning tool. 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.

An area is a part of a project and is connected to other areas in a Bluetooth mesh network. A project can be divided into areas for better clarity and easier navigation. For example, it can be a room, a floor or a whole site, or a part of a floor, site, or building. All devices in each area must be in range of the Bluetooth mesh network. Areas can include a floor plan or a 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.

A zone is a part of an area that contains devices (luminaires, sensors, or switches) that have been commissioned using the Silvair mobile app and configured to operate according to the same settings (control profile). It can be a whole room or a part of it, or a separate space. All luminaires in the zone operate in the same way.

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 web app.

A control profile is a scenario with a set of settings that is 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 is a type of control profile which defines how the light behaves in that 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. Right-click a zone and select “Edit”.

3. Expand the “Profile” list and select “New profile”.

4. 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 JPG, 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 to act as a relay automatically by the Commissioning tool. A device can also be manually set 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 relays manually in these cases, see SN-213 Recommendations for complex lighting installations.

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

A device assigned as a static proxy always allows a Silvair mobile app to communicate with the mesh network.

A device assigned 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. It is configured automatically and handled in the background by the mobile app and the devices themselves.

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 sends the data packets received from the EnOcean switch into the mesh network and is set up as the adapter using the Silvair mobile app.

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

Do not use a device as an EnOcean adapter and as a relay or static proxy at the same time. 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 energy monitoring does not differentiate between power outages or devices being off. In such cases the result is calculated as a linear interpolation from the last data point before the failure to the first one after the failure.

Currently there is no mechanism to store data to the non-volatile memory, so the data is lost on power failure.

Yes, if the internet connection is lost the gateway can store the captured data (up to the size of available non-volatile memory) provided the gateway does not lose power or is not rebooted (see #Q2).

Scheduling requires a Silvair gateway to be added to the project. Additionally, scheduling only works with the “Multiple Scenes” Scenario. Please see SN-201 - Scheduling.pdf for additional information.

INS is a scheduling service that allows users to set up events that trigger predefined scenes at desired times. Contrary to gateway-based scheduling, it does not require a gateway device or Internet connection. Other notable functional differences include the following:

• INS does not support astronomical clock (events based on sunrise and sunset)

• INS is exposed to a slight time drift. In installations that include an RTC (real-time clock) node, the worst-case scenario is ~30 seconds per month. In installations without RTC, the maximum time drift increases to ~2 minutes per month.

• With gateway-based scheduling, users can adjust schedules remotely if needed. With INS, all adjustments need to be performed on-site via the mobile app.

For every zone, you can configure up to 16 time events and 4 scenes triggered by those events.

Yes, schedules can be temporarily overridden by users via manual control. If this happens, the luminaires automatically return to their schedule when the next scheduled event is triggered.

Not yet, but this feature is on our roadmap. Until released, the time needs to be synchronized using the mobile app whenever DST begins or ends within the time zone relevant for the project.

An RTC node is a dedicated piece of hardware with a real-time clock chip and, preferably, extended battery life which keeps the time running even when the power supply is off.

The main goal of the RTC hardware is to minimize the gradual time drift and thus ensure the high precision of the scheduling service. If the RTC device includes battery backup (most of them do), it also allows automatic time synchronization in the event of a network-wide power outage.

No. Installations using INS are recommended to include an RTC node for optimal performance. However, this is not a mandatory requirement as the mobile app can always be used for time synchronization (e.g. after a power outage, to adjust for DST, or to offset the time drift).

One is enough. Only one device can perform the role of the so-called Time Authority for the entire project at a given time. Therefore, adding multiple RTCs will not produce any benefits in terms of scheduling precision. A general requirement for Bluetooth mesh lighting control systems is that communication is maintained at all times between different zones and areas, allowing each device to communicate with any other device in the network. As long as this requirement is met, a single RTC device will effectively handle time synchronization across the entire project. If project-level communication is not provided, both the scheduling service and other lighting control features might not perform as expected.

The app does not have a feature enabling detection of devices with battery backup.

Yes, this will happen automatically as long as there is a relay node within its zone. Information about relay nodes can be found i.a. in the commissioning report.

The current time is automatically injected from the mobile app to the network during the INS configuration/commissioning process. What happens next depends on whether the network includes an RTC node. If it does, the RTC takes care of ongoing time synchronization, ensuring minimum time drift and high scheduling precision. If RTC is not available, time management happens within network nodes and the expected time drift slightly increases. In both cases, the mobile app can be used to offset any time drift that has already occurred.

No. If only a group of nodes is powered down, their internal clocks will be automatically synchronized with the remaining nodes as soon as the power supply is restored. This automatic time recovery procedure might not work in some very rare edge cases - so it’s recommended to verify whether scheduling works properly after a power outage takes place. If it doesn’t, the mobile app must be used to synchronize the time.

This depends on whether the network includes a battery-powered node. This could be an RTC device (most of RTCs include a battery) or any other node with battery backup. In case of a network-wide power outage, a battery-powered node will automatically share its internal clock with the entire network as soon as the power supply is restored. This procedure might not work in the event of some particularly long power outages (longer than ~24 hours). When a power outage lasts longer than the RTC’s battery capacity, the mobile app will have to be used for time synchronization.

If the installation doesn’t include any nodes with battery backup, a network-wide power outage will result in time desynchronization. Once the power supply is restored, the mobile app will have to be used to inject the current time into the network. This is a simple operation requiring the user to click a relevant button in the app, but it needs to be carried out on-site. If the time is not synchronized following a power outage, INS schedules won’t be implemented.

In the case of practically foreseeable power outages, time drift will not be affected. Theoretically, it might increase slightly in a network with a non-typical node layout that suffers very frequent power outages, but this is an extremely rare edge-case scenario that we do not expect to come up in commercial implementations.

Currently, there is no such possibility. The app automatically assigns the Time Authority role to a node that is best suited for it (in terms of timekeeping precision and/or battery backup).

A node performing the Time Authority role is the node that determines the time for the entire network. If the network includes an RTC device, such a device will automatically be selected as a Time Authority.

No, there is no automatic time synchronization between the mobile app and the Time Authority device. Time can be injected into the network in the following three cases:

• when the Time Authority role is being assigned

• when the project’s timezone is changed and Time Authority reconfiguration takes place as a result

• when the user manually requests time synchronization by pressing the Sync time button in the mobile app

Yes, existing installations based on older FW versions can be easily updated to enable INS as long as OTAU has been made available for devices used in the project.

1. Update the firmware of all your devices via over-the-air update (OTAU)

2. Remove all devices from the project.

3. Add devices back to your project.

Once these steps are performed, you can start setting up your schedules.

Yes, INS will work just fine in such projects as long as all nodes are updated to FW 2.20.2+. In-node scheduling can be implemented independently of gateway-based scheduling.

Currently, in-node scheduling does not support the Photocell scenario and cannot trigger Photocell behavior.

We strongly recommend that each node is updated before the INS feature is used. Even a single node with older firmware can cause a number of problems. Not only will it fail to execute scheduling events, but it will also be unable to propagate time through the network or participate in the time recovery procedure. In certain cases, this might lead to time synchronization issues affecting also the nodes with the latest firmware.

It has to be 100%. Only full network-wide connectivity ensures the flawless performance of the in-node scheduling feature. In fact, maintaining 100% connectivity at the project level is strongly recommended for every mesh lighting control network, regardless of whether or not it uses the INS feature.

It is not possible to manually adjust the Time Authority setup via the app. Also, only one device can perform the Time Authority role for the entire network at a given time.

If the project includes only 1 area, you should perform a standard mesh quality test to verify whether 100% mesh connectivity is maintained across that zone. If there are multiple areas, you should perform the mesh quality test for each zone independently to make sure that 100% connectivity is maintained within every single zone. In addition, you can verify cross-area connectivity by launching the app in the area where the Time Authority node is located and, while still remaining in that location, testing at least one node from each other area. The location of the Time Authority node can be verified in the commissioning report. In the future, we plan to add a more convenient testing tool that will allow users to easily verify mesh quality at the project level.

Yes, the manual event will override the scheduled event in the linked zone.

Zone linking does not affect in-node scheduling in any way. Specified schedules will be executed independently for each of the zones.

Both will be triggered at the same time but one of them will instantly ‘overwrite’ the other. As a result, only one of these scenes will be visible in a given space. It cannot be precisely determined which scene will prevail as this is dependant on multiple factors. The user should make sure that such a conflict of schedules does not take place in a project configuration. In the future, we plan to introduce system warnings that will prevent this from happening.