-
### Clarifying the notify payload
The specification is not really clear about the notify payload, they say:
_The “Notify” operation is sent from the LWM2M Client to the LWM2M Server during a valid …
-
If the Client doesn't receive a Finish Bootstrap within EXCHANGE_LIFETIME (247s) of the last command from the server it needs to timeout and consider the bootstrap failed.
-
The description below is based on the current draft 1.0 version of the LwM2M specification (OMA-TS-LightweightM2M-V1_0-20170111-D).
Section 5.2.7.1 BOOSTRAP WRITE (side note: there's a typo in the …
-
The description below is based on the current draft 1.0 version of the LWM2M specification (OMA-TS-LightweightM2M-V1_0-20170208-D).
Hello again ;) We previously resolved an [issue with Access Contr…
-
OMA-TS-LightweightM2M-V1_0-20170111-D
Mentions in
> 7.1.3 X.509 Certificates
> The X.509 Certificate mode requires the use of X.509v3 Certificates [RFC5280].
> Certificates used in LwM2M SHOUL…
boaks updated
7 years ago
-
### Missing feature - LWM2M
LWM2M is currently not part of the NodeMCU software stack
### Justification
LWM2M is becoming more and more common for IoT to cloud connectivity. Multiple commercial …
-
5.3.1 Register
...
```
„However, devices might be hosting other Resources on an endpoint,
and there may be the need to place Objects under an alternative path.“
```
(How) does this feature combine …
boaks updated
7 years ago
-
Hi,
Before #299, I was adding custom Objects definition at runtime by providing a modified oma-objects-spec.json file.
Now, this does not seems to work anymore.
I provided the DDF file for my cus…
-
Switch to the master branch, and when integrated into Android, client can boot normally, but it cannot communicate with the server.
Here is my code
static NetworkConfig config;
…
-
Hi,
The OMA LWM2M enabler specifies that (see section 5.3.1):
> The payload Media-Type of that registration message MUST be the Core Link Format
> (application/link-format) defined in [RFC6690]
It …