Skip to main content
A harmonized interface defines what a set of device values means. It lets applications interpret a capability consistently across different device implementations.

Interface identity

An interface has a versioned URI. Applications must compare the exact identifier and supported version instead of guessing from a model name. A temperature interface, for example, identifies a shared interpretation of temperature fields and their required metadata. A device can implement a base interface and optional extensions. Aggregate interfaces add shared behavior, such as statistical values, to a base capability. Support for an interface does not by itself grant permission to read or control the device.

Application responsibilities

  • Check the interfaces and versions available through the provider’s supported API.
  • Retain units, timestamps, quality information, and node identity with values.
  • Require the base capability before using one of its extensions.
  • Handle unknown interface identifiers without interpreting them as a familiar version.
Use the device model for addressing concepts and Agent Things API availability before implementing a device workflow.