LwM2M server for DeviceChain
Constrained and cellular fleets often speak OMA LwM2M, a compact device-management standard over CoAP. DeviceChain terminates it directly: devices connect in over CoAP/UDP secured with DTLS, and their registration, telemetry and firmware map onto the same device model every other transport uses. The service is optional.
Authentication at the handshake
A device presents a DTLS pre-shared-key identity. DeviceChain resolves it to a tenant and a device before any application traffic flows, and an unknown or malformed identity fails the handshake. Tenancy comes from the authenticated identity, never from the payload. Roaming cellular clients are followed through DTLS Connection ID, so a session survives an address change.
The pre-shared keys are not part of the Helm release: the installer keeps them in a Secret and projects it into the service at start, so the chart values never show one.
Presence and telemetry
Presence follows the registration lifecycle: Register marks the device online, periodic Updates keep it alive, and Deregister or a lapsed lifetime marks it offline. DeviceChain observes the device's sensor object instances and decodes each Notify into typed measurements, so LwM2M telemetry reaches history, live state, dashboards and rules like any other reading.
Sensor objects are those in the fixed IPSO Smart Object range, observation is capped at 32 instances per registration, and neither is a setting. Management objects are never observed.
Commands and firmware
Platform commands become Read, Write and Execute operations on the device's resources. A command for a sleeping device is held durably and delivered on its next wake, within a bounded hold: if its time-to-live runs out first, it is not delivered. Firmware is updated by an operator sequence against the standard Firmware Update object, issued as ordinary commands in order.
What it does not do.
- Only SenML-JSON notifications are decoded, and only numeric resources become measurements. A conformant LwM2M 1.0-only client cannot produce SenML, so it registers, drives presence and accepts commands but reports no telemetry. Size this up front.
- A Write is limited to a single scalar resource, and a Read body over 8 KiB is truncated while the response is still reported as a success.
- Observations do not survive a failover: presence is rebuilt, and telemetry is re-established only as each device's registration renews.
- The firmware path is a runbook of commands, not a managed update job with artifacts and signatures.