September 18, 2025 - LWM2M service utilization of Notifications 2.0 tenant-level operation subscription

Cumulocity Change Log Device Management & connectivity
, , ,
1

Context

Change Type: Feature
Product area: Device management & connectivity
Component: LWM2M
Deployed at: eu.latest.cumulocity.com, apj.cumulocity.com, jp.cumulocity.com, cumulocity.com, us.cumulocity.com

Technical details

Build artifact: lwm2m-agent (1021.10.30)
Internal ID: DM-4867

Description

The LWM2M service is now utilizing Cumulocity’s Notifications 2.0 tenant-level operation subscriptions to retrieve device operations in real time. This enhances the service’s overall performance.
Note that when this mode is active, device push connections will no longer appear as active in the Info tab of the device details.
This is because they are now managed through tenant-level subscriptions rather than device-level subscriptions.

2

That’s by the way I tried to address some time ago. It would be nice to at least have an option at Notification 2.0 to define if the push connection status should be updated or not when doing a MO-scoped subscription.
Only workaround I’m aware of is to actually establish a connection to the MQTT Endpoint in parallel and create a subscription, which is not very nice.