Cumulocity IoT Feedback Portal
Problem:
While connecting to the Bootstrap server, some of the configurations (Lifetime, pmin, pmax) are automatically sent to the devices, even if the were not specified during the device registration process.
This could lead to problem, for instance in case of some network issues. In that case, the Bootstrap server could alter some of the configurations of a device.
Solution:
The Bootstrap server should send these configurations, if they were explicitly configured during the registration process.
Another option would be to introduce null value to specify that the values should not be sent to a device.
Hi Attila, another site-note with regards to your comment: "In our case the request PUT /1/0 results in an error, since the device does not support the resource "Notification Storing When Disabled or Offline"."
It is our understanding that a device must support this request in order to be compliant to the LWM2M specification as this is a mandatory resource (https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/1-1_1.xml).
In the LWM2M 1.1 specification https://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf section 6.1.7.5. Bootstrap-Write Operation, you can also find: "The LwM2M Client MUST write the value included in the payload regardless of an existence of the targeted Object Instance(s) or Resource(s)"
Hi Attila, thanks a lot for the feedback! We agree that if the value for the bootstrap configuration is left empty, the agent default configuration should not be used and the value should be omitted instead. We will change the current behaviour with a future release.
Please see the attached file, to see the automatically sent bootstrap configurations in the request PUT /1/0.
In our case the request PUT /1/0 results in an error, since the device does not support the resource "Notification Storing When Disabled or Offline".