19.03.2022, 07:44
(This post was last modified: 19.03.2022, 07:48 by Erwin van der Zwart.)
Difference is that objects can only hold a single value, storage can hold tables so depending on your task you might need to use storage.
From performance you need to use virtual objects otherwise the values are processed for sending to the KNX interfaces and that uses recourses.
I think storage or virtual objects are using the same amount of resources but admin might correct me ?
The biggest difference is that you can see the objects and the values in the objects tab or even on your visu if needed, storage is only visible by using log() or the storage viewer app.
Both methods are running in RAM and are stored on SD by the save interval, so both are save to use with persistent / high speed writing.
From performance you need to use virtual objects otherwise the values are processed for sending to the KNX interfaces and that uses recourses.
I think storage or virtual objects are using the same amount of resources but admin might correct me ?
The biggest difference is that you can see the objects and the values in the objects tab or even on your visu if needed, storage is only visible by using log() or the storage viewer app.
Both methods are running in RAM and are stored on SD by the save interval, so both are save to use with persistent / high speed writing.