Thanks for that. I had a read through of that, but can’t quite figure out how to apply it to my scenario. This one looks like he is trying to copy the state description of an item to apply it to another. I want to apply a new state description.
You also seem to use a more complex method than just using .updateMetadataValue. Is this necessary?
If you follow the link in that thread to the github issue, you will find 1) a discussion of how to add metadata config to an item config object which you should be able to replicate and 2) You will see that the issue has been recently closed because a very new PR has greatly improved the JSScripting metadata handling.
The slightly more complex example is certainly still viable and works for adding metadata in addition to updating. But, you can try the item config object method or try the newest JSScripting libraries (there are instructions somewhere here on the forum for how to update just the libraries if you don’t want to update to a recent snapshot, but I have never tried this).
Thanks, but I’m not sure I understand. I’ve read through all of this and am still very confused. Are these new changes you mention only a few days old? I’m using 3.4 now and don’t see any milestone updates available.
I don’t know if the itemConfig approach will work because I’d have to redeclare every property. I can’t just do
Yes. I suspect you need to be on a very recent 4.0 snapshot for these new metadata functions to be a part of the installed binding. But, as I mentioned, there are ways to install the newest version of the library that would have these changes without updating the binding. You’ll just have to search the forums for those library update methods if you want to go that route.
That is one of the new functions. Unless you have the newest openhab-js library you don’t have that function available to you.
In the OH core, the item metadata is all handled through the OH specific java classes. The first three lines of the example just import the metadata registry service and the underlying java classes that will be required to interact with the metadata service. Once you have all those pieces in place (which you only need to do once in a rule no matter how many times you then subsequently work with the metadata), the fourth line accesses the already existing stateDescription metadata for an item. The next line updates the pattern configuration in the stateDescription and the last line send the modified metadata back to the item via the metadata registry.
This is the most simplified version of these steps, not a recommendation that you use exactly those lines of code. For the most robust code you’d want to add some other pieces e.g., checks in case thestateDescription namespace hasn’t been added to the item yet.