nLIGHT SensorView Lighting Control Software User Guide

nLIGHT SensorView Rindrambaiko fanaraha-maso jiro

fepetra arahana

System Architecture
- SensorView is installed on a single host workstation or server (provided by others) that resides on the same Ethernet LAN (or WAN) as one or more nLight ECLYPSETM or nLight Gateway devices. SensorView can also be configured to communicate directly with a single group of devices. The system architecture is shown in Figure 01.

System Architecture

nLight AIR Wireless Devices
nLight ECLYPSE and nLight AIR Adapter
SensorView Configuration and Monitoring Software
nMazava
Host PC or Server Provided by Others
nETHSW Local IP Network

System Requirements

Single-user / Commissioning Installation:
- Rafitra fikirakirana: Windows 10 or newer.
Multi-user Installation:
- Rafitra fikirakirana: Windows Server 2016, 2022, or 2025.
- Hardware Minimum Operating Specs:
- RAM: 8GB
- Kapila mafy: 20GB
- Browser: Firefox, Google Chrome, Microsoft Edge
- Supported Windows Versions (both 32 and 64 bit versions supported):
- Client Versions: 10, 11
- Server Versions: 2016, 2022, 2025
Pre-installation Software Components:
- .NET Framework (Available for download from Windows Updates web pejy)
- IIS (Internet Information Services): IIS 10 and later

Torolàlana fampiasana

To ensure proper installation of the SensorView logiciel, araho ireto dingana ireto:

