Actually you can have both one parent Equipment and one parent Location.
This scenario is interesting and useful when you want to promote certain Points directly under the location to control a bit what is considered to compute the badges in the location cards.
When you have multiple “candidate” points with a given class/property, for example “Measurement/Temperature”, those points directly under the Location will be considered first. Only if there are no matches, those related to Equipment will come into play.
Example:
I have a window sensor and a motion sensor in the living room, both happen to have a temperature measurement point.
The motion sensor is away from openings, while the window sensor is - obviously - near the window and thus reports a temperature way lower than the actual ambient temperature in the room is.
I decided I want to consider the temperature of the room to be the one reported by the motion sensor (ZW074) because it’s arguably more accurate to the actual ambient temperature.
So I have added my temperature measurement to both the Equipment and the living room Location. You can see in Model treeview that when you select it it is recognized to be one single item (it appears twice but is also highlighted twice).
And in the semantic classification details you can see it has both “hasLocation” and “isPointOf” relationships:
So as said above, since I have a temperature measurement directly under my Salon location, in my card badge I will only see this one:
If I hadn’t “promoted” that item by adding it to the gSalon group, this is how it looks:
It took the 2 temperature measurements found under Equipment indistinctly, and shows the average (that’s how the badge works).
Hope that’s clear!