Why does TimeSeries not extend from State and Command?

I’m trying to understand the new TimeSeries and wondering why it wasn’t implemented as a Type (from State and Command), that way it can be treated as such. I haven’t got the big picture yet here. By being a Type, it would simply be handled through item changed / updated / command events without adding a separate event type.

Equally, sending a TimeSeries to an item could simply be done using GenericItem.setState(), etc.

What makes TimeSeries so different that it requires a whole separate methods / events around it?

A State or Command represent a single current value at a defined (=now) point in time. The TimeSeries is composed of several states, timestamps and metadata (how to handle other values in that time-range) and is therefore largely different. What issues do you see with the way it is implemented now?

1 Like

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.