The unit of presence on the mesh. Identified by a DIN (device id) within an SID (segment id). Owns drivers and the routing table.
A transport binding — INET4, BLE, and more. Nodes can hold several and fail over between them automatically.
The Device Data Object: a compact typed datagram (≤32 B header) with a typeset, payload and routing metadata.
Register a callback invoked whenever a DDO addressed to this node arrives, after routing and de-duplication.
Emit a DDO towards a target DIN. The mesh handles discovery, routing and retransmission.
Bring the node online or take it down cleanly, releasing drivers and de-registering from the segment.
Full method signatures and per-language notes live in the docs.
Read the Guides