Open mhilbush opened 5 years ago
I see many problems with this schema that need to worked out....
For instance, with locations. There are 2 intermingled concepts -> the actual location of the room and then the room type.
Additionally, do we need to list all permutations where a room/location can be located? Ie if we define porch which is a covered shelter as part of a building do we need to define front and back porches? What about if there are side porches? And how do you identify the side (north, south, west, east OR left right). Do we need even want to go down this route of identifying all the possible locations of a room/area/location?
I am not even sure that room is the right verbiage to use. It implies there are walls, ceiling, floor and doors. What is there is a large room ie like a great room, which often encompasses a kitchen, eating area, and TV area in one?
I think this is extremely important to get right. It will allow for more generic rule and automation functionality.
Mike
+1 for the "Driveway" Location. Very common in the UK, and may have lights or automatic gates.
I'd also like to suggest some new Properties too:
Over the past couple days of using HABot and adding tags to my items, I've created a list of tags that I'm proposing adding to the semantic tag library here.
I'm sure other may have suggestions as well. Please advise on how to proceed.
Locations
Properties (a number of my Z-Wave sensors produce these)
Equipment
Points (seems like there's a need to differentiate between heating and cooling setpoints)