Cumulocity IoT 2024 Q1 update

Cumulocity IoT has released many new capabilities during Q1 of 2024. These are made available as soon as the capabilities are ready, to all customers that are using continuous deployment (rather than using the annual release). You can refer to the full change log for more details.

​​​​​​​Highlights of the new capabilities introduced in Q1 of 2024 include:

Device replacement wizard. The Device Management application includes a new wizard that guides you through the steps for replacing a physical device. Learn more

X.509 certificate support has been added to LWM2M devices to provide an additional option for secure connections. Using X.509 certificates provides a variety of benefits such as eliminating the need to share private keys and being able to disable certificates. Learn more

LWM2M configuration tab helps you to more intuitively configure LWM2M devices and adds additional configuration options. Learn more

Bookmark your most used pages. Save time navigating and instantly access frequently used devices, files, groups, dashboards, etc. by adding items to your Bookmarks list in the right navigation bar. Learn more

Better visualize your complex asset properties in Digital Twin Manager by defining custom ordering using the new “Order” field. Learn more

Assign coordinates or a map location to your asset in Digital Twin Manager using the new “Location” property. Learn more

Create global Analytics Builder models. E.g., Use the new “All Inputs” as your input source to create a single model that raises alarms for any device where the temperature exceeded 100 (C). Learn more

Define selection lists for template parameters in Analytics Builder. You can now optionally provide users with a pre-defined selection list to choose from when creating instances of your Analytics Builder models. This helps you know what values the user can enter and therefore you can build a more robust model. Learn more

EPL app sample demonstrates how to receive and process update notifications. A common request from EPL developers getting started with Cumulocity IoT is how can my app be notified when a managed object is updated? A new EPL app sample shows you how to do exactly that. Learn more

Splitting of the Inventory permission into separate permissions for Binary and Managed Objects enables finer grained permission control for your devices. Learn more

Certificate Revocation List (CRL) can now be configured to ensure a device’s certificate has not been revoked during the device authentication process. This makes certificate management for your devices easier. Learn more

Cumulocity IoT Edge can be deployed and managed using Kubernetes. This removes the dependency on using a Hypervisor to run Edge and as a result improves resilience, resource usage efficiency, scalability and enables the use of the wider Kubernetes ecosystem for tooling and support. Learn more

EPL now includes a number of additional developer-oriented improvements:

  • EPL apps are more robust as a result of any exceptions thrown from listeners and stream listeners, which are not caught, no longer terminating the app/monitor instance. Instead, the app now simply stops handling the current event.
    App robustness is also improved due to EPL events no longer throwing exceptions from the isCreate and isUpdate actions. If these actions fail, they now simply return false.
  • Use + to concatenate a string and a non-string (e.g., float) now converts the non-string to a string and concatenates the two strings, rather than raising an error.
print “Welcome “ + 2024;
> Hello 2024
  • Many new convenience methods that make development easier have been added that can be used with strings, sequences and dictionaries. For example, the new getOr method on a sequence returns a default value if no value was found at the specified index.

mySequence.getOr(100, "default value");

  • Base64 string encoding and decoding using a new EPL plug-in to easily encode UTF-8 strings in Base64 format, and to decode them.


  • Manage unexpectedly large data responses from a server using the HTTP client’s maxResponseKB and maxResponsePolicy options to restrict the size of the server responses for either an individual request or for the entire transport.

Learn more