Skip to Main Content
Cumulocity IoT Feedback Portal
Status Planning / planned
Categories Data at Rest
Created by Peter Gaspar
Created on Nov 10, 2021

Digital Twin: Include last measurements and events in the managedObject of the device

To improve performance of dashboards, and to allow faster access to digital twin, it would be good, if for each measurement and event type, the last received object was also cached in the managedObject. In case new measurement/event of the same type is received, the old one would be rewritten.

To avoid caching unnecessary events/measurements, it would be good, if the types of events and measurements to cache in managedObject was configurable (like datapoints for example)

The feature is useful, if the current status of many devices is needed. With this we could avoid individual calls for last measurements and last events for each device (which can go into hundreds or even thousands of calls)

  • Attach files
  • Peter Gaspar
    Dec 22, 2021

    BTW, the map widget in a group would also benefit from this. We could adapt marker color or icon used based on last measurements (larger/smaller) or events (opened/closed)

  • Peter Gaspar
    Nov 29, 2021

    Hi Nikolaus,

    the main usecases for this are:

    • get all latest measurements for a single device in a single call

    • get all latest measurements for all devices within a group in a single call

    Not sure, how this can be done with a current API. The problem is not the response time of the current API, but the number of call. If a device has 10 possible measurements and a group has 50 devices, the second case takes 500 calls. This is a common case with for example the asset table widget.


  • Admin
    Nikolaus Neuerburg
    Nov 28, 2021

    Hi Peter, Dominik,

    thanks a lot for submitting the idea. Your main motivation for proposing this solution seems to be performance. Assuming the current APIs would retrieve results immediately, would this be an equally good solution for you?



  • Guest
    Nov 10, 2021

    When using LWM2M this something that is already working out of the box. It comes in really handy for many use-cases. Extending this to a more general solution for other communication mechanisms would be a very useful feature.