Swidget Driver Configuration

Estimated reading: 3 minutes

Installation Process

It is recommended that you follow the below installation process in order to ensure you are running the latest version of the driver.The Driver is installed as a Communication Device.

Under Lighting, Click Communication Device —> Add New Communication Device and pick SwidgetPro

Enter Secret Key used when the device was provisioned using the Swidget Guide
Choose Installation Options:
1. Lighting will install only the light section of the device
2. Sensors will install only the sensor section of the device
3. Lighting + Sensor will isntall both.
Choose the Check Connection: 1 Hour is the default. This check is extra. The driver has a built in heartbeat and healing mechanism. This will add a manual check to reconnect any devices.
Enter the number of devices you have on the network. The driver will automatically install a lighting subdriver per 10 devices. If you have less than 10, leave this field empty, the driver will automatically detect and install the first 10 Swidget. This is not a driver or Swidget limiation but an Nice / Elan API limitation.
Click Discover / Install. The driver can up to 60 seconds to discover and install up to 10 devices. If the number of devices exceeds 10 the time can be longer. Please be patient….
The Driver will discover all Wi-Fi enabled light switches on the network.
Note: The driver will split lights into groups of 10 to accommodate Nice / Elan OS requirements. This doesn’t

Note: If a device has multiple power control inserts, the driver will split those into two entries. The split entries still count as one device towards the 10 device limit per driver (you can install multiple drivers to accommodate more that 10 Swidget device, so go ahead and buy more 😊)

Input / Output Driver

The driver will also install each device that has a supported insert as an input / output driver.
The driver will automatically choose the best sub driver to match each insert.
Energy measurements will be split into their own sub drivers. So it is possible for one insert to have multiple sub drivers.
The Driver will install Numeric Inputs to be used for triggers. See section at the end on how to handle Numeric Inputs with the same name.

Note: If an insert or sensor is not discovered or installed after first Discover / Install, try again. You might have to try a few times. If after a few tries not all sensors are installed, start troubleshooting.

Numeric Inputs

The Driver will add the insert data points as numeric variables so you can use them as numeric triggers. For example, if the battery position < value, then execute an event.

By default, the controller names all the Input / Output variables using the same name.

To change the names for easy identification, match the Driver ID under each numeric input to the System # in the Input Controller and change the name to match. Use the new names in Event Maps and triggers.

Creating a Numeric Trigger

If a device has a measurement unit that lends itself to numeric evaluation, the driver creates it as a Numeric Variable. Use Elan’s internal engine for comparison to create trigger events. See Illustration below