I am looking for ideas for the organisation of dashboards and views for Lovelace. I have to organise a property with 2 buildings, 5 apartments and a large outdoor area. There are about 40 entities spread across the premises.
My initial thought was to have one dashboard per entity type (light, switch, sensor) and then one view per apartment and for outside. But the relations would be lost, e.g. that a motion sensor activates a light via a switch.
Alternatively, there could be one dashboard per apartment, each with one view. But especially outside, there are of course motion sensors that (also) switch lights on different apartments. These would not appear or would have to be listed twice.
And both approaches do not take into account that there are also administrative entities, such as input helpers, statistics sensors, etc.
How have you addressed comparable situations?