Aggregation and realtime conflicts to each other. If you want to see realtime data you see what is delivered by the device (pushed to the UI). If you select any aggregation the UI will select only historic data and aggregates it according to your selection (pulled from the API). Again, this won’t work on realtime data which is just received by the device.
Possible solution: Use streaming analytics and aggregate the values in a new measurement. Each time the measurement is updated it will be pushed realtime to the UI (with aggrgated data).
We would like to have a bar per day. Each new incoming measure (created using streaming analytics) should increase the existing bar, if necessary, not to create a new bars next to each other. So we would like to have something like this:
Sure, multiple ways how to achieve that. For each measurement you could accumulate the daily value starting from 0 each day and updating it in the managed object, temporary event or measurement. Another model could listen for this temporary event/measurement, latch it and when a cron timer trigger fires (both inputs are true) once per day the latest accumulated value will be written to a daily aggerated measurement (only one value per day).
I’m not the expert here, so maybe someone else has a better idea.
