Heater
- Temperature
- °C
- R
- Setpoint
- 5 to 30
- RW
- Identify
- action
Pre-release
A bridge runs beside your equipment and only dials out. One definition gives each Thing REST, WebSocket, MCP and a Thing Description.

01 One control plane
A definition lists what a device can do and how the bridge reaches it. Nodelets gives every Thing the same interfaces from that one file, whether it speaks HTTP or MQTT.
PUT /nodelets/nl_4f2a…/properties/setpointobserveproperty temperatureread_property temperature"temperature": { "type": "number" }02 Nothing opened, nothing changed
No inbound port, new firmware, vendor gateway or hub. The bridge keeps addresses and topics on site, and the cloud holds what each device can do.
03 Clear limits
The cloud can call only what a definition declares. Each credential reaches only the Nodelets and operations it was given. Each command goes out once, and a failed one says what happened.
not-executedThe device didn't act. Nothing reached it, it refused, or a read timed out.
unknownThe device may have acted and nothing confirmed it. Nodelets says so and doesn't guess.
PERMISSION_DENIEDThe credential doesn't cover this operation. The cloud refuses it, and an owner can see the attempt.
04 What it doesn't do