Configuring controllers in Nebula Beta

Overview

To configure controllers in Salto Nebula, you need to use the Salto Nebula app.

When setting up controllers for the first time you can either:

1. Create controllers in Nebula web first, then configure them via the app. Or…

2. Use the app to create and configure the controllers.

The way you set up and configure controllers depends on your specific use case. In the majority of cases, and specifically in larger installations, you will set up controllers and their associated access points using Nebula web first. In smaller installations you may find you will use the app to create and configure the controllers.

In both cases, an installer, who is aware of the names and locations of the controllers, will go through the Salto installation setting up the physical devices, phone in hand.

You can also configure controllers before installing them on the doors.

For a situation where you're updating firmware or resetting already-configured controllers, see resetting devices or updating firmware.

Controllers in Nebula

Model	Description
BLUEnet Controller	The BLUEnet Controller is a specific type of wireless controller used in Nebula which is designed to be used where a larger more complex installation is not required. This model only supports one reader.

Select installation

Before configuring controllers, you need to ensure you're operating within the correct installation. This could be your office building, for example.

You can view which installations you have access to, or select one if you have access to multiple installations, using the top left menu selector of the app.

If you don't have access to manage installations, this screen is not available. See user roles and permissions for more details.

Start configuring

Navigate to the Devices section of the app.

The app uses Bluetooth Low Energy technology to connect to devices, so make sure you have Bluetooth enabled on your phone before starting to configure. You must also ensure you have a working internet connection on your phone. If you're using an Android phone with Android version 6.0 or above, you need to enable and give permissions to location services on your phone, if they're not already enabled. See error handling for more information.

• Press the Configure button. The app begins to look for devices.
• Hold your phone close to the reader that's connected to the controller you're configuring, and keep it close until the light comes on.
• The app then asks you if the light came on. If it did, select Yes to continue.

If no devices are found

The Bluetooth scanning process has a timeout of 10 seconds to look for and connect to a device. If the scanning process doesn't find any nearby devices after that period, a "No device found" alert is shown and you can retry the search. If no device is found and the light doesn't come on, try moving your phone closer to the controller's reader before retrying.

Select existing access point

On the Which device are you configuring? screen you'll see a list of access points which are pending configuration. This option will only display if there are previously created controllers with their associated access points.

The drop-down menu shows a list of names of access points which have been created already. You can then assign the physical controller device you're configuring to its corresponding access point in the list of names.

If there are more than 20 devices pending configuration, the list is not displayed and you need to search for the specific access points using the search function. If there are 20 or less devices pending configuration, the list is displayed and you can directly select one of those 20 or use the search function.

Create new access point

You can create a controller and its associated access point using the app with the same process you use to configure it. Once the controller is created and configured, it displays as an access point in Nebula web. This means that the system manager can find it when creating access rights for users.

When the app connects to a device in the previous step, you'll see the Or create a new device option. Selecting this will reveal the following fields:

• Name (required)
• Unit (will only display if there are units in the installation)
• Connection type (required)
• Parent device (only required if the controller is online. Can be a gateway.)
• Calendar (will only display if the installation contains 2 or more calendars)

Name

Use a coherent naming system when setting up access points so they can be found in the system and make sense in the context of their associated controllers. For example, "Car park barrier entrance".

You cannot have more than one access point with the same name in your installation.

 Unit

This is an optional field which will only display if there are units in the installation. For more information see the section on units.

Connection type

You can set up controllers to be either Online or Offline. For more information see connection type.

Parent device

If a controller is online then it needs a parent device, such as a gateway. This field only appears in the app if you choose Online in the Connection type field above. You need to set up parent devices first before configuring their controllers. See configuring devices for more information.

Calendar

You can add a calendar to an access point to define your organization's working calendar at the installation level. This field will only display if the installation contains 2 or more calendars. If the installation only has one calendar, that will be the one automatically set for the access point.

Note that you manage calendars in the web application, not in the app. For more information see the section on calendars.

Once you've entered this information select Create to continue the configuration process.

Firmware update

If the app detects that a new firmware version is available while you are configuring a controller, it automatically downloads the firmware to the controller during the configuration process. The app displays the message "Updating firmware" in this situation. If no new firmware is available then you won't see this message.

For more information about firmware, see updating firmware.

Finish configuring

Once the configuration process has finished, you'll see a notification like "Car park barrier entrance is ready". This means that the controller is now correctly configured and ready for use!

If this process fails due to a loss of connection it starts up again. Once the connection starts up again the process continues at the point from which it cut off.

When your controller is ready you can exit the device configuration process by selecting Finish.

Be aware that this process only adds the controller to your installation. To give users access to your installation, a system manager has to create the users and assign access rights to them in Nebula web.

Updating

You need to update offline controllers when a change has been made within the Nebula system which affects a device. The updating process is similar to configuring controllers because the software already knows which ones require an update.

Navigate to the Devices section of the app and select Configure. You should hold your phone close to the controller's reader.

The app automatically updates the controller with the information displaying a notification like "Car park barrier is ready" once the process has completed.

This process also automatically detects if a firmware update is required.