Provisioning Devices

The process to provision a device depends on what kind of device you are using. For this process, there are two main kinds of devices: hub devices and children devices, denoting a device’s ability to connect (or not) to the internet. Both types of device require pre-made device classes, so if you do not have a class type defined for your device, visit the “Defining Device Classes” guide in the Development Guides section. If you want to provision a device of an already-defined class, please see the appropriate guide for your device based on its ability to access the internet.

Provisioning an Internet-Capable Device

Before beginning to provision your device on the dashboard, make sure that it is correctly powered and connected to internet. Once your device is ready to go, click on the “Create Device” button on the project’s home screen, to get this pop-up:

../_images/CreateDevice.png

This pop-up allows you to enter a device name, a serial number (which must be transcribed from the physical device in order to properly pair), and to enter your device’s class type. After pressing submit, the new device will be visible on the device list like this:

../_images/DemoHub.png

Click on the view button on the left-hand side of this bar to see the device’s details. At this point, there will be visible attributes such as name, Id, serial, and activation key. The serial number is the singular sequence that defines the particular device being configured, and at this point the serial number must be copy-and-pasted into the activation key box, too.

With that done and the device turned on and connected to the internet, the activation should happen automatically, indicated by the Connection State changing, like this:

../_images/ConnectionState.png

At this point, the device has been provisioned and activated, and is live and online. Now, it is possible to connect child devices to the hub, the process of which is demonstrated below!

Provisioning Other Devices

Without internet capabilities of its own, provisioning a non-IP device follows a slightly different process than an IP-capable device, and can only be done with an IP-capable device properly provisioned and activated. The reason that non-IP devices need “smart” devices is because a non-IP device transmits its data to a “smart” device, which communicates with the dashboard on the other’s behalf.

Devices that do not connect to the internet become “children” to internet-capable devices, so these IP devices can communicate with the server on the non-IP devices’ behalf. To get started with a non-IP device, it must be powered on and must be in range of an internet-capable device that will become its “parent.”

Once powered, the device is ready for provisioning in the dashboard. Similar for this stage of setting up an internet-capable device, go into your project’s homepage and click the “Create Device” button to enter your device’s name, serial number (again, found on the physical device), and class type.

With your new device created on the dashboard, you can now proceed to pair your device to its parent using the pairing features in the hardware of each, the method of which depends on the device type you are using. For example, a Crow leak detector has a pairing button in the middle of its body, which is triggered by a five-second press. Once your device connects to its parent, the dashboard will update to reflect this relationship, and your device will begin collecting data and uploading it through its parent to the server.