SensorView System Requirements: Refer to the ‘Specifications’ section above for detailed hardware and software requirements.
Fametrahana mialoha: Ensure the following Windows software components are installed prior to SensorView fametrahana:
- .NET Framework
- IIS (Sampandraharaham-baovao amin'ny Internet)
FANAMARIHANA: If .NET/IIS are not installed prior to running the SensorView installer, the user will be automatically prompted to install these items during SensorView fametrahana.

SensorView Fametrahana: Ny SensorView application installer is downloaded from the Acuity Brands webtranokala:
https://fota.acuitynext.io/v1/updates/sensorview/stable/svsetup/installer/latest/SensorView_Setup.exe

FANAMARIHANA: Internet access is required during installation to download the latest available version of the SensorView software.

Connection to Gateway: A system controller, such as nLight ECLYPSE, uses Ethernet ports to communicate with the computer running the SensorView software. Please reference the Gateway Setup section under the Admin section for details on methods to connect to a system Gateway.

SensorView Torolàlana ho an'ny mpampiasa

1 amin'ny 51

3 amin'ny 51

SensorView TAPITRAview
SensorView is an intuitive and easy-to-use, web-based software that gives authorized users the ability to remotely configure and monitor nLight Wired and nLight AIR network luminaires and controlled devices. It provides a simple and quick setup tool for creating custom configuration profiles that can either be scheduled or run on demand. SensorView also can assist with system commissioning by indicating and reporting on sensor and controller settings in addition to displaying live device status.
SensorView is installed on a single host workstation or server (provided by others) that resides on the same Ethernet LAN (or WAN) as one or more nLight ECLYPSETM or nLight Gateway devices. SensorView can also be configured to communicate directly with a single group of devices. The system architecture is shown in Figure 01.
This document covers common configuration and management tasks that arise when setting up and maintaining the network over time, as well as step by step instructions for accomplishing a given task.

nLight AIR Wireless Devices

nLight ECLYPSE and nLight AIR Adapter

SensorView Configuration and Monitoring Software

nMazava

Host PC or Server Provided by Others
nETHSW Local IP Network

Sary 01: Architecture System

4 amin'ny 51

SensorView Fametrahana
To ensure proper installation of the SensorView logiciel, araho ireto dingana ireto:
1. SensorView System Requirements: Depending on the intended usage of SensorView, there are two sets of computer hardware/software requirements:
o Single-user / Commissioning Installation: Recommend Windows 10 or newer. o Multi-user Installation: Recommend Windows Server 2016, 2022, or 2025. o Hardware Minimum Operating Specs:
Ram: 8GB Hard Drive: 20GB Browser: Firefox, Google Chrome, Microsoft Edge Version of Windows supported (both 32 and 64 bit versions supported):
Client Versions: 10, 11 Server Versions: 2016, 2022, 2025
2. Pre-installation: The following Windows software components are required prior to SensorView fametrahana:
.NET Framework: Available for download (free) from Windows Updates web page IIS (Internet Information Services): IIS 10 and later
NOTE NOTE If .NET/IIS are not installed prior to running the SensorView installer, the user will be automatically prompted to install these items during SensorView fametrahana.
3. SensorView Installation: The SensorView application installer is downloaded from the Acuity Brands webtranokala:
https://fota.acuitynext.io/v1/updates/sensorview/stable/svsetup/installer/latest/SensorView_Setup.exe
NOTE Internet access is required during installation to download the latest available version of the SensorView software.
4. Connection to Gateway: A system controller, such as nLight ECLYPSE uses Ethernet ports to communicate with the computer running the SensorView software.
Please reference the Gateway Setup section under the Admin section for details on methods to connect to a system Gateway.
If assistance is required, please contact our technical support team at 800-535-2465 or nLight-Support@AcuityBrands.com.

5 amin'ny 51

Once installed, SensorView can be accessed several ways: from the Start menu, via a desktop shortcut, or by typing http://<Host Computer Name>/ SensorView ao anaty a web browser. Users must enter a valid User Name and Password to login to the SensorView (Figure 02). The default User Name for the application is “administrator” with the Password “admin”. Login will be blocked for fifteen minutes if a password is entered incorrectly 8 times successively.
After logging into the application using the default credentials, the default password will need to be changed to a unique password. New passwords must contain one capital letter, one number, and one special character. Accepted special characters include ! @ # $ % ^ &* { } – _ = ~ ‘ : ; < > , [ ].
The Users tab (Figure 03) allows for login credentials to be changed or new users to be created.

Figure 02: SensorView Hiditra

Figure 03: Users Tab Location
SensorView supports four different User Types, as noted in the following table:

Karazana mpampiasa
mpandrindra
Admin Basic Read-Only

Description
Administrators can access all the features in the application. The administrator user only features are listed below.
Add/Edit/Delete users Update the SensorView settings Update the devices’ firmware View log details View reports Configure and view ny plugins Export diagnostic archive Can view all system controllers
Admin users have the same privileges as the Administrator user type but only have access to gateways assigned by the Administrator User type.
The Basic user privilege allows user to view and update all the device related settings and status except the features that can be only accessed by administrator.
The Read-Only user can only view the device settings and status.

6 amin'ny 51

Login and User Management – cont’d
Clicking on the User tab will bring you to the User Accounts screen. From here, you can follow these steps to add or edit users:
1. Click on the drop-down that says administrator and choose the Add a user option (Figure 04).
Figure 04: Add a User

2. Fill in the fields under the User details section with the relevant information (Figure 05).

3. Choose the desired User Type from the drop down menu (Figure 06).

Figure 05: User Details

4. Select the devices from the device tree that a user should have visibility of. Devices must be selected for a user to be created.
5. Click the Save button to save the new user data (Figure 07).

Figure 06: User Type

7 amin'ny 51

Admin

The Admin Dashboard is accessed by pressing the Admin button on the top left of the SensorView window (Figure 08). This option allows the SensorView administrator the ability to update and configure the following settings, each of which will be explored further in this section:
Setup (Figure 09) gives access to the basic settings of SensorView, including Registration (required to receive firmware updates), Location, Gateway Password, Gateways, Mail Server, and Custom Greeting.
Databases (Figure 10) allows you to create and load full system backups, as well as the option to Import/Export system backups. Importing a database will update device tree information, device information including labels, settings, profiles, and other system information. It will also import users (basic, read-only, and admin) and their credentials/logins. The “administrator” account password will persist through a database import and will not be updated.

Figure 08: Accessing the Admin Dashboard Figure 09: Admin Dashboard – Setup Figure 10: Admin Dashboard – Databases

FloorPlan (Figure 11) is for importing floor plan packages, and for exporting edited floor plans.
ny Plugins (Figure 12) option allows you to start services for the nLight GreenScreen Monitor, nLight Virtual Wallpod Server, and the nLight Plugin Host Service.

Figure 11: Admin Dashboard – Floorplan Figure 12: Admin Dashboard – Plugins

Located to the far right of the screen on the Admin Dashboard bar, Reports (Figure 13) allows you to generate various reports about SensorView and the devices on the connected network.

8 amin'ny 51

Admin Dashboard – Setup
Administrators can update the following settings in this section:
fisoratana anarana
Registration is where you input your contact information and details about your site (Figure 14). SensorView must be registered with Acuity Brands to get software and firmware updates. The information captured in this section may appear on your diagnostic logs and reports that help the support team identify details about your site to help diagnose your system. An internet connection is required to save this setting.
Figure 14: Setup – Registration
Toerana
The location of each gateway connected to SensorView can be updated in the Location section (Figure 15). Users can edit the location in one of two ways, as follows. If the Edit Coordinates box is checked, users may input the location via the latitude and longitude boxes on the right. If the Edit Coordinates box is unchecked, then the location may be edited through the dropdown menus. The Save button present in the bottom right of the section allows the user to save the updated location. The location data helps SensorView maintain the date and time according to its time zone.

Figure 15: Setup – Location

9 amin'ny 51

Admin Dashboard – Setup – cont’d
Gateway Password
This feature enables authorized users to change the current system controller’s password (Figure 16). It prevents unauthorized users from using a different SensorView instance to modify the system and restricts direct configuration access to system controllers. The Save button writes the updated password to the system controller. The Gateway Password will be blank for new installations and should be updated to match the SensorView Password assigned to all corresponding nLight ECLYPSE controllers. The Gateway Password can be updated on an nLight ECLYPSE controller by logging into the controller’s web page (https://[ip address of controller]/login.html), accessing the nLight Explorer Tab, Selecting Settings, and Selecting the Reset button beside SensorView Password. Only alphanumeric characters are accepted.

vavahady

Figure 16: Setup – Gateway Password

All the gateways (controllers) present on the network where SensorView is connected will be automatically discovered and included in the Gateways section (Figure 17). Administrators can enter system controller IP addresses to discover the controllers. Controllers can be excluded from the Devices section by unchecking the Include box of the respective controller. A controller can be deleted from SensorView by clicking on the Delete button.
Unless excluded or deleted after discovery, controllers will be listed in the device tree of the Devices section. Associated group and port labels, global and local channels, and all channel labels will reflect what was most recently saved on the devices.

Figure 17: Setup – Gateways

10 amin'ny 51

Admin Dashboard – Setup – cont’d
RADIUS Server
SensorView supports RADIUS authentication for users in addition to local accounts. Required fields are flagged with asterisks, and valid RADIUS credentials must be entered before it can be enabled. Once enabled, all authentication and authorization will rely on a RADIUS server’s user database. SensorView’s local user database will no longer be referenced by SensorView (sary 18).
Figure 18: Setup – RADIUS Server

Mail server

This section is used to update the Mail Server settings. The Mail Server is used to send notification to an administrator if the Windows service fails to launch when GreenScreen starts (Figure 19).
Figure 19: Setup – Mail Server

11 amin'ny 51

Admin Dashboard – Setup – cont’d
Custom Greeting
This section is used to update the custom greeting, which appears at the login screen (Figure 20). The greetings will show on the Login screen, as either a header or footer greeting, or both (Figure 21).
Figure 20: Setup – Custom Greeting
Figure 21: Setup – Greeting Locations

12 amin'ny 51

Admin Dashboard – Databases
The device network information and all other related details will be stored in the Databases section. The database will be backed up automatically and saved daily. The backed-up database’s name contains the date and time so that the backup can be easily distinguished. Users can perform the following options on the database, as called out in Figure 22.
1

2 3
4
5 6
7
Figure 22: Databases Section
1. Backup List: All the backed-up databases will be displayed on this list. By selecting a database from the list, user can Backup, Erase, Restore, or Export the database as mentioned in below sections.
2. Backup: A backup of a database that has been created on an as-needed or as-desired basis. Administrators may backup the database at any time. To back up a database from the list, select the desired database, enter a name in the Backup name (optional) field, and click Backup.
3. Erase: A backed-up database from the list can be deleted by using Erase. Select the database and click on Erase button to delete it.
4. Restore: A backed-up database can be restored to SensorView using this option. SensorView will load all data from the selected database and user can perform the changes on it.
5. Import: SensorView supports the import of database files with the .svdb extension. When a database is imported, a backup copy is also retained automatically. The imported data will be displayed within SensorView, allowing users to review and analyze its contents. Importing a database will overwrite existing system data, including login credentials for all non-administrator users. However, the administrator account credentials (e.g., administrator/SomePassword) will remain unchanged.
6. Export: The backed-up databases can be exported and shared with other users. The exported file will be with the extension of *. svdb. The file will be present in the download location of the browser.
7. Clear: The data of the current SensorView database, including non-administrator user accounts/passwords/device tree data/etc., can be cleared using this option. The data will be cleared and database will be filled with newer data from the networked devices.

13 amin'ny 51

Admin Dashboard – FloorPlan
Ny SensorView nFloorPlan tool provides a simple and intuitive way to navigate and monitor an nLight Wired and/or nLight AIR lighting control system instead of traditional tree view display. To display the floor plan, the administrators must load the floor map packages. This section allows user to import or export the map packages.
Figure 23: FloorPlan
Contact us to have a layout produced for your nLight installation. Once a layout is produced and you have received the layout (.mvdb) file, it can be imported into SensorView by clicking the Import button (Figure 23), then browsing to and selecting the file.
Plugins
Eo ambanin'ny Plugins tab is the Services section, where each plugin is listed along with its current status, either Running or Stopped. Plugins can be stopped or started via the buttons to the right of the Status (Figure 24).

Sary 24: Plugins
GreenScreen polling rate controls the rate at which this plugin is being polled. Increasing the rate may allow for GreenScreen reporting points to increase but will result in additional network traffic. To change the polling rate, select a new rate, and click Save & Restart Service.

The nLight Plugin Host Service status (either running or stopped) is indicated in the last table of the section. Controlling the nLight Plugin Host Service requires system administrator credentials (not SensorView credentials). You may have to contact your local IT department to retrieve the proper set of credentials. Administrators can enter their credentials (Username, Password, and Domain) for the SensorView host machine and click Stop or Start.

14 amin'ny 51

Admin Dashboard – Reports
Located to the far right of the Admin Dashboard bar (Figure 25), Reports is linked directly to the current active SensorView database, authorized administrators can view detailed reports on the following:
Sary 25: Tatitra
Network Device Report: Creates a printable report containing basic information about the devices in the network and their basic properties, such as Label, Device ID, Firmware Version, Group, and parent Bridge.
Ohbfile, Scene, & Presets Report: Creates a printable report describing the configuration of all profiles, scenes, and presets currently in the system. Device Settings Report: Creates a printable report describing the default settings for all nLight devices in the system. Global/Local Channels Report: Creates a printable report listing all configured Global Channels along with the devices broadcasting and
tracking within them. Also listed is all Global Preset configurations saved to any Global Preset capable device. Discovery Report: Creates a printable report listing basic discovery statistics about gateways in the system. This is generally used for diagnostic
tanjona fotsiny

15 amin'ny 51

vaovao farany

This feature enables user to update SensorView and network devices’ firmware to the most recent versions. When this screen is accessed, SensorView’s firmware cache will be updated for all available devices, and the information will be displayed as shown below (Figure 26).

Figure 26: Updates
1. Device Tree: Devices with available updates will be displayed. As devices are selected, they will appear in the section indicated by callout 6. The devices will be updated to latest firmware upon click on Update Firmware button click after selecting it. The Gateway, Bridge, and XPA device will be displayed in the grid directly.

2. Update Firmware Button: Clicking the Update Firmware button writes the latest firmware to all selected devices. As the devices update, the status of the update will be captured through a bubble at the top of the screen as pointed out in Figure 26. The status of the write will be displayed on the Status column of the grid. The grid also contains the details of the device with current firmware version.

3. Software Updates: If a newer version of SensorView is available, it will be displayed in this section. Users can run the installer and follow the installation setups described in the Installation section to continue with updates.

4. Channel Information: If updates are available for SensorView, this section will identify the channel from which the updates can be downloaded.

5. Update Firmware Cache: This feature enables user to download or update a local cache of nLight Wired firmware, allowing for a network of devices to be updated without Internet access. Download Cache with Latest FW – Clicking this button will download the most recent firmware version of all nLight Wired device types, including device types that are not currently represented in the device tree. Older firmware files will not be downloaded. This download may take as long as 20 minutes to complete but is only recommended when a user wants to update their offline cache. This option is recommended for most users. Download Cache with All FW – Clicking this button will download all versions, old and new, of nLight Wired firmware for every device type, including device types that are not currently represented in the device tree. Due to the quantity of files ary file sizes, this download can take 30 minutes to complete and may take longer for slower Internet connection speeds. This option is recommended for field service technicians or for use when instructed by Acuity Brands Technical Support.

16 amin'ny 51

Updates – cont’d
6. Selected Device Updates: When devices are selected for a firmware update, they will appear in this section. Old and new firmware, update status, and completion status will be displayed in this section.
7. nLight AIR Devices FW Updates: If nLight AIR devices are present, a screen for updating each nLight AIR Adapter (nECYD NLTAIR) will be available along with options to update the entire nLight AIR network.
8. XPA Bridge Updates: XPoint Wireless devices will appear in this section. Devices are labeled using their IP address. Over the Air Discovery (OAD) options are available for any selected XPoint Wireless bridges.
9. Bridge and Gateway Updates: Bridge and system controller firmware can be updated by selecting devices from this section. nLight ECLYPSE firmware updates will not appear in this section. Firmware for an nLight ECLYPSE should be updated using the nLight ECLYPSE Web UI.

17 amin'ny 51

GreenScreen

Figure 27: GreenScreen
This section will detail how to setup SensorView to use the GreenScreen plug-in (Figure 27). This will entail installing and setting up a database (PostgreSQL), a driver to connect to the database, a DSN for the data source, initializing the database, starting GreenScreen, and configuring GreenScreen options in SensorView.
Fametrahana PostgreSQL
Ny fametrahana ny PostgreSQL amin'ny solosaina dia mitaky ny fampidinana sy ny fametrahana ny rindranasa, ny fametrahana ny angon-drakitra mba hanaiky fifandraisana lavitra, ary ny famerenana indray ny mpizara database.
PostgreSQL dia vokatra mitokana izay tazonina sy novolavolaina misaraka tanteraka amin'ny SensorView ary tsy misy ifandraisany amin'ny nLight, SensorSwitch, na Acuity Brands.
Ho an'ny ambiny amin'ity antontan-taratasy ity ny andian-teny "XY" dia manondro dikan-teny lehibe sy kely amin'ny dikan-tenin'ny PostgreSQL napetraka; ho exampny: 9.0.
GreenScreen is compatible with PostgreSQL version 10.1.
Fametrahana PostgreSQL
SensorView can use an existing PostgreSQL database or a dedicated one. Which option is most appropriate is at the discretion of the system owner. The most recent versions can be downloaded at: https://img.acuitybrands.com/general-site-storage/Private/Sensorview/postgresql-10.1-1-windows.exe for the relevant windows version, x86-64 (64 bit) or x86-32 (32-bit).
Super-User Creation Screen
The screen below (Figure 28) configures the default super-user account for PostgreSQL, take note of these credentials as those will be the default login account and password for all access to the PostgreSQL database.
FANAMARIHANA Ny tenimiafina dia tsy afaka mampiasa afa-tsy tarehintsoratra alfa-numerika (isa, litera kely ary lehibe) tsy misy tarehintsoratra manokana.

18 amin'ny 51

GreenScreen – Installing PostgreSQL – cont’d
Port Configuration Screen
The screen below (Figure 29) allows for configuration of the port that PostgreSQL will use for connections. Use whatever value is required by the system administrator.
NOTE SensorView and GreenScreen can be configured to use any port value.
Figure 29: GreenScreen Port Configuration
Advanced Options
The screen below (Figure 30) allows for configuration of the locale that PostgreSQL is operating in. The default is almost always sufficient. If the installation site has specific requirements, then select the most appropriate option from the drop down. This selection has minimal impact on GreenScreen operations and can typically be left as the default.

On the final screen, push Next to finish the installation of PostgreSQL onto the local computer.

Figure 30: GreenScreen Advanced Options

19 amin'ny 51

GreenScreen – Configuring PostgreSQL to Allow Remote Connections
Ity dingana ity dia ilaina raha tsy misy SensorView and the PostgreSQL database reside on separate computers. By default, PostgreSQL will not allow any remote connections; to change this, administrative access to the host machine for the database is required. To setup PostgreSQL to allow remote connections, go to the directory PostgreSQL was installed at (by default C:Program FilesPostgreSQL), from that folder open the file ao amin'ny X.Ydatapg_hba.conf; ITY file azo sokafana amin'ny notepad na tonian-dahatsoratra generic. Raha mila antontan-taratasy fanampiny momba ny fomba fanamboarana pg_hba.conf, sy ny fanontaniana rehetra, jereo ny:

Dikan'ny PostgreSQL 10.1

URL https://img.acuitybrands.com/general-site-storage/Private/Sensorview/postgresql-10.1-1-windows.exe

Ho an'ny dikan-drakitra rehetra, ampio ity andalana manaraka ity eo amin'ny farany ambany amin'ny file hamela ny fifandraisana lavitra REHETRA amin'ny angon-drakitra:

host all 0.0.0.0/0 md5

FANAMARIHANA Ny famelana ny fifandraisana rehetra dia loza mety hitranga amin'ny fiarovana izay tokony ho lanjain'ny tompon'ny rafitra.
Tehirizo ireo fanovana ary tapaho ny file. PostgreSQL will now accept remote connections from the configured host.

Restarting PostgreSQL
PostgreSQL must be restarted before the changes made to pg_hba.conf will take effect. If no changes were made to pg_hba.conf then this step is unnecessary. Go to Start Menu -> Control Panel -> System and Security -> Administrative Tools -> Services.
Firewall Setup
If the computer running PostgreSQL is a different from the computer running SensorView, then the firewall on the computer running PostgreSQL may need to be updated to allow for incoming connections on whichever port PostgreSQL was configured to listen on. This will vary depending on the firewall software in use.

20 amin'ny 51

Fametrahana mpamily PostgreSQL
Ho an'ny SensorView Mba hampifandraisana sy hifehezana ny angon-drakitra PostgreSQL dia tsy maintsy apetraka eo amin'ny milina mandeha Sensor ny mpamilyView. Install the following driver: https://img.acuitybrands.com/general-site-storage/Private/Sensorview/psqlodbc_10_03_0000-x64.zip After downloading, open the zip file and run psqlodbc.msi and install the driver.

DSN Configuration

DSNs provide a way to configure a datasource connection in a standard consistent way that can be used throughout the machine. A DSN must be configured to allow SensorView ary GreenScreen hifandray amin'ny angon-drakitra; izany dia tsy maintsy atao amin'ny milina mandeha SensorView. A DSN consists of a name, database, server, port, user, password, and SSL connection requirements. Locating the correct DSN configuration tool varies depending on the specific version of Windows and whether or not it is 64 bit.

To configure a DSN for all 64 bit variants of Windows go to Start Menu -> Run -> type C:WindowsSysWOW64odbcad32.exe and press Enter (Assuming Windows is installed to C:, otherwise substitute correct system path).

To configure a DSN for Windows 7 32bit/Windows 10 32bit go to Start Menu -> Control Panel -> System and Security -> Administrative Tools -> Data Sources (ODBC).

Once the Data Sources (ODBC) popup is open, select the tab System DSN, then press Add. Select a datasource from the list. The name of the driver will vary depending on what was installed, commonly for 32 bit the name will be “PostgreSQL Unicode,” this is the driver that was previously installed during PostgreSQL setup section. Select Finish and a form will appear with additional fields to fill out (Figure 32). Fill out the form with the following values:

Data Source Database Server Port User name Password SSL Mode

Anarana mahazatra ho an'ny DSN izay hapetraka ao amin'ny SensorView nLight_system_data Adiresy IP na anaran'ny mpampiantrano ny milina mandeha amin'ny mpizara PostgreSQL. (127.0.0.1 na localhost ho an'ny solosaina eo an-toerana) Port PostgreSQL dia natsangana mba handehanana (amin'ny alàlan'ny default 5432) Anaran'ny kaonty sy tenimiafina ho an'ny mpampiasa angon-drakitra (jereo ny Super User Creation)
Araka ny mety amin'ny angon-drakitra (efa kilema amin'ny alàlan'ny default)

Select Save.
NOTE The Data Source name value as this is the field that must be entered into SensorView taty aoriana.
NOTE Pressing the Test button will fail with ” database not found” until Configuring the Administrator Email has been completed.

Figure 32: GreenScreen ODBC Driver Setup

21 amin'ny 51

GreenScreen – Setting Up GreenScreen
In order to configure and run SensorView the plug-ins component must be installed. For new installs this can be accomplished by making sure that plug-ins is checked during the feature select portion of the SensorView install. For existing installations, run the installer and select Modify, then check plug-ins and push modify. Once the plug-in components have been installed, open SensorView and go to the Admin page and select Plugins.
Tefeo ny mailaka mpitantana (tsy voatery)
GreenScreen will notify the administrator via email if it encounters any issues while attempting to start. To configure email notification, the administrator’s use of SensorView must have an email address entered; additionally, the Mail Server section (found at Admin->Setup->Mail Server) must be filled out to allow for emails to be sent from SensorView. Ny mailaka fampandrenesana dia halefa raha tsy mahomby ny serivisy Windows mpampiantrano.
Fanombohana ny angon-drakitra

Once PostgreSQL, the database driver, and the system DSN have been set up and configured, the last step is to build the GreenScreen database and start the service. To create the database:
1. Open pgAdmin III.
2. Click the + sign by PostgreSQL under Servers (or you can double click on PostgreSQL).
3. Click the + sign by Databases (or you can double click Databases).
4. Right Click on postgres.
5. Click on New Object.
6. Click on New Database. Enter the name of the database you entered when you created the DSN (usually nLight_system_data).
7. Tsindrio OK.
Manomboka GreenScreen
Mba hanombohana GreenScreen, ny singa plug-in dia tsy maintsy efa napetraka teo aloha (Setting Up GreenScreen); raha tsy vita izany dia tsy hisy Plugins tabilao. Mankanesa any amin'ny efijery Admin ao amin'ny SensorView ary mifidiana Plugins (Figure 33). The host service should already be running; if it is not then the username, password, and domain (optional) must be filled out, then start the nLight Plugin Host Service. Once this is running GreenScreen can be started and stopped in the top window.

Figure 33: GreenScreen ODBC Database Setup

22 amin'ny 51

GreenScreen – Configuring GreenScreen Operations
Within the accordion select GreenScreen; on this page options can be set that will configure how GreenScreen will compute savings and what units to display them in (Figure 35).

Figure 35: GreenScreen Configuration
Display Options
SensorView azo amboarina hanehoana tahiry amin'ny dolara na kWh. Ho an'ny fitsitsiana CO2, ny karazana famokarana ho an'ny herinaratra dia azo ampiasaina hamaritana ny tahiry CO2.
Vidiny elektrika
SensorView can be configured with the building’s electrical rates. Set the rate and time periods in which the rate applies. These settings will only be used if SensorView dia natao hanehoana tahiry amin'ny dolara.
Vanim-potoana fototra
Mandritra ireo vanim-potoana ireo, SensorView will assume the building is occupied. Energy savings (whether in dollars or kWh) are relative to how much energy would have been spent, with all control points in the system being on for the duration of the baseline periods. Refer to the GreenScreen data sheet for a more detailed explanation of savings analysis.
Hit Save Settings to save the configuration.
Once SensorView has a valid Data Source which can connect to the database, it will display the current size of the database and the state of hosting service in the bottom left corner of the screen.

23 amin'ny 51

TAPITRAview
Ny Overview screen will be the default selection after the successful login of the user (Figure 36). The Overview screen will show the summary of the system.
1 2
3 4
Sary 36: Tapitraview Ecran
The summary includes the details noted below: 1. Recent Activity: Recent activities that have occurred in the networked devices, such as Firmware updates, will be displayed in this section. The information will be very high level. 2. Device Network: The available gateways and associated device’s count will be displayed in this section, including All Devices, Offline Devices, and Devices Mismatched (ones whose settings differ from SensorView’s records). 3. Updates: All available updates for connected devices will appear here. Users can navigate to the update screen from this section. 4. Resources: Documentation for the current SensorView version and for the devices on the nLight network can be accessed here.

24 amin'ny 51

fitaovana
On the SensorView Devices page, the user selects from the Device Tree. By default, these devices are listed in hierarchical order: gateways are parents of bridges, which are parents of groups, each of which contain sensors, switches, relays, dimmers, or other devices.
Device Tree Overview

Figure 37: Device Tree
The Device Tree Menu, available from the filter icon to the right of the search textbox, contains selection features that aid in the location/selection of devices (Figure 37). Three primary types of search features exist: Features, Profiles, and Device States (Figure 38).

Figure 38: Device Tree Menu
Features allows for selecting/searching of the tree based on predefined characteristics of the device, such as whether it has a relay or occupancy sensor; available options are: current-sensing, occupancy, daylighting, relay, dimming, switch, dimming-or-relay. Profiles locates or selects devices that are in a particular profile; this is useful when creating a new profile that operates on all the devices already in an existing profile. As profiles are added or removed from the system the contents of these selections will change. Device States allows for searching or selecting devices depending on their current state.
Find New Gateways (Figure 39) searches the local subnet for gateways that may not be reflected in the device tree.

25 amin'ny 51

Devices – Tree Layout
The layout of the SensorView device tree corresponds closely with the actual wiring of the devices, with a few notable exceptions:

Figure 40: Tree Layout 01

Figure 41: Tree Layout 02

Bridges are not nested within their parents (Figure 40).

Groups off a bridge are displayed in ascending alphabetical order (Figure 41).

Devices in a group are displayed in alphabetical order, not wiring order (Figure 42).

Figure 42: Tree Layout 03

Search/Filter/Locate Device

Ny SensorView tree allows for the user to select or search for devices based on a variety of parameters. The Device Tree Menu contains numerous options for

searching for (“finding”) devices based on predetermined characteristics (such as device state, or features the device has). The text field above the device tree

also allows for free text search over the devices (Figure 43). A user can type any value into the field and the tree will automatically begin filtering to display

devices with label(s), model(s), or device ID(s) matching the entered value(s).

There are two primary ways to quickly locate a device: use the

device Search, or the Prebuilt Filters.

1. Device Search: Allows a user to immediately begin

typing to search for the device (over device ID, model, or

custom label).

2. Prebuilt Filters: Allows for a user to search for a device based on: Features: Current-sensing, dimming-or-relay, occupancy, photocell, relay, switch, wireless Profiles: Select by Profile name Device States: Error, normal, offline, warning
Figure 43: Search Devices
Note that any device matched and displayed will automatically cause the parent group, bridge, and gateway to be displayed. When operating in MultiSelect (link) mode, clicking on the parent nodes will select all the currently visible child nodes, and will omit the ones that have been filtered out.

26 amin'ny 51

Fitaovana – View Device Properties and State
For any device selected from the Device Tree (left), SensorView displays data in real time by selecting one of the available tabs: Properties, Current Settings, Default Settings, and Status. Figure 44 shows the readings from one of the nLight Ceiling-Mount, Passive Dual-Technology sensors covering approximately an area of 9 meters in diameter (nCM PDT 9) in the Group called “Port 6,” which has been selected from the device tree menu.

Figure 44: Device Properties
There are 5 possible states that an nLight device can be in. These different states generally indicate some sort of operational problem with a device. Offline: The device is no longer online, check that the device is properly connected. Bootstrap: The device failed a firmware update and is in bootloader mode. Any relay or dimming output will be toggled on, but the device will not respond to any operational changes. Update the device to resolve this. Misread: Some properties of the device were not read by the gateway. To resolve state, go to the device and select Rediscover or use Network Management -> Rediscover Incompatible: SensorView is not compatible with this device and is unable to configure it. Upgrade the device to resolve this. Mismatched: SensorView has detected that the device settings do not match what is expected. Synchronize the device (either using SensorView or the device’s settings) to resolve. Choosing to synchronize from a device will update SensorView’s record of device settings. Choosing to update from SensorView will update a device’s settings to match SensorView’s record.

FANAMARIHANA
Device State is not the same as Device Status. Individual device types can have various status conditions, depending on their functions.
Under the product image of your selected device (Figure 44) are a number of options. Note that some options pertain only to certain types of devices and do not appear otherwise:
Avereno ny firafitry ny orinasa
Resets the device to its default factory settings.

Rediscover

Reprompt SensorView to poll the selected device.

100 Hour Burn In

Overrides relay on and/or dimming output to full bright (typically used for lamp seasoning).

Download Screen Saver

Download the current background screen image from the selected device.

Alefaso ny Screen Saver

Upload a screen image to the selected device. nPOD TOUCH Supported file formats: JPG, PNG, GIF, BMP, TIF Optimal resolution: 320×240 16bit color. nTS Supported file format: JPG (Baseline encoding) Optimal resolution: 1024 x 600″

Figure 45: Device Options

27 amin'ny 51

Fitaovana – View Device Properties – cont’d
Other information found on the Properties tab includes the following. Note that some items on Properties pertain only to certain types of devices and do not appear otherwise:
Basic Info
ID: An unique ID assigned to the device. Firmware Version: Indicates the firmware currently installed and running on the device. If this number does not match information in the
TAPITRAview screen under “Updates,” it may be time for a firmware update. Label: A label can be customized to describe and represent the device. Labels are automatically generated for nLight AIR devices using the
CLAIRITYTM+ mobile application. nLight Wired devices will have a blank label field until updated by the user. Information in this field is utilized for BACnet labeling. I.e., an output device will generate a BACnet object with the formatting [Label]_[BACnet Property Type]_[Device ID]. Notes: (optional) Comments on this device or the area it serves. Load: (in Watts) Shows and/or sets the load on the selected device or devices within the selected group; used with GreenScreen. Only applicable to devices containing relays or nIO LEDs. Update Historical Load Data: This indicates whether to change the load for data points previously collected for GreenScreen (when checked) or leave old load values unaltered (unchecked). Only applicable to devices containing relays or nIO LEDS.
Efa tapitra ny fitaovanaview
Fehiny fohyview of the selected device, its unique ID, and its general status. Identify: Causes the device LED to flash, helping to identify the physical device in the space.
Copy Programming
Copy programming to the selected device from another existing device.
Advanced Details
Date Code: Indicates the internal lot number for the device. Parent Device: The name of the device above the selected group in the network hierarchy. Group: The name of the group in which the selected device resides. Network Depth: The number of steps below a gateway in the network hierarchy.
FAHASALAMANA
This section provides diagnostics read-outs for nLight Engineers and Field Techs.
Fikirana ankehitriny
The Current Settings option (Figure 46) allows the administrators to see the current settings for the selected device, and make changes there via drop down menus. Once changes are made, use the Apply Settings button to push the changes to the device, or Revert to Defaults to set the device back to the defaults set in the Default Settings option.

28 amin'ny 51

Devices – Default Settings
The Default Settings option (Figure 47) allows the administrators to change and apply the default settings for a device. Once changes are made, use the Save Defaults button to save the changes to the “Default” settings collection, or use the Save Defaults and Apply Now button to save the settings, update settings that appear under Current Settings, and affect active settings on the device.
Figure 47: Device Default Settings
For detailed information on what settings affect, hover over a setting, and a description of that setting will appear in the lower left corner of the screen.
Wallpods
The Wallpods page is where users adjust what switch options appear on an nPOD GFX, nPOD TOUCH, and nTS (Figure 48). Users can define how a switch will appear (as dimming capable or only on/off), and they can optionally choose for the switch to appear under the Shades/Blind screen (applies to an nPOD TOUCH).

sary

Figure 48: Wallpods

The Scenes page is where users adjust what scene options affect an nPOD GFX, nPOD TOUCH, and nTS (Figure 49).

29 amin'ny 51

Homescreen
The Homescreen page is where users configure the blocks of each controls page of an nTS. Each block can be configured with an already-created wallpod or up to three (3) already-created scenes (Figure 50).

Figure 50: Homescreen
Devices – Status
The Status page (Figure 51) displays the present state of any device selected in the left tree menu. Device types have different functions. The status pages display parameters specific to the type of device selected, indicated by icons easily seen at glance. The current state of the device for each parameter (icon) is also displayed in readable text, which may include additional information on the particular status of the parameter within the selected device. For a complete guide to Status Icons or possible conditions for a given device parameter, visit the Status Icon Glossary.
Figure 51: Device Status

30 amin'ny 51

Driver Mapping
The Driver Mapping page is visible when configuring nPS 80 DALI device(s), and displays discovered drivers. Use the Zone drop-down to assign each driver to virtual zones 1 through 16 (Figure 52).
Figure 52: Events
ZAVA-NITRANGA
When selecting a system controller (nLight ECLYPSE or Gateway), the Events button will be visible (Figure 53). Selecting the Events button will display all gateway captured records over a user-selected time period (24 hours, 7 days, 30 days, or all records). The resulting list of events can be sorted by errors, warnings, or “other.” Lastly, the cause for the event can be filtered as well.
Figure 53: Events
AIR Site Survey
The AIR Site Survey screen (Figure 54) is visible only by selecting an nLight AIR Adapter (nECYD NLTAIR G2). This screen is used to view if a device is serving as a Repeater, device Daughter Count, and device Hop Layer. Repeater status will reflect a “Yes” or “No” depending on if the device is presently serving as a repeater. Daughter Count indicates the number of devices that connect downstream of the device, bridged to the nECY and nECYD using Autonomous Bridging Technology. Hop Layer indicates what layer of the wireless network a device is on. A device within the initial broadcast range of an nECYD will be on hop layer 1, whereas if the device must connect to the nECYD through one or more repeater-capable devices, the device will appear on hop layer 2 or greater. A device on the third hop layer would only be able to connect to an nECY and nECYD through repeated messages by two devices in series. Hop Layer 15 symbolizes that SensorView cannot communicate with a device. This status often appears if a device falls offline or has been removed prior to SensorView having synchronized with an nLight ECLYPSE.

31 amin'ny 51

Preset Scenes
Preset scenes, both global and local, are used to set output devices to a static light level when triggered. Most scene-capable devices are able to trigger a preset scene. When triggered, a preset scene is sent to tracking devices as a broadcast, which results in very fast response by end devices.
A local preset scene that is triggered by an nLight Wired device is used to adjust the light level of all or some directly connected output devices. Devices must be on the same daisy-chain or connected to the same nBRG 8 port to be affected by a preset scene local that is triggered by a Wired device.
A local preset scene that is triggered by an nLight AIR device is used to adjust the light level of all AIR devices in the same group. Devices must be in the same group to be affected by a local preset scene that is triggered by an AIR device.
A global preset scene can be used to trigger the light level of any device(s) connected to an nLight system. Broadcasting and tracking devices must be configured under the same global channel prior to a global preset scene being available. Global channels require connection to an nLight ECLYPSE.

32 amin'ny 51

Control Channels
nLight devices exchange control information via the use of Local and Global channels, accessed via the Control Channels tab (Figure 55). Communication performed within a group (single nBRG port) is dictated via Local Channels; while Global Channels allow a device to receive input from any other device on the nLight network.
SensorView allows users to modify both Local and Global Channels to configure the control they need. Local Channels are commonly used to subdivide a single Group and allow for switches to control individual fixtures or switch legs within a Group, rather than all of them. Global Channels are more commonly used to provide control over multiple spaces via a single input device.
Channels, both Global and Local, can be used to fine tune the control that one devices has over others, for Occupancy, Switching, and Daylighting.

Figure 55: Control Channels
Channels eo an-toerana
The Local Channels option (Figure 56) allows a user to specify the channeling for all devices in the selected group. Users can configure Switching, Occupancy, and Photocell channels on a single screen.
Devices tracking a particular channel will respond to commands sent by any device broadcasting on that channel. To configure one device to control another simply set the broadcasting and tracking numbers for the devices to the same number. The column on the left indicates broadcasting devices assigned to channels, and the column on the right indicates tracking devices assigned to channels.

Figure 56: Control Channels – Local Channels
To configure a local channel (Figure 57): 1. Select a group from the Device Tree. 2. Add channels via the New Channel button. 3. Turn existing channels Off or On. 4. Add devices to the broadcasting devices. 5. Add devices to the tracking. 6. Once a field is selected, the device tree will indicate a list of devices that could be added to that field, via checkbox. 7. When all changes have been made, click Save.

Figure 57: Control Channels Add Devices Acuity Brands | One Lithonia Way Conyers, GA 30012 Phone: 800.535.2465 www.acuitybrands.com 2026 Acuity Brands Lighting, Inc. All rights reserved. Rev. 03/25/2026

33 amin'ny 51

Control Channels – Global Channels
With traditional wired nLight systems, devices within a group communicate occupancy, photocell, and switch events over local channels. With Global Channels, communication of this information is possible between spaces as well. This provides enhanced design flexibility for applications requiring master control.
General Information: Switch, occupancy, and photocell (inhibit and automatic dimming) global channels are available for spaces connected to a single nLight ECLYPSE. Switch, occupancy, and inhibit photocell global channels are available between nLight ECLYPSE controllers. Automatic dimming via photocell for daylight harvesting is not available for devices connected to separate nLight ECLYPSE controllers. If daylight harvesting is required, both the broadcasting photocell and receiving output devices must be connected to the same nLight ECLYPSE. Global channels can only be configured through SensorView and cannot be configured using an nCOMKIT nor nConfig. Communication between Wired and AIR devices is available using global channels. A maximum of 128 global channels are available per nLight ECLYPSE. Global channels that span multiple ECLYPSE controllers will consume one channel on each nLight ECLYPSE whose device(s) are broadcasting or tracking on the channel.
To configure a global channel (Figure 58): 1. Under the Channels tab, select the Global Channels option. Any Global Channels that have been previously assigned will be displayed. 2. Select Switch, Occupancy, or Photocell to display all global channels in the respective category. 3. New channels can be added by clicking the New Channel button while viewing a relevant category. 4. Add devices to either the broadcasting or tracking fields by selecting the tracker or broadcaster box and selecting devices respectively from the device tree. The device tree will filter to show devices that can be added to the box selected. If the device you want to add to a box is not shown, verify you have selected the appropriate box and the appropriate device category. 5. Once a field is selected, the device tree will indicate a list of devices that could be added to that field, via checkbox. Devices can be added to more than one channel if desired. 6. To delete a channel, click the red circled X at the far right of the channel. 7. When all changes have been made, click Save. 8. Once saved, channels can be tested by clicking the Off and On buttons.
Figure 58: Control Channels – Global

34 amin'ny 51

Fitantanana tambajotra
The Network Management tab is where default settings can be modified for many devices at once.
Fikirana
From the Settings option (Figure 59), start by selecting devices from the Device Tree.
Figure 59: Network Management – Settings
Users may select multiple devices at once. When operating in this tab, all line items displayed in the tree will be given a checkbox which will allow for selection (Figure 60). Single clicking on a device no longer displays information specific to the device, but rather selects/deselects it. This mode of selection is used when large amounts of devices are to be operated on simultaneously. Selecting a device within a group only selects/deselects that device. Selecting a group, bridge, or gateway selects/deselects children; this allows for a user to quickly select all devices in a group, bridge, or gateway (Figure 61). The user may also deselect individual devices from a group, bridge, or gateway (Figure 62).

Figure 60: Network Management MultiSelect

Figure 61: Network Management – Select All Devices

Figure 62: Network Management – Deselect Devices

With a device or devices selected, the user may now click the drop-down list next to Add a Setting. The list of settings available depends on the devices selected. Add one or more settings, then select the desired value(s) for those settings before choosing Save (see below). Settings on multiple devices can be adjusted from this screen by selecting devices from the tree, and when updates are made, only the devices selected are affected. Settings that can be adjusted include settings such as Basic (PIR sensitivity, override, occupancy time delay), Dimming (follow photocell mode, occupied bright level, unoccupied dim level), Broadcasting, Tracking, ADR, and Global Broadcasting and Tracking. The other choices beneath the Settings option include:

afa-tsy

Defaults and Apply Now: This saves your settings as a default and immediately applies them to the selected devices, as applicable. Defaults Only: Saves the settings as defaults but does not push them immediately to the devices selected.

hiverina
To Custom Defaults: Reverts the settings of the selected devices to the user defined custom values. To Factory Settings: Reverts the settings of the selected devices to factory default settings.

mampifanaraka
The synchronize button allows users the ability to synchronize settings on multiple devices with SensorView or to synchronize SensorView settings to match the devices.

Rediscover Devices
Rediscover devices causes SensorView to search for devices per what has been selected in the device tree.

35 amin'ny 51

Network Management – Group Copy
The Group Copy option (Figure 63) allows the user to copy settings, scenes, profiles, and loads to devices from a source group over to the destination group. Drag devices in the destination group to change the mapping. When devices are mapped appropriately, click Copy.

entana

Figure 63: Network Management – Group Copy

Output capable devices have a field for Load, which represents the power of the fixture(s) they are controlling. The Loads option (Figure 64) allows a user to select devices to modify and write a value to the Load field on those devices. Click Save to apply the changes made. Click Set Baselines to make the new setting the baseline for that device (this will cause the relay to toggle on and off). Lastly, check the box to Update GreenScreen Historical Data to ensure that changes made are recorded in the GreenScreen reports.

Figure 64: Network Management – Loads

The Fixtures option (Figure 65) allows for a user to adjust the icon that appears for the device when under Map view. Users can select from fixture manufacturer types Lithonia, Peerless, and Holophane. A selection of fixture-specific icons appear under each ofthe manufacturers. Select A Manufacturer via drop down, then Select A Fixture from the following list. When you are done, click Save Fixtures.

Screen Savers

Figure 65: Network Management – Fixtures

Screen Savers for nPOD GFX and nPOD TOUCH devices can be uploaded from this screen. Upload a screen image to the selected device using the Upload Screen Saver button. Optimal resolution is suggested to be 320 x 240 16bit color. Accepted file formats include JPG, PNG, GIF, BMP, and TIF.

Export Diagnostics

The Export Diagnostics screen is used to create a zip file with system-pertinent information required for both history and troubleshooting purposes. The file includes information on gateway health and diagnostic information, error logs, a SensorView database export, and a SensorView Map Builder export. Clear Health is used to reset all counters for selected devices to 0. Only devices that are selected using the tree view are affected. In the Description field, users can enter notes or text, and all entered information will appear in their Diagnostic Export as a .txt file. An option to Include Health Statistics of devices is found below Description. This option is enabled by default, and when left enabled, the created diagnostic file will include a variety of logs (including the Audit Log) and .xlsv with information relating to devices and their corresponding health statistic counts.

36 amin'ny 51

Ohbfiles
Ny Profiles tab (Figure 66) is where control modes and settings for a particular group are selected. A schedule (complete with a recurrence pattern) and priority are also chosen on this page. The tab has three configuration panels: Profiles, Settings, and Scheduler. Profiles exist in both local and global forms. Global Profiles are created and edited via the Profiles tab, and a user can create up to 2048 Global Profiles per system. Local profiles are created and edited via the Devices tab by modifying settings on broadcasting devices, such as scene switches.

Sary 66: Profiles Tab
Global Profiles are stored in the database and the Gateway, which administers profiles according to priorities. The profiles can also be activated on demand via SensorView, an nGWY2 GFX, or via a scene switch that is connected to a network of nLight devices. When activated, global profiles execute in unicast, writing to all applicable devices.
Local profiles are stored in broadcasting devices (Figure 67). The profiles are activated by triggering the broadcasting device, and when activated, local profiles execute in unicast, writing to all selected devices on the same nBRG 8 port or daisy-chain.
To configure a global profile:
1. Click New under the Profiles panel (Figure 68) to start creating a new profile or click the name of a profile in the list to edit an existing profile.
2. In the Settings panel to the right of the Profiles panel, users will be prompted to select the devices affected by this profile and to create a name for the profile (Figure 69). When you are finished making changes to the profile, click the Save or Save As Copy button.
3. Add or remove devices using the checkboxes in the Device Tree on the left (Figure 70). Checked devices can participate in the profile and receive applicable settings while the profile mihazakazaka.

Figure 67: Local Profiles Figure 68: New Profiles Figure 69: Name Profile Figure 70: Select Devices

37 amin'ny 51

Ohbfiles – cont’d

4. Select the desired settings for the selected devices via the Add a Setting drop down menu (Figure 71). Multiple settings can be added to the profile and will affect the applicable selected devices.

5. Create a new schedule on the Scheduler panel, or select an existing schedule from the drop down menu (Figure 72). The Scheduler allows the following options:
Schedule date/hour/minute for any setting change or control mode
Astronomical start/end dates include +/-180 minute deviance from Sunrise/Sunset
Set daily/weekly/monthly/yearly recurrences; drilldown options provide more detailed patterns
Unlike other systems which allow scheduling of lights on/off or on-demand dimming scene control, nLight provides users with the ability to schedule changes to almost any operational parameter. This allows for dynamic sequences of operation that can be tailored to a space across different times of day and/or dates.

Figure 71: Select Settings Figure 72: Create Schedule

6. Users can change the priority status of profiles on the Priority tab (Figure 73), which allows devices in multiple profiles to react based on the priority of said profiles. Select the priority of the profile to change, then use the arrows to move to the appropriate position, or down into the disabled area.

Figure 73: Set Profile ZAVA-DEHIBE INDRINDRA

38 amin'ny 51

fandaharam-potoana
Figure 74: Schedules
The Schedules tab (Figure 74) shows all scheduled profiles for zones and devices in the nLight network, on a 24-hour schedule for a given date.
Hovering over a profile name displays the profile’s begin and end times. Clicking the profile name is a shortcut to editing that profile on the Profiles tab. When a zone is expanded, individual schedule bars for the zone’s devices are generated. These bars are colored to denote a specific profile. Clicking the header with the time markings will bring up a date picker for quick viewing of a future date.
If two profiles are scheduled at the same time, the one with the higher priority (per the Profiles tab section) takes precedence. The below holidays are available for selection or exclusion when creating schedules.
New Year’s Day MLK, Jr. Day George Washington’s Birthday Memorial Day Independence Day Labor Day Columbus Day Veterans Day Thanksgiving Day Christmas Day Boxing Day New Year’s Eve

39 amin'ny 51

CLAIRITY Link Transporter
The CLAIRITY Link transporter encrypts information exchange between authenticated users and the CLAIRITY Link portal. This software is available for optional installation when installing SensorView versions 15.3 and later. Using this software, factory authorized representatives are able to access a site with an active connectivity plan remotely using the CLAIRITY Link portal.
Running the CLAIRITY Link Transporter
The below are steps to run the CLAIRITY Link transporter. An active Internet connection is needed for the transporter to authenticate with the CLAIRITY Link cloud. 1. Run the CLAIRITY Link transporter application. You will see a message like the below when the application starts.
2. Open the system tray (collapsed list of programs on the right-hand side of the taskbar).
3. Right click on the CLAIRITY Link icon and select “Sign In…”

40 amin'ny 51

Running the CLAIRITY Link Transporter – cont’d
4. If users have an existing CLAIRITY+ or SensorSwitch VLP account, their login can be used to sign into the CLAIRITY Link transporter. Otherwise, new users will need to click “Sign up now”.
5. Multi-factor authentication is required to log in after a valid username and password are provided. Users will be sent a verification code to their email address. Once the verification code is confirmed, the page will update and display the below confirmation message.
6. With the CLAIRITY Link transporter successfully running, authorized users can log into the CLAIRITY Link portal using their portal credentials and interact with the CLAIRITY Link routers and their downstream devices.

41 amin'ny 51

SensorView Audit Logs
SensorView versions 15.4 and later include audit logging capabilities, capturing data that includes timestamps, actions taken, and the user account associated with the actions. Discovery of gateways, settings updates, synchronization of SensorView banky angona files, importing of SensorView banky angona files, profile creation, and any other action that results from a button click in SensorView is automatically logged. See the below for an example log.
Audit logging information can be found in the Acuity BrandsSensorViewLogsSensorViewAudit folder. If installed in the default location, the full file path is C:Program Files (x86)Acuity BrandsSensorViewLogsSensorViewAudit. Each log file includes data for each action taken during SensorView sessions on a particular day. Message logs persist for 180 days, and files older than 180 days are replaced with new files when SensorView is next accessed.

42 amin'ny 51

SensorView Anarana iombonana
The following is a glossary of terms used in SensorView.

100 Hour Burn In Active Screen Brightness ADC Photocell On/Off Auto Set-Point Automated Demand Response Automated Demand Response Low Level Automated Demand Response Max Level Automated Demand Response Medium Level BLE Output Power Blink Warning Button Action Button Enabled
Cloud Detection
Color Number Color Number Switch Tracking Color Temperature Global Switch Tracking Color Temperature Percent Color Temperature Switch Tracking Contrast Level Custom Color 100% Custom Color 93% Custom Color 94% Custom Color 95% Custom Color 96% Custom Color 97% Custom Color 98% Custom Color 99% Deadband External Photocell Dim When Held Dimming Always On Dimming Curve Dimming Level Driver Group Dual Zone Off-Point
Dual Zone Offset
DZ Photocell Mode Fade Off Time

Overrides relay on and/or dimming output to full bright for one hundred hours. Specifies the brightness of the backlight when device is in use. Turn the lights on or off if dimming is insufficient to meet photocell Set-Point requirements. Photocell calibration procedure for detecting optimum lighting control level. Enable/Disable load shedding. Dim Level to use as upper limit when in load shedding mode. Dim Level to use as upper limit when in load shedding mode. Dim Level to use as upper limit when in load shedding mode. The BLE radio output power in dBm. Enables a blink warning for the output to toggle five minutes before it turns off. Defines what action a button press performs. Specifies whether or not the button is currently disabled / inactive. When enabled extends transition time from daylight harvesting to reduce on/off transitions when ambient light level is rapidly changing. Sets the active color for the color cell. If enabled, the luminaire will ignore Color Number commands. Indicates whether color temperature will track global switch channels. The color temperature of a tunable white fixture as it relates to wall switch dim level percentage. Indicates whether a device’s color temperature output will react to manual switching and/or dimmer events. Sets the grayscale Contrast Level for the luminaire. Sets a user-defined color for Custom Color 100. Sets a user-defined color for Custom Color 93. Sets a user-defined color for Custom Color 94. Sets a user-defined color for Custom Color 95. Sets a user-defined color for Custom Color 96. Sets a user-defined color for Custom Color 97. Sets a user-defined color for Custom Color 98. Sets a user-defined color for Custom Color 99. Adjustment factor for measured artificial light contribution. Light levels will dim when pressed and held. Maintain dimming level at minimum value when in the “off” state. Specifies dimming curve used in the driver (linear/log). The dimming level output when the associated preset is activated. Group dimming outputs together. Zone 2’s set-point as a percentage of Zones 1’s set-point (Dual Zone photocell applications only). Fixed voltage increase of Zone 2’s dimming output from Zone 1’s dimming output (Dual Zone photocell applications only). Indicates a Dual Zone photocell sensor’s method of operation. The time after receiving an “off command” for lights to dim down before turning off.

43 amin'ny 51

SensorView Terms – cont’d

Fade On Time Follow Photocell Mode Global Occupancy Broadcasting Global Occupancy Tracking Global Photocell Broadcasting Global Photocell Tracking Global Switch Broadcasting Global Switch Tracking High End Input Trim (100%)
High End Trim (100%)
Idle Screen Brightness
Idle Time Until Dim
Invert Relay Logic Lamp Type LED LED 1% Follow Photocell Level LED 100% Follow Photocell Level LED 50% Follow Photocell Level LED Inhibit Offset
Line Voltage
Load Fault Protection Local Occupancy Only
Local Photocell Only
Local Switch Only
Louver inhibit
Louver Photocell Delay Time Louver Photocell Pulse Time Louver Stroke Time Louver Switch Delay Time Louver Switch Pulse Time Low End Input Trim (1%)
Low End Trim (1%)
Lumen Compensation Maintain Dim Level when Vacant

The time after receiving an “on command” for devices to reach full bright. Instructs a device to track the dimming output maintained by an ADC device. Enable/Disable global occupancy broadcasting. Enable/Disable global occupancy tracking. Enable/Disable global photocell broadcasting. Enable/Disable global photocell tracking. Enable/Disable global switch broadcasting. Enable/Disable global switch tracking. Max photocell voltage. Follow photocell level will be 100% at high trim. Maximum dimming voltage. Output reports 100% at high trim; corresponding lumens depend on ballast/driver. Backlight brightness is reduced to this level after backlight timeout setting. Time after last detected occupancy that lights reduce to Unoccupied Dim Level for local channels. Time after occupancy time delay expires lights remain at Unoccupied Dim Level for global channels. Reverses open/closed state for relays. Specifies the dimming curve for PCD. Controls whether or not a device will illuminate its LED. Foot-candle level in shaft in which the LEDs will be full dim (1%). Foot-candle level in shaft in which the LEDs will be full bright (100%). Foot-candle level in shaft in which the LEDs will be at 50%. Offset (deadband) above “LED 1% Follow Photocell Level” before “Photocell Transition Off” timer begins. Specifies the main’s voltage the current monitoring device is operating on; used to properly calculate power level. Enable/Disable load fault protection.
Instructs a device with a relay and/or dimming output to react to only its internal occupancy information.
Instructs a device with a relay and/or dimming output to react to only its internal photocell information.
Instructs a device with a relay and/or dimming output to react to only its internal switch information.
Foot-candle level in shaft in which the Louver Transitions from Full Open to Full Close (Evening) or Full Close to Full Open (Morning). The amount of time between pulses that are sent to the motor in response to daylight harvesting. The length of the pulses that are sent to the motor in response to daylight harvesting. Time it takes the louver to go from fully open to fully closed (or vice versa). Time between pulses due to switch commands. Time the relay closes due to switch commands. Min photocell voltage. Follow photocell level will be 1% at low trim. Min dimming voltage. Dim level reports 1% at low trim; lumen output depends on ballast/ driver. Not recommended to be below factory defaults. Specifies lumen compensation mode. Prevents lights from turning fully off once in unoccupied state.

44 amin'ny 51

SensorView Terms – cont’d

Maintain Dim Level (Local Occ)
Maintain Dim Level (Global Occ)
Microphone Grace Period Microphonics Middle Input Trim (50%) MLO (High) MLO (Low) MLO Mode MLO Secondary Broadcast Channel MLV Mode Enabled Momentary Relay Mode nClass Night Light Brightness nIO Input nIO RLX Input Occupancy Broadcast Channel
Occupancy Broadcasting
Occupancy Expiration of Manual Off Occupancy PIR Sensitivity Occupancy Time Delay Occupancy Tracking Occupancy Tracking Channels
Occupied Bright Level
Override Override Input State Pattern Number 3 Cell Pattern Number 5 Cell Pattern Number 9 Cell Phase Dimming Frequency Photocell Broadcast Channel Photocell Broadcasting Photocell Dimming Range (High) Photocell Dimming Range (Low) Photocell Mode Photocell Tracking Photocell Tracking Channels

Lights will go to their Unoccupied Dim Level when occupancy is detected on an otherwise untracked local channel but no occupancy is detected on a directly tracked local channel. Lights will go to their Unoccupied Dim Level when occupancy is detected on an otherwise untracked global channel but no occupancy is detected on a directly tracked global channel. The time period after lights are automatically turned off that they can be reactivated by audio. Specifies sensitivity of microphone used to enhance occupancy detection. Mid photocell voltage. Follow photocell level will be 50% at middle trim. Dim level for the MLO high state. Dim level for the MLO low state. When enabled allows a single pole switch to control two individual switch channels. The channel on which a device with a manual switch will transmit its secondary MLO switch press. Optimizes control for magnetic low voltage devices, preventing flickering. Toggles relay momentarily for 1s when a tracked input causes an state change. Operational modes for classroom configurations. The percent of full brightness of the units night light LED. Specifies how the device should interpret incoming data on the input wires and the action it should take. Determines if actions on the input wire affect dimming, on/off, or both. The local channel on which a sensor transmits its occupancy information. Indicates whether a sensor will transmit its occupancy information to the rest of its zone. If enabled with Return to Last State after Power Cycle (RLS) also enabled, RLS will cease to function. Reverts override off commands to normal mode after Occupancy Time Delay expires. Threshold at which motion is considered detected for Occupancy. The length of time an occupancy sensor will keep the lights on after it last detects occupancy. Indicates whether a device’s relay and/or dimming output will react to occupancy information. The local channels on which a relay and/or dimming output receives occupancy information. The percentage of the controllable dimming range up to which lights will rise when occupancy is detected or the luminaire is overridden on. Indicates whether a device’s relay is forced on/off and/or dimming output is forced to maximum/minimum. Specifies the state to which the relay will remain when panel Override input is made and held. Sets a predefined grayscale pattern. Sets a predefined grayscale pattern. Sets a predefined grayscale pattern. Specifies frequency of the power feed the phase dimmer is operating on. The local channel on which a sensor transmits its photocell information. Indicates whether a sensor will transmit its photocell information to the rest of its zone. The maximum output percentage up to which an automatic dimming photocell will control. The minimum output percentage down to which an automatic dimming photocell will control. Enable photocell either to turn lights on and off, or only prevent lights from turning on. Indicates whether a device’s relay and/or dimming output will react to photocell information. The local channels on which a relay and/or dimming output receives photocell information.

45 amin'ny 51

SensorView Terms – cont’d

Photocell Transition Off
Photocell Transition On
Photocell/Profile Dimming Rate
PIN Protection Predictive Exit Time
Predictive Grace Period
Ohbfile Override Push-Button Operation Reduced Turn-on Relay Always On Relay End State
Relay Line Voltage Fasa
Relay Throw Delay
Return to Last State After Power Cycle
Rubik Factory Test Mode Scene Expiration Blink
Scene Expiration Time
Screen Backlight Timeout Screen Order for GFX Scenes/WallPods Screen Saver Mode Screen Saver Timeout Semi-Auto Grace Period Sensor LED Set-Point Ones Digit Set-Point Tens Digit Setup Screen Timeout Setup Screen Timeout Special Operating Modes Special Switch Tracking Mode Speed Percent Speed Switch Tracking Start-to-High

The time period for which a photocell must measure a light level above the set-point before it will turn the lights off. The time period for which a photocell must measure a light level below the set-point before it will initiate the lights on. The speed at which dimming level changes when triggered via profile scenes (global or local) or automatic photocell dimming. Specifies whether a pin is required to modify light levels and program device. Time period after manually switching lights off for the occupant to leave the space. The time period after the Predictive Exit Time that the sensor rescans the room for remaining occupants (Predictive Off mode only). Allow button-initiated profiles to run concurrently, as long as the profiles target different devices. Overrides a device and enables its push-button to toggle the device’s internal relay(s) or dim level. Reduces the initial PIR detection strength required to trigger occupancy. Forces relay to stay closed even in off state. Specifies the state which the relay will go to when the panel loses power. Indicates relay load’s phase relative to relay panel power supply. Helps reduce relay wear related to high switching voltages. Specifies the delay between relays when throwing multiple relays at the same time. Restores on/off/dim level set by non-sensors after power is lost and restored. This setting is ignored when Occupancy Expiration of Manual Off is enabled. Factory test commands. Blink warning will toggle all outputs prior to the expiration of the scene timer. The length of time a selected profile scene (global or local) will run before reverting affected devices to defaults. Specifies how long the backlight should remain at full brightness when in use.
Specifies order of the Scenes and WallPods screens.
Controls displayed screen saver. Sets idle time before screen saver is displayed. The time period after lights are automatically turned off that they can be reactivated with occupancy. Controls whether or not the sensor will illuminate its LED. The target light level that is to be maintained by the device (foot-candles). The target light level that is to be maintained by the device (foot-candles). Sets idle time before device exits setup mode. Sets idle time before device exits setup mode. Unique behaviors for relays and/or dimming outputs. Allows a device to ignore specific switch commands. Sets the speed at which grayscale patterns will transition. If enabled, the luminaire will ignore Speed Percent commands. Lights go to full bright for 20 minutes upon initial power up.

46 amin'ny 51

SensorView Terms – cont’d

Sunlight Discount Factor
Sweep Exit Time Sweep Grace Period Switch Broadcast Channel Switch Broadcasting
Switch Tracking
Switch Tracking Channels
Temperature Fault Protection Timed Expiration of Manual Off Timed Override Delay Unlimited Photocell Dimming Range
Unoccupied Dim Level
Visibility (Graphic Preset) Visibility (Graphic Scene) Visibility (Graphic WallPod)
WallPod Dimming Adjustments

Adjust the photocell’s ability to influence light level. Decreasing the discount in a period of high daylight will lower the light level. The time period before a sweep is executed (affects all buttons operating in sweep mode). The remaining time delay a sensor reverts to after a sweep is executed. The local channel on which a device with a manual switch and/or dimmer transmits. Indicates whether a device will transmit its manual switching and/or dimmer events to the rest of its zone. Indicates whether a device’s relay and/or dimming output will react to manual switching and/or dimmer events.
The local channels on which a relay and/or dimming output receives manual switching or dimming events.
Enable/Disable temperature fault protection. Reverts override off commands to normal mode after Timed Override Delay expires.
The length of time an Override On or Off state initiated by a Special Operating Mode will remain in effect.
Allows the offset zone on a DZ device, or follow photocell device, to go full bright or full dim. Level to which lights dim once the Idle Time Until Dim expires. Also, low trim level for dimming switches and photocells. Specifies whether or not a configured Preset button will be displayed. Specifies whether or not a configured Scene button will be displayed on the main page. Specifies whether or not a configured WallPod button will be displayed on the main page. Defines whether user dimming adjustments are maintained after lights are cycled or whether they revert to preset levels.

47 amin'ny 51

Kisary sata

BOKYtage Status

matoanteny

sarobidy

Bridge / Transceiver PowerState Power Supply Voltage: (VDC)

Bridge / Transceiver Power State Power Supply Voltage: (VDC)

Broadcasting & Tracking Status

matoanteny

sarobidy

Occupancy Broadcasting

Occupancy Tracking

Photocell Broadcasting

Photocell Tracking

Switch Broadcasting

Switch Tracking

Scenes & Profiles Status

matoanteny

sarobidy

Scene States (per button/nIO) Scene State: Active

Scene States (per button/nIO) Scene State: Idle
Scene States (per button/nIO) Scene State: Disabled

Scene Expiration Time

Photocell Not Inhibiting
Photocell Status (per pole) Transition time: (hh:mm:ss)
hafanana
LightLevel Measured light level: (fc)
Ohbfile Active

Ohbfile tsy mavitrika

Description Device has adequate power (bridge) Device is close to low power condition (bridge) Device is in low power condition (bridge)
Description Occupancy status broadcast is active Occupancy status tracking is active Photocell status broadcast is active Photocell status tracking is active Switch status broadcast is active Switch status tracking is active
Description Scene associated with button is active Scene associated with button is not active Button is disabled Indicates when current running scene/profile will expire Indicates that photocell is not preventing lights from being on Indicates when current photocell state will change Current temperature at the processor of the device Current foot candle level as measured by the photocell Profile is currently active Profile is NOT currently active

48 amin'ny 51

Status Icons – cont’d

Photocell Status

matoanteny

sarobidy

Photocell Inhibiting

Photocell Not Inhibiting

Photocell Status (per pole) Transition time: (hh:mm:ss)
LightLevel Measured light level: (fc)

PIR & PDT Status

matoanteny

sarobidy

Time Delay Remaining (hh:mm:ss)

Tracked Occupancy Timer

PIR Activity

Microphonic Activity

Occupancy, Relay & Dimming Status

matoanteny

sarobidy

variana

banga

Dimming Output (input) level: (%)

Input Dim Level

Pole State Reason

Accumulated Hours

Compensated Output Level

Description Indicates that photocell is preventing the lights from being on Indicates that photocell is not preventing lights from being on Indicates when current photocell state will change Current foot candle level as measured by the photocell
Description Indicates when current occupancy state will expire Reason why pole is open or closed PIR Activity detected/detecting occupant motion No PIR Activity. PIR not currently detecting occupant motion Microphone has detected a triggering noise Microphones are not currently detecting noises
Description Room is occupied Room is not occupied Current % of 0-10 VDC scales Follow Photocell Level: 4.9% or Input Dim Level: 100% Reason why pole is open or closed Accumulated Hours: 1272 Compensated Output Level: 0 Pole State reason: Manual Switch Override Off

Relay State (per pole)

mihidy

49 amin'ny 51

Status Icons – cont’d

Occupancy, Relay & Dimming Status – cont’d

matoanteny

sarobidy

Relay State (per pole)

Photocell Status

matoanteny

sarobidy

Wireless Signal Strength: (1- 5)

Wireless PAN ID

Wireless Node ID

Wireless Channel: (11-26)

Wireless State:

Bridge Port Information

Description
Misokatra
Description
Indicates wireless signal strength (higher is better)
Wireless panel identification number
Wireless node identification number
Indicates the wireless channel currently being used
Wireless States: Normal Validating the network Searching for a network that is allowing joining Creating a new network Allowing joining Cloning is happening in the system Multiple SSI networks are allowing joining Lost a remote device during OTA cloning Wireless device is not responding
Port States: Polling downstream devices Upstream port Commissioning tool connected Polling downstream bridges Error: Too many adds/deletes (reset bridge) Error: Local loop Error: Non-local loop Error: Devices connected between bridges

50 amin'ny 51

Status Icons – cont’d
Photocell Status – cont’d

matoanteny

sarobidy

Transceiver Port Status

Description
Number of downstream wireless Bridges and Transceivers
Port States: Polling downstream devices Upstream port Commissioning tool connected Polling downstream bridges Error: Too many adds/deletes (reset bridge) Error: Local loop Error: Non-local loop Error: Devices connected between bridges
Number of downstream wireless Bridges & Transceivers

51 amin'ny 51

Documents / Loharano

SensorView Rindrambaiko fanaraha-maso jiro

User Guide · SensorView Lighting Control Software, SensorView, Lighting Control Software, Control Software, Software

References

fota.acuitynext.io/v1/updates/sensorview/stable/svsetup/installer/latest/SensorView_Setup.exefota.acuitynext.io
img.acuitybrands.com/general-site-storage/Private/Sensorview/postgresql-10.1-1-windows.exeimg.acuitybrands.com
img.acuitybrands.com/general-site-storage/Private/Sensorview/psqlodbc_10_03_0000-x64.zipimg.acuitybrands.com
acuitybrands.comwww.novaintranl.nl
User Manualmanual.tools

Published: June 8, 2026

Nohavaozina: 9 Jona 2026

nLIGHT SensorView Lighting Control Software User Guide

nLIGHT SensorView Rindrambaiko fanaraha-maso jiro

fepetra arahana

Torolàlana fampiasana

Admin

vavahady

Mail server

Documents / Loharano

References

Mametraha fanontaniana

Lohahevitra mifandraika

nLIGHT SensorView Rindrambaiko fanaraha-maso jiro

fepetra arahana

Torolàlana fampiasana

Login and User Management

Admin

vavahady

Mail server

Documents / Loharano

References

Mametraha fanontaniana

Mametraha fanontaniana Cancel question

Lohahevitra mifandraika

farany nHazava Manuals