Developer’s User Interface
We have developed a range of tools to assist in the profiling of devices, which requires the operation of each device to be examined in detail. .
The starting point for the profiling of a device is the testing of an individual device. This entails the joining of the device to the network, and then the online observation and recording of all of the device behaviors.
The information obtained in this way then forms the basis of the profile for all devices of the same type and manufacturer as the tested device. Each of the devices listed here have been subjected to this testing.
This particular example is for a Hive heating receiver. Although this heating receiver is normally used in conjunction with a Hive thermostat, the profiling enables it to be operated with other thermostats. It can also be operated with just a temperature sensor, with the settings controlled solely through an App, so that the thermostat becomes redundant.
To illustrate the tools that are used, four screenshots have been taken of one of several onscreen areas (panes) that are available to the profile developer. These are presented in a video as a succession of static images
Four tabs are shown in succession in this video.
You can run and pause the video by clicking on the button at the left hand end of the progress bar. You can also click at any position on the progress bar when the video is paused to view the tab at that point in time. You can also click on the progress bar when the video is running to restart it from that point.
This example is for a heating receiver, which controls the boiler and the circulatory pump for a central heating system. Heating receivers normally operate in conjunction with a thermostat, or just a temperature sensor, and an App, through which the system can be controlled.
The heating receiver has a built-in programmable heating scheduler. It will accept updates to its heating schedule, and commands to override the schedule. The heating receiver also sends reports, including the current actual temperature and the target temperature.
This is reflected in the tabs, which Overview tab, tabs for Endpoint #5, Endpoint #6, Endpoint #7 and Endpoint #8, a Zones / Events tab and an Advanced tab. All of the data shown on these tabs is captured in real time by the control system.
Only the Overview tab, the Endpoint #5 tab, the Endpoint #6 tab and the Zones / Events tab.
A button at the top of every tab enables the user to access the profile that has been generated for the device.
This tab provides a summary of the device and its location. Although not yet being released, the system includes a floor plan, which shows the location of each device one each floor of the property. The icon to be used for the device is selectable on this page. As well as showing the location of each device, the status of each device is also shown on this floor plan.
The user can also view the current activity of the device in terms of its reporting, the commands that it has received, and the frames being exchanged.
Depending on the type of device, controls are included towards the bottom of this tab for testing the device. In the case of the heating receiver, the current report temperature is displayed, and the user can set the target temperature.
The heating receiver has more controls than most devices, and these are shown on a separate pane. This pane provides much more detailed reporting from the device, as well as the external weather conditions.
It also contains controls for boosting, with variable duration and target temperature, day-to-day scheduling, and manual control. These enable the developer to test the heating receiver in all of the ways that it might be used normally.
The next two screenshots are for the Endpoint #5 tab. The first screenshot shows the Basic Cluster for Endpoint #5, and the Attributes for this Cluster. The second screenshot shows the additional Clusters for Endpoint #5, which Identify, Alarms, Time and Thermostat.
The next screenshot shows the Cluster for Endpoint #6, which is Thermostat.
The last screenshot lists the device events that have been identified for use within the profile, and a log of the recent events.