> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neuro-tech.io/llms.txt
> Use this file to discover all available pages before exploring further.

# IoT device model

> Map things, identities, sources, nodes, sensors, actuators, and operations

## Concepts

| Concept             | Meaning                                                                |
| ------------------- | ---------------------------------------------------------------------- |
| Thing/entity        | A physical device, virtual device, service, or application             |
| Network identity    | Address used to communicate, normally an XMPP JID                      |
| Conceptual identity | Persistent identity of the thing independent of a connection           |
| Data source         | A named source tree exposed by a concentrator                          |
| Node                | A physical or virtual item inside a data source                        |
| Partition           | Optional discriminator when node IDs are reused in separate partitions |
| Sensor              | Exposes read-only fields over time                                     |
| Actuator            | Exposes writable, typed control parameters/actions                     |
| Concentrator        | One network identity that contains many sources/nodes                  |

A standalone device uses its JID as the address for sensor/control operations. A concentrator operation adds source ID, node ID, and optional partition.

## Capability discovery

Query capabilities before calling an interface. A concentrator can expose sensor data, control, node management, commands, queries, events, and troubleshooting features independently.

## Extended addressing

Use this tuple as a stable node address inside a concentrator:

```text theme={null}
(Concentrator JID, Source ID, Node ID, optional Partition)
```

Node display names and positions are not identifiers. Persist the full tuple and be prepared for a node-moved event.

## Harmonized interfaces

Basic sensor and control models enable human UIs. Harmonized interfaces add agreed machine semantics for a use case. A device advertises the qualified interface identifiers it supports, allowing cross-vendor applications to interpret data without model-specific code.

## Bridge pattern

A protocol bridge maps Modbus, MQTT, HTTP, GPIO, files, or another local technology into this model:

```text theme={null}
Protocol device -> bridge node -> sensor/control interface -> XMPP federation
```

Keep protocol-specific identifiers as metadata, while exposing stable Neuro source/node IDs to clients.