Skip to content

Pre-release

A consistent control plane for the Internet of Things

A bridge runs beside your equipment and only dials out. One definition gives each Thing REST, WebSocket, MCP and a Thing Description.

Device tiles on one plane, connected by green lines to bridges below and to four interfaces above.

01  One control plane

One definition, four interfaces

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.

Heater

nl_4f2a…
Temperature
°C
R
Setpoint
5 to 30
RW
Identify
action
  • RESTPUT /nodelets/nl_4f2a…/properties/setpoint
  • WebSocketobserveproperty temperature
  • MCPread_property temperature
  • Thing Description"temperature": { "type": "number" }

02  Nothing opened, nothing changed

The bridge only dials out

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.

br_8k2mQf…ConnectedOutbound only

Heater

nl_4f2a…
Temperature
°C
R
Setpoint
5 to 30
RW
Identify
action

Light strip

nl_7a6e…
State
on, off
RW
Brightness
0 to 254
RW
Colour temperature
RW

Meter

nl_9c01…
Power
W
R
Energy
kWh
R
Reset
action

03  Clear limits

Nothing else can be called

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-executed

The device didn't act. Nothing reached it, it refused, or a read timed out.

unknown

The device may have acted and nothing confirmed it. Nodelets says so and doesn't guess.

PERMISSION_DENIED

The credential doesn't cover this operation. The cloud refuses it, and an owner can see the attempt.

04  What it doesn't do

Where Nodelets stops

  • It is not for control loops or safety functions. Every operation crosses the cloud, so those stay on the local controller.
  • It doesn't find devices. Each kind of device needs a definition, and a capability is never inferred.
  • It has two drivers, HTTP and MQTT. MQTT devices have properties only, with no live values, credentials or TLS yet.
  • It isn't generally available. Nodelets is pre-release and runs on staging.

Read how it works