Skip to main content
Sensor fields and control parameters describe how to exchange values. A harmonized interface describes what those values mean together. It is a versioned capability contract that lets a client interoperate without product-specific knowledge.

​
Interface identifiers

Each interface is a URI. Neuro-Foundation base interfaces use urn:nfi:iot:hi:; aggregate interfaces use urn:nfi:iot:hia:; shared enumeration definitions use urn:nfi:iot:hie:. The URI ends in a version, so compatibility is explicit.
An interface defines mandatory behavior and optional extensions. If a device advertises an optional part, it must implement that part exactly as the interface defines it. Devices may still expose additional fields and controls outside the minimum contract. Anyone controlling a domain can publish an interface in a namespace they own. Only Foundation-published interfaces use the urn:nfi: namespace.

​
Discover capabilities

For a standalone device:
For a node behind a concentrator, add its extended address:
The response lists supported URIs:

​
Aggregate interfaces

Aggregates add generic behavior to a base interface without multiplying definitions. For example, a historical-statistics aggregate can extend temperature, humidity, or power sensors. The aggregate’s version is explicit; the base version comes from the separately advertised base URI.

​
Consumer rules

  • Feature-detect every interface and version; never infer it from a model name.
  • Require the base interface before applying one of its aggregates.
  • Ignore unknown interface URIs while retaining them for diagnostics.
  • Negotiate a version you understand; do not silently treat a future major version as compatible.
  • Keep application policy separate from capability discovery. Support does not imply permission.