While that syntax is apparently admissible, here I’m informed of yet another problem:
2023-10-04 20:44:02.828 [ERROR] [internal.handler.ScriptActionHandler] - Script execution of rule with UID 'test' failed: java.lang.UnsupportedOperationException: rrd4j does not allow querys without a begin date, unless order is descending and a single value is requested
On this, I really do not want to disgress from the subject. But it, frankly, doesn’t help to to imply with every other answer to a valid question of less experienced users that they aren’t reading the bible, while the bible may not be challenged. In this particular case. I have read the “documents” on the extensions, they provide a pseudo-syntax and no mention that they cannot be used in the most commonly used language JS Scripting., which - if I understand correctly - OH4 is now converging too.
What is then the correct syntax for using this extension?
as the two ones I tried out, do not work?
And it was, that’s how I came to discover that their is exactly zero information of what the 24 functions of the ItemHistory object actually do. This information, is - as mentioned - vaguely included in the API documentation. When using the syntax provided there with openHAB standard persistence service rrd4j, it gives you an error message that seems out of context.
I don’t want to get into a discussion on how to use this forum. But to me the problem doesn’t seem to be that users aren’t reading the documents, it’s that there is just too many non-updated pages in the documents and relevant information isn’t very logically distributed and more often than not leads to a dead end.
So i’m trying to rephrase my question again: Is there a (working) way to determine one of the many many JS Scripting functions or concepts and openHAB’s standard persistence service rrd4j, at what time(stamp) an Item was last changed ?
I can determine, when it was last updated – and the answer with rrd4j is - always - within the last minute, if the everyMinute strategy is active.
There are also two examples, however the first one could be updated with regards to the timestamp.