When an SVG constructed in this manner is added to a web page, then those individual groups or “sprites” can be referenced in-line as their own elements in the page. The drawing elements in an SVG file can be grouped together in mostly arbitrary ways, and these groups can be given unique identities. This icon library system is based on SVG sprites. The icon display widgets themselves can be used anywhere the oh-icon and f7-icon components can be used in custom widgets. They can also be recolored just as the f7 etc. As they rely exclusively on the widget system, these libraries can be shared in the widget marketplace. Here I’m going to go through a mechanism to define an entire SVG icon library using only two MainUI custom widgets (one for the library and one to display the icons). These custom icons, however, have a few limitations: most notably that unlike the other new icon sets, these icons cannot be recolored by the user in the widgets. For example, my sonos speakers use a custom SVG icon that can be set as the default icon for an item: In these circumstances, OH gives you an ability to add your custom icons to the system to be called just as any of the other OH icons are. Even so, there are still times when only a custom icon will do. The MainUI devs have done an amazing job making sure that when making your own custom widgets, you have access hundreds of possible icons, with the moderately recent addition of the iconify resource pushing that into the thousands.

Where is icon set in openhab