There is no right it wrong in the model beyond using tags that don’t exist or trying to put the same item in miss more than one semantically tagged Group. So there is no should. You need to do what makes the must sense to you.
Anyway, at this point all I can tell you is that it can work. Beyond that it’s starting to look like .things files, trying to get it right it’s going to be a huge time sink. I’ve all my Items defined in the UI so can’t provide much more on. items files beyond the fact that others have made it work so it can work.
You can’t mix and match points and properties. I don’t think there is a Battery Point type nor is there a measurement property. The “rules” are:
-
Locations are a Group with a single Location tag and only a single Location tag.
-
Equipment are a Group or an Item with a single Equipment tag.
-
Points are an Item with a single Point tag and an optional Property tag.
You can’t have two property tags. You can’t use a property tag with a location or an equipment tag. You can’t have just a property tag.
If you look at the medel page of the Getting started tutorial you will see which tags are which.
I think that was mentioned at some point but it won’t apply to .items files if it does get implemented. As has always been the case, what’s in files overrides what gets autodiscovered or done through the UI.
Text configs are still very much supported, but as has always been the case, when you use text configs you have to do it all.