Devices
Last updated
Was this helpful?
Last updated
Was this helpful?
A device in general is defined as a data stream which generates measurement data on a location. It can be an IoT device or a webhook from a gateway or a connection to an existing database.
In case the measurement data comes directly from an IoT device then this IoT device can be connected to a location. A location is the representation of the asset that is measured, or the location where the measurement is performed.
The device installation process consists of a few steps. Ideally connectivity at the location is tested first. Then, the device is installed. Lastly, while on the location the device is connected to the location and ports in the monitoring environment.
Ideally, the device connectivity is tested before installation, to make sure the device is able to make cellular connection at that location. This can also be done after installation, but if there is a problem, the work of connecting all the wiring may have been in vain.
To test the connection follow these steps:
Attach the antenna if needed
Turn on the device
Go to the monitoring environment of the device
Go to 'Devices' and find the specific device on the basis of the Device ID
Check the most recent time the device was online (if only a time is shown, that means it was today)
Depending on the type of device, installing the device in the field typically requires attaching it to the wall or placing it in a pole or cabinet. The sensors of the device have to be attached to the specific point on the asset where measurement need to be taken. Generally, it is important to install the antenna in a location where it is not obstructed from making cellular connection.
This is done by filling in the unique Device ID (hashID) which is listed on the device.
A device can be unlinked from a location and linked to another location or even a different monitoring environment. We demonstrate how to connect and remove a device to/from a location in a how-to video.
If a device is moved to another location, all the previous measurements will not be moved with it. Measurements are stored on a port of a device which is linked to a location.
In the GIF below it is shown how to create a new location and link a device to that newly created location. The steps taken are:
Unlink a device from a location (in this case 'Test location 1')
Create a new location
Link the device to the new location
Create ports
Go to graphs (where no old data is stored and new data will be coming in)
Many devices also use bi-directional communication to activate specific functionality, change measurement frequency or update the device firmware. You can view the specific device commands by going to commands. There you can schedule a new command or you can see the history of executed or planned commands. The device supplier can configure which commands are visible in the monitoring environment.
You can easily create repeating commands with different intervals. While setting up a periodic command, you’ll see the exact same for as for when you create a command, then you will be able to setup some extra fields (e.g. date and time) for the repetition of the command itself.
Once a periodic command planned date is passed (+/- 5 minutes), a command will be created and the periodic command will be updated to reflect the next planned command
It is possible to search the commands with different constraints such as whether commands were executed, for specific devices, which user created the command and whether it was planned on or before a specific date.
In case the measurement data comes from another data source through for example a webhook, then the connection process is carried out in the same way. To see how to generate hashIDs or how to set up such links see the section.
A command can be sent to a number of devices which share the same . It is also possible to send commands to all devices that share a command type in an existing of locations, or to all devices of the same .
