Skip to Main Content
Cumulocity IoT Feedback Portal
Status Added/Resolved 🎉
Created by Guest
Created on Nov 15, 2021

Mark LWM2M device with a new fragment "c8y_IsLwm2mDevice": {} instead of "type": "c8y_lwm2m"

The device type of newly created LWM2M devices is automatically set to

"type": "c8y_lwm2m"

Your support confirmed that this type must not be changed, otherwise it won't be treated as a LWM2M device in the platform. By having no option to change the type of a device, useful features do not work. For example default dashboards cannot be used as they are relying on the type. Also the device type filter of the firmware update feature is not working.

The problem is: Not every LWM2M device is the same device. We have for example many different device types, all communicating via LWM2M but all are of a different type having different features.

I would suggest to have a separate fragment to mark a device as LWM2M device. There is already the fragment isDevice{} indicating that a managed object should be treated as a device. The idea is to use for example the fragment c8y_IsLwm2mDevice{} to indicate that a device is communicating via LWM2M. By doing this the original "type" fragment can be used for something different.

  • Attach files
  • Guest
    Reply
    |
    Aug 16, 2022

    in which exact version of 10.13 is this implemented? 10.13.0.167 or....

  • Admin
    Nikolaus Neuerburg
    Reply
    |
    Feb 25, 2022

    This idea has been implemented and will be available with Cumulocity IoT 10.13 and higher.

  • Admin
    Nikolaus Neuerburg
    Reply
    |
    Nov 30, 2021

    Dear Dominik. Thanks a lot for the feedback. We do agree that for each device, the device type should be configurable by the user without this change affecting the device integration. Hence, we do plan to allow users to freely change the device type for LWM2M devices in Cumulocity. We will provide an update as soon as we can confirm the release version for which we do plan to implement this improvement.