Cumulocity IoT Feedback Portal
This is for Battery Powered devices. Conversion of Empower ticket to AHA
https://getsupport.softwareag.com/servicedesk/customer/portal/2/SI-562837
C8Y.lwm2m.operationMaxAgeHours: would be possible to segregate operations timeouts and have a dedicated parameter for FW DL operations, not affecting other type of operations, would SAG be keen to put such a feature on the roadmap ?
“I heard back from R&D: Yes sure. We'll implement another config parameter specific to the FW DL.
Regarding the first point, your understanding is correct. For our test, we used californium3.properties.COAP.BLOCKWISE_STATUS_LIFETIME=2000000 (in milliseconds). So this timeout is a little more than 1800 seconds (30 minutes) which is our expected maximum delay between 2 BLOCK2. So depending on the expected max delay between two block transfers the customer has to set a value. The value doesn't represent the entire session here.
C8Y.lwm2m.operationMaxAgeHours is related to the whole firmware update operation. When you start a firmware update from C8Y, an operation is created which is then picked up by the lwm2m agent. This operation stays as EXECUTING until the device doesn't send a successful result (i.e. until 5/0/5 reports a value 1).
Please refer to this image. The operation was created on 5th July and set to EXECUTING state when it started and finally on 9th July it was set as SUCCESSFUL when the whole firmware update was completed.
