Trigger and condition based on floors and areas

Feature Requests
1

Hi all,

Wouldn’t it be nice if we could be using floor_id and area_id alongside entity_id / entity in automations, scripts, conditions and conditional cards?

Now, if we want to see if all the lights are on in a specific room, we would need to create a template light for this, containing all the lights in that area. This could then be used as a trigger. Not only would this save a lot of extra entities with state changes, logbook, templating etc, it is also easier to control.

Example of situation now:

light:
- platform: group
  name: "Living Room"
  entities:
  - light.a
  - light.b
  - light.c
  - light.d
  - light.e
  - etc

automation:
- trigger:
  - platform: state
    entity_id: light.living_room
    to: "on" 
  condition:
  - condition: state
    entity_id: light.living_room
    state: "off"

Suggested change:

automation:
- trigger:
  - platform: state
    area_id: living_room
    domain: light
    to: "on" 
  condition:
  - condition: state
    area_id: living_room
    domain: light
    state: "off"

Cheers,

Douwe