Just to play devil’s advocate, what problem does this solve? In your rules do you need to know the difference between a location group and an equipment group? Are the location groups not already apparent based on their names without the letter signifier? And if not, isn’t it apparent by the tags? The same for equipment.
If it solves a problem for you so much the better. But as someone who used to have a similar naming convention for Items and Things, after years of maintaining it I’ve found that they serve almost no practical purpose. Pretty much all of the information conveyed by the letter prefixes is already apparent based on what I already understand about the Items (i.e. my mental model) and by using meaningful names for what the Item represents.
And if you move to creating and managing your Items through the UI the Item names become even less relevant. It’s the labels that the Items are listed by and sorted by and such.
However, there is one naming convention I would strongly recommend users adopt. When you have Point Items that are a member of an Equipment Group, prefix the Item with the name of the Equipment Group followed by a “_” and then what that Item represents. There are a number of reasons why this is a good idea:
- that’s how the Items are named by default when you create them from a Thing
- in custom widgets that, for example, use a bunch of Items from a single equipment (e.g. a single widget that includes the Image, player, app, artist and media title for a Chromecast), you can set a single property they the name of the equipment Group and reuse that widget for more than one Chromecast
- in your rules you can construct the names of related Items on the same equipment through a simple split on the name of the triggering Item
And if you plan on doing much with your Items on the UI, it is even more important now to use meaningful and unique labels for your Items than the name because the label is what’s used primarily in search and sorting.