Skip to Main Content
Cumulocity IoT Feedback Portal
Status Planning / planned
Created by Juergen Hahl
Created on Feb 21, 2023

LWm2m: Avoid unnecessary unavailability alarms for LwM2M device

Description:
For LWm2m devices, the expected transmission interval (Required interval) is currently linked to the registration lifetime and it doesn't matter what is entered in the GUI, this value is always be overwritten by the "LwM2M Server Lifetime" object.
This means that the actual that parameters "Registration Lifetime" and "Required interval" (expected transmission interval) cannot be set for lwm2m independently of each other. This leads to thousands of unnecessary unavailability alarms in LwM2M in the field.
For example:
If you wants to monitor devices and record possible outages via a fault management and
unavailability alarm comes constantly, because the devices in the Nb-IoT do not send so reliably, this monitoring makes no sense.
In this case the acceptance for this alarm type is zero, since here simply the real circumstances are not taken care of.

As explained, the two parameters should be configurable independently of each other. Especially with regard to flexibility and, above all, practicality in operation.

Actual:

  • Parameters "Registration Lifetime" and "Required interval" (expected transmission interval) in CoT cannot be set for lwm2m independently of each other.

  • Thousands of unnecessary unavailability alarms in LwM2M are triggered.

After implementation of the AHA request:
Parameters "Registration Lifetime" and "Required interval" (expected transmission interval) can be set independently of each other for lwm2m.

Thanks

  • Attach files
  • Admin
    Oezge Akin
    Reply
    |
    Jun 13, 2024

    Hi Jürgen,

    Unfortunately this was delayed due to other priorities.

    We have decided to make this setting configurable in the device level (not tenant) since we have introduced LWM2M Configuration UI feature and LWM2M agent's LWM2M Configuration REST API endpoint starting from release 2024.

    This will be first made configurable using LWM2M agent's LWM2M Configuration REST API endpoint for release 2024.

  • Juergen Hahl
    Reply
    |
    May 27, 2024

    Hi Oezge,
    has the AHA request been implemented and do you have a release number for me .

    Thank you

  • Admin
    Oezge Akin
    Reply
    |
    Aug 18, 2023

    Hi Jürgen,

    We are planning on including this change in Q4 2023.

  • Juergen Hahl
    Reply
    |
    Aug 4, 2023

    Hello Oezge,
    is there a new status for this aha request and its implementation?

    Thanks for feedback.

    best regards
    Juergen

  • Admin
    Oezge Akin
    Reply
    |
    Mar 13, 2023

    We are currently considering the option of having a tenant level parameter (tenant options) to make the configuration. Also we have decided to backport this to 1015 once the implementation is done.

  • Admin
    Oezge Akin
    Reply
    |
    Mar 8, 2023

    Thanks for your feedback. We will introduce an optional field in LWM2M device registration to enable/disable setting of required interval based on registration lifetime. This will be included in the future releases.