openHAB 5.1.1 (not sure if this is important or applies)
Openhabian RP8 5 8 Gb
openHAB has a standard for accessing icons where the syntax is
service:category:iconName
Example iconify:solar:bluetooth-circle-bold-duotone
As it turns out the standard openHAB location “/classic” for icons also seems to correspond to oh:classic:iconname
It also appears that if a folder is created under icons folder e.g. “custom”
And icon called myicon.png can be referenced as oh:custom:myicon
This is great for installing bundles of icons and uncluttering the standard /classic but before i proceed with this i would like to confirm this functionality is the supported and expected behavior that will be provided as part of openHAB going forward and not just a side effect of the existing implementation.
What you describe seems to match what the docs say:
Icon sources
Some user interfaces supports other icons than those provided by openHAB. Thus, the most generic reference to an icon is composed of 3 segments separated by a colon:
The first segment is the icon source, e.g. “oh”
The second segment is the icon set from this source, e.g. “classic”
The third segment is the name of an icon in this set, e.g. “switch”
If the value contains only two segments, the first segment is assumed to be the icon source and the second the icon name. In this case, the icon set is to “classic” by default. This is used in particular when the icon source only provides a single set of icons. As an example, <material:favorite> references the “favorite” icon from the Material icons. <oh:switch> references the “switch” icon from the openHAB classic icon set.
If the value contains only one segment, it is assumed to be the name of an icon from the openHAB classic icon set. As an example, <switch> references the “switch” icon from the openHAB classic icon set.
That’s a pretty good indication it’s working as you describe by design. If it does change, usually the developers will go to great lengths to keep the old way working for something like this.
