Possible Unit types used for decimal values.
Dimensionless quantity
Percent
Decimal degrees
Celsius
Fahrenheit
Kelvin [SI]
Kilometer [SI]
Meter [SI]
Centimeter [SI]
Millimeter [SI]
Hour
Minute
Second [SI]
Millisecond
Square kilometer
Square meter
Square cm
Cubic meter
Liter [SI]
Centiliter [SI]
Milliliter [SI]
Kilogram [SI]
Gram [SI]
Milligram [SI]
Watt hour
Kilowatt hour
Watt [SI]
Ampere [SI]
Hertz [SI]
Volt [SI]
Newton [SI]
Pascal [SI]
Coulomb [SI]
Farad [SI]
Ohm [SI]
Siemens [SI]
Weber [SI]
Tesla [SI]
Henry [SI]
Lumen [SI]
Lux [SI]
1 byte = 8 bits
Meter per second
Candela [SI]
Mole [SI]
Ultraviolet index
RGB color, encoded as integer value between 0 (usually represented as
0x000000) and 16777215 (usually represented as 0xFFFFFF), e.g. Blue
would be 255 (usually represented as 0x0000FF)
Parts per million (Alternative use percent: 1ppm = 0.0001%)
Sievert (J/kg) [SI]
Joule [SI]
Rotations per minute
Pulses per second
Cubic meters per second
Liters per second
The decibel (symbol: dB) is a relative unit of measurement equal to one tenth of a bel (B). It expresses the ratio of two values of a power or root-power quantity on a logarithmic scale.
dBm or dBmW (decibel-milliwatts) is a unit of power level expressed using a logarithmic decibel (dB) scale respective to one milliwatt (mW).
Electron Volt
var: (IEC symbol): reactive power (volt-ampere-reactive).
It represents the electrical power that flows back and forth between the phase conductors and the neutral conductor of a three-phase network, but does not perform any mechanical work.
VA: (SI symbol) apparent power: unit of measurement for electrical power.
It represents the total available power in a alternating current system. It is made of the active power (W) and the reactive power (var).
PF: (Power Factor: In AC power system it is defined as the ratio of the real power absorbed by the load to the apparent power flowing in the circuit.
It is important the the power factor should be as close to "1.0" as possible. It is generally expressed as a decimal value or as a percentage.
A timestamp in dateTime format (the subset of the ISO 8601 date-time format defined by the SOAP dateTime type).
bps: bits per second
Describes the type of Device that the {{object}} instance is
representing. {{enum}}
Describes the type of IoT Level Controller or Sensor that the {{object}}
instance is representing. {{enum}}
Amount of space that an object or substance occupies
Describes the type of IoT Enum Controller that the {{object}} instance is
representing. {{enum}}
Describes the type of IoT Enum Sensor type the {{object}} instance is representing.
Describes the type of IoT Blob Sensor that the {{object}}
instance is representing.These are examples to identify a "string of bytes" that has been sent by a Sensor {{enum}}
Describes the type of pulse that the {{object}}
instance is representing. {{enum}}
{{numentries}}
Each Node instance represents distinct functional devices, which are
virtual and abstracted representation of functionality.
{{datatype|expand}}
Human-readable description of the {{object}}. e.g. a more detailed
description of {{param|Type}}.
Extensions for the proxied device object
{{datatype|expand}}
Human-readable description of the {{object}}. e.g. a more detailed
description of {{param|Type}}.
A textual name of the instance, which can be assigned by the user.
{{object}}.
This parameter provides the state of the {{object}} on the underlying
(proxied) connected network.
The date time of the last successful contact.
{{reference|a protocol object that uses the {{param|ProxyProtocol}}}}.
The protocol being used to communicate between the Agent and this
Proxied Device. {{enum}}
Vendors can extend the enumerated values with vendor specific
extensions, in which case the rules outlined in {{bibref|TR-106|3.3}}
MUST be adhered to.
see {{bibref|Z-Wave}}
see {{bibref|ZigBee}}
see {{bibref|UPnP-DM:1}}
{{numentries}}
This list of IoT capability objects.
A textual name of the instance, which can be assigned by the user.
Describes the type of functionality that {{object}} is representing.
Depending on the functionality the corresponding sub-object is
instantiated.
Note: Only one of the defined sub-objects can exist in an {{object}}
instance.
{{numentries}}
This capability provides a boolean function that is mapped to the type
of function it represents.
E.g. If the instance represents a door lock ({{param|Type}} is
{{enum|Locked|Type}}), a {{param|Value}} of {{true}} says the door lock
is locked.
Describes the type of functionality that {{object}} is representing.
Human-readable description of the {{object}}. e.g. a more detailed
description of {{param|Type}}.
Value of {{true}} or {{false}} that reflects the functionality.
Toggle the {{param|Value}}.
LevelController is used to model a control with a range of continuous
states.
These values are configurable via {{param|Value}} and measured in
{{param|Unit}} and are restricted between a Min and Max values.
Intensity profile - {{param|Value}} of intensity and ability to update
that level through {{command|StepUp()}} and {{command|StepDown()}}
commands with a configurable {{param|StepValue}}.
{{datatype|expand}}
Human-readable description of the {{object}}. e.g. a more detailed
description of {{param|Type}}.
The desired run value that this {{object}} will be between
{{param|MinValue}} and {{param|MaxValue}}.
Units in which {{param|Value}}, {{param|Value}}, {{param|MinValue}},
{{param|MaxValue}} and {{param|StepValue}} are expressed.
{{datatype|expand}}.
Minimum allowed value for {{param|Value}}.
Maximum allowed value for {{param|Value}}.
Number of {{param|Unit}} changes of each {{command|StepUp()}} and
{{command|StepDown()}} command.
Step Up the {{param|Value}}.
Step Down the {{param|Value}}.
The EnumControl reflects the Enumerated level Control functionality.
The enumeration is defined by the {{param|ValidValues}} parameter. This
will provide a comma-separated list of values that are available for
configuring via the {{param|Value}} parameter.
{{datatype|expand}}
Human-readable description of the {{object}}. For example, a more detailed
description of {{param|Type}}.
Current value representing the {{object}}; MUST be an element of
{{param|ValidValues}}.
List of valid values from the control represented by the {{object}}.
Step up the {{param|Value}} to the next allowed value in the enum.
Step down the {{param|Value}} to the previous allowed value in the
enum.
{{object}} provides information to an actuator that sensor changed from one state to another state.
In addition to the state change, the {{object}} can provide additional information about the type of transition via {{param|Transition}} and the pulse duration via {{param|Duration}}.
{{datatype|expand}}
Human-readable description of the {{object}}. For example, a more detailed
description of {{param|Type}}.
Some {{object}} instances can provide a duration together with the latest state change.
The duration is an indication of the time, measured in {{units}}, between the start of the state change and the end of the state change: i.e., returning to its orignal state.
The original state can be a low state or high state.
Indicates the moment a pulse is generated. This can be a
{{enum|RisingEdge}} transition: in case the sensor changes from low to high state.
{{enum|FallingEdge}} transition: in case the sensor changes from high to low state.
The sensor changes from low to high state.
The sensor changes from high to low state.
Generate a Pulse with a {{enum|RisingEdge|Transition}} transition for a duration of {{param|Duration}}.
Time between the start of the state change and the return to its original state. {{param}} is measured in {{units}}.
Generate a Pulse with a {{enum|FallingEdge|Transition}} transition for a duration of {{param|Duration}}.
Time between the start of the state change and the return to its original state. {{param}} is measured in {{units}}.
BinarySensor is used to reflect the functionality of a sensor that
reports a {{param|Value}}. The {{param|Sensitivity}} configures the
degree of sensitivity that the sensor uses for detection.
Timed BinarySensor profile - To provide the ability to add time based
control over the {{param|Value}} attribute. How long the
{{param|Value}} remains true is controlled by the {{param|HoldTime}}.
{{param|RestTime}} controls how soon, after being activated, the sensor
will respond to continuous events.
Describes the type of functionality that {{object}} is representing.
Human-readable description of the {{object}}. e.g. a more detailed
description of {{param|Type}}.
If the {{object}} has been recently activated, the value would be
true. For how long the state attribute remain true after being
activated depends on the underlying sensor reports.
The date and time in UTC when {{param|Value}} has been changed to the
current value.
The date and time in UTC when the {{object}} has received data.
A 0 to 100 value indicating how reactive to changes the {{object}}
should be, 0 being not sensible / disabled and 100 max sensitivity.
After activation has been detected and the sensing attribute set to
true, how soon, in {{units}} should the {{param|Value}} be reset to
{{false}}.
After activation has been detected and the {{param|Value}} set to
{{true}}, how soon, in {{units}} should affected again per subsequent
event.
LevelSensor is used to reflect the functionality of a sensor that
reports a {{param|Value}} in {{param|Unit}}.
{{datatype|expand}}
Human-readable description of the {{object}}. e.g. a more detailed
description of {{param|Type}}.
The current value reading of this {{object}} in units defined in
{{param|Unit}}.
The date and time in UTC when {{param|Value}} has been changed to the
current value.
The date and time in UTC when the {{object}} has received data.
{{datatype|expand}}
Unit in which {{param|Value}} is expressed.
Low level indicator. Is set to {{true}} if {{param|Value}} is equal
or less than the value defined in {{param|LowLevelThreshold}}.
The threshold value in for {{param|LowLevel}} expressed in the same
units like {{param|Value}}.
High level indicator. Is set to {{true}} if {{param|Value}} is equal
or higher than the value defined in {{param|HighLevelThreshold}}.
The threshold value in for {{param|HighLevel}} expressed in the same
units like {{param|Value}}.
MultiLevelSensor is used to reflect the functionality of a sensor that
reports multiple {{param|Values}} with the same {{param|Unit}}.
Describes the type of functionality that {{object}} is representing.
RGB color, encoded as integer value between 0 (usually
represented as 0x000000) and 16777215 (usually represented as
0xFFFFFF), e.g. Blue would be 255 (usually represented as
0x0000FF)
The sensor reports a location with the values of Longitude,
Latitude, Altitude as decimal values in km.
Human-readable description of the {{object}}. e.g. a more detailed
description of {{param|Type}}.
The current value reading of this {{object}} in units defined in
{{param|Unit}}.
The names of the values expressed in {{param|Values}}.
The date and time when {{param|Values}} has been changed to the
current values.
The date and time in UTC when the {{object}} has received data.
{{datatype|expand}}
Unit in which {{param|Values}} are expressed.
EnumSensor is used to reflect the functionality of a sensor that
reports explicit non-continuous values.
{{datatype|expand}}
Human-readable description of the {{object}}. e.g. a more detailed
description of {{param|Type}}.
The actual reading value; MUST be a member of the enumeration defined
in {{param|ValidValues}}.
The date and time when {{param|Value}} has been changed to the
current value.
The date and time in UTC when the {{object}} has received data.
List of valid values reported from the sensor represented by this
{{object}}.
BlobSensor is a sensor that is able to send specific data as a "string of bytes" depending on its use. For example in case of traffic control Sensors,
A Sensor can forward an image, a numberplate. RFID-Sensors forward an RFID. They have all in common that a "string of bytes" have been sent. To identify
the type of bytes, the IoTBlobSensorType provides information about this "string of bytes".
{{datatype|expand}}
Human-readable description of the {{object}}. e.g. a more detailed
description of {{param|Type}}.
A Blob value is to be considered as a "string of bytes". The {{param|Type}} of this "string of bytes" is intended to be explained by {{param|Type}}.
Examples do exist for Sensors used in traffic control, such as an image, numberplate, and face recognition, RFID readers and other areas where Sensors produce bytes.
The date and time in UTC when {{param|Value}} has been changed to the
current value.
The date and time in UTC when the {{object}} has received data.
The Value is typically a string of bytes and its meaning is described by {{param|Type}}. A string of bytes will use the base64 type.
The current value reading of this {{object}}.
This {{object}} only exists in a Sensor IoTCapability.
Adding a {{object}} instance to a Control IoTCapability MUST fail.
Each entry in this table describes the link between this Sensor IoTCapability and a specific Control IoTCapability.
When a Sensor IoT Capability is bound to a Control IoT Capability, then for each Value parameter updates of the Sensor IoTCapability, the Agent evaluates the needs to update the Value parameter of the bound Control IoTCapability.
Friendly name for this binding.
Description of the binding's intent and function.
When {{true}}, the binding is active; otherwise, no data flow occurs and the Value parameter of {{param|ControlIoTCapability}} is not updated.
A valid {{param}} is a reference to a Control IoTCapability in the {{object|##.IoTCapability}} table.
Setting {{param}} to a Sensor IoTCapability MUST fail.
It references the Control IoTCapability to use as the binding destination on which the Agent updates the Value parameter.
As a mountable object {{object|##.IoTCapability}} may also be mounted on one of the following mountpoints:
* {{object|##.Node.{i}.}},
* {{object|##.ProxiedDevice.{i}.}},
* {{object|##.ProxiedDevice.{i}.Node.{i}.}}
A {{object}} is used to reflect the functionality of a sensor that changed state from low to high or high to low.
A {{object}} provides a trigger on the rising edge of this state change, which is identified by {{param|Transition}}.
Some {{object}} instances have the possibility to provide a pulse duration {{param|Duration}} together with the latest state change.
{{datatype|expand}}
Human-readable description of the {{object}}. For example, a more detailed
description of {{param|Type}}.
The date and time in UTC when {{param|Duration}} or {{param|Transition}}has been changed to the
current value.
The date and time in UTC when the {{object}} has received data.
Some {{object}} instances can provide a duration together with the latest state change.
The duration is an indication of the time, measured in {{units}}, between the start of the state change and the end of the state change: i.e., returning to its orignal state.
The original state can be a low state or high state.
Unit in which {{param|Duration}} is expressed in {{units}}.
Indicates the moment a pulse is generated. This can be a
{{enum|RisingEdge}} transition: in case the sensor changes from low to high state.
{{enum|FallingEdge}} transition: in case the sensor changes from high to low state.
The sensor changes from low to high state.
The sensor changes from high to low state.