On a device’s page, you will see a list of options that looks like this:
These tabs will help you unlock the most out of your devices, and so each option in the list is detailed below.
The data management tab is home to all of a device’s streams. For example, a hub might have a stream called “openRegistration”, whose integer value refers to the connection state of children to the hub. While each device class has its own set of streams that define that particular class’s attributes, this tab is home to them all. Streams are defined by a device class, so that no matter how many of a given device you have in a project, they are all similarly attributed and can be analyzed in the same ways. For example, if you have a class of leak detecters, each instantiation will have a standardized set of streams including things like “leakDetected” to report.
Triggers are protocols activated as response to streams, and can be anything from sending an alert to your team’s Slack or plugging a stream value into a function for calculation.
To learn how to create triggers within a device class, visit the Creating Triggers guide in the Development Guides section.
The next tab is called “Configuration Management” and contains the .json files defining each device’s firmware. For basic operations, this section can be left untouched. But if you want to tinker with a device’s configuration, visit the “Defining Device Classes” guide in the Development Guides section.
The “Child Devices” tab (visible only for hubs), displays all children devices of a hub, and allows for assignment of more devices to that hub, with this button:
For a sensor device, this tab does not appear, as each sensor can have only one parent, which is shown in the “relationships” line at the top of the page.
This tab contains information about the version of software installed on your device, and allows for updates and further management. Below is shown a bar of options in this tab, allowing you to update software and firmware, as well as view software records and manage rollout:
These options will allow you to update and manage your device’s software in real time.
Visit the “Managing Firmware” section for more.
This section contains a list of all a device’s events, with time stamp and information accompanying events like “firmware_request,” “firmware_response,” or “mqtt_command_sent_ping.” These tags tell you what action was taken, associated with a time stamp, so that you can accurately monitor the activity of any given device in real time. Further, this tab is home to a drop-down menu called “Actions,” which houses options to ping your device, restart the client, trigger configuration change, reboot your device, and reset your device to factory settings. With these options, you can work through issues with your assets throughout their lifecycle.