icon.
Manage Device Controls
To manage device controls resources use the icon.
For a newly configured device there will be no configured controls. To create one click on the 'New' button. If a control has been configured then it will be in the list. Select the item to modify and press the 'Edit' button or just double click the item.
The 'All' button selects or deselects all of the items.
Manage Device Control
The selected device control resource dialog is as follows
Name
The 'Name' field is a definable name that is used to meaningfully refer to this control. If left blank it will be auto filled when the 'Node' field is selected.
Node
The 'node' field is the device's unique directory node of the device. This field is created from the list of capability resources that the device reports. There can only be one control for every resource. If the resource is not used then there is no need to create a control for it.
Description
The 'Description' field is definable text to describe the device's functionality and or location. It is used for human readability. It will be auto filled when the 'Node' field is selected.
Type
If the type of resource control is known and is on the list then choose it. This will help the application to better handle the control.
For sensors the 'Binary input', 'Analog input' or 'Range input' should be selected. If it is a simple input that only detects on / off, open / closed, active / inactive then 'Binary input' is the best type setting for it. For an input that has a numeric value like an analog input then 'Analog input' is the choice. If the value has an upper and lower setting then the 'Range input' should be chosen.
For actuators the 'Actuator', 'Relay output', 'Level output' or 'Range input' should be picked. If it is a simple output that is on / off, high / low or open / closed then 'Actuator' or 'Relay output is the best type setting for it. For an output actuator that has a numeric value like an analog output then 'Level output' is the choice. If the value has an upper and lower setting then the 'Range output' should be chosen.
Units
The 'Units' field is definable text to describe the device's control units. It is used for human readability. Some examples are "Celsius", "Watts" and "Amps" etc.
Active
The control is seen as in an active state when it reported value is in a specific range.
Inverse for active
If the 'Inverse for active' is ticked that what is normally considered active like input is on will be considered inactive and off will be considered active. It effectively just inverts the logic.
Upper Level
The 'Upper Level' field is used for controls with numeric values. The control is considered active when the value is at or above the upper level. This can work with the 'Inverse for active' if it needs to be active when below the level.
Lower Level
The 'Lower Level' field is used for controls with numeric values. It is used in conjuction with the 'Upper Level' The control is considered active when the value is at or above the upper level or at and below the lower level. This can work with the 'Inverse for active' if it needs to be active when between the levels.
Hysteresis
Inputs can jitter about its current level if this is right on the level setting it will generate a series of active and inactive reports. To mitigate this hysteresis can be applied to ensure an absolute change.
This is used with the 'Upper level' and 'Lower level' settings. When the controls value level falls back below the upper level then the condition is restored. However if the hysteresis is set then the controls value level must fall below the set level by the amount of the hysteresis to restore the condition. Similar it applies 'Lower level' where the Control level must restore above then lower level by the hysteresis amount to become inactive again.
Report Alarm
If the 'Report alarm' option is ticked then whenever the control goes into and out of an active state then it is reported in the log. If the event is unimportant then this can be unselected.
Classification group
The 'Classification group' is a label that can be assigned to this control. Similar controls can be assigned the same label to facilitate group actions on all of the controls with the same classification.
Override settings
There is a lot of variation in implementation between vendors of various IoT devices. To assist in extracting the correct information from the data these settings can be applied. This feature is an advance setting and requires some level of expertise.
These settings are not normally needed as the node and type setting is used internally to judge these setting Sometimes just the node setting is required.
Note that querying the control can provide information that an operator can then determine what override settings can be applied
Object ID
The node setting selects the aspect of the device that has useful content. However sometimes with more complex devices the information can be bundled. For example it could provide both voltage and current. With this sort of information there is also a reference string that can be used to identify which is which. Setting the object ID to the desired reference string will allow the correct information to be extracted
Object Type
There is often a lot of information is provided but only what is relevant is needed. The information often use IPSO type numbers to make is clear to machines what the information is suppose to mean. Setting this will override what is determined to be the the object of interest for this control.
Resource Type
Similar to the object type the resource type can override what property is really wanted.