I’ll edit the topic subject line, done.
Thanks again for clarifying this. I looked at the source code but couldn’t find it anywhere. I thought that some components (e.g. the GUIs) are able to access it somehow, but it’s definitely not clear how to do it from within a rule
This feature would be really helpful in many cases - e.g. when notifying someone/something. Why would the sitemaps/GUI have exclusive access to this information? It is even specified in the .items files (as well os the icon). I reckon the label should probably be readOnly due to context issues see this discussion.
The workaround is hard coding the item label string in the rule for every single item, meaning you now have two places to maintain the same string.
Also take the example of an item group of some kind of status (temperature, battery level etc.) at different rooms/locations. It would be handy to be able to make a single rule, iterating through the items and notifying someone (using item label) on some criteria.
This leads me to another nice-to-have: The possibility to make a rule which is executed upon a change to one of its members and additionally giving access to the specific member.
I do not agree. To me it is clear that it should be the one specified on the item (if specified). The same goes for the icon. The sitemap is context specific and just a presentation that may or may not override the item label. Items can exist in many sitemaps as well.
Yes, it can be done by work-arounds, but it is not a pretty solution. My point being that internally the group update is initiated by an item, so the information is available already. Just need to be forwarded as a variable on the group item (eg. lastUpdatedItem)