LwM2M: bootstrap
With bootstrap, your device only needs the bootstrap URI. It asks the bootstrap server for its accounts, gets the account of the LwM2M server and then registers there on its own. A device that bootstraps without encryption gets NoSec accounts; a device that bootstraps with DTLS gets DTLS accounts with its own key.
| Bootstrap URI | coap://164.30.75.205:5783 (NoSec) or coaps://164.30.75.205:5784 (PSK) |
|---|---|
| Security mode | NoSec, or PSK with a key from the Keys page whose identity is the endpoint name |
What your device receives
The bootstrap server first deletes the device's Security (/0) and Server (/1) objects,
then writes:
| Instance | Account | Content |
|---|---|---|
/0/0 | Bootstrap server | URI coap://164.30.75.205:5783, Bootstrap-Server true, security mode NoSec; over DTLS: coaps://164.30.75.205:5784, security mode PSK with the identity and key of the device |
/0/1 | LwM2M server | URI coap://164.30.75.205:15683, Bootstrap-Server false, security mode NoSec, short server ID 1; over DTLS: coaps://164.30.75.205:15684, security mode PSK with the identity and key of the device |
/1/0 | LwM2M server settings | short server ID 1, lifetime 300 s, binding U |
The device can change the lifetime and the binding in its Register message, and the lifetime later with a Write
to /1/0/1. Every bootstrap session with its steps is listed on the
Bootstrap page.