Human interactions

[analog tide]

I want to count the number of human interaction per area or per label to execute actions over or under limit:
Exemple: if no one has been in first_floor for 20 minutes switch off all lights, reduce temperature.

A human interaction is either a press on a switch, a movement before a movement detection, a physical change of thermostat temperature...

So far I am planning to filter out all events to keep only the relevant human interaction event.

Is there a smarter way to do it ?

[worthy goblet]

Via tags?

[sick tusk]

I'm curious how would that work?

[worthy goblet]

Tags or labels in the devices you want to control, I see the AO says that also

[sick tusk]

can you give an example please, or elaborate more? Your short answers are not so easy to understand

if I label the devices with an area name, how do I perform the automation to have the "no activity for 20min" for example?

[worthy goblet]

I'm sorry, it's an idea, I don't know if it's posible, but I'll dig into that way

In my case, for something similar, I have multiple triggers, the traditional way, I don't mind enter it one by one 🤷‍♂️

But as I said, if I wanted to do it in more elegant way, I'll try what I said, if it's posible, that I dont really know

[lavish sinew]

Wouldn't presence detectors be better for knowing if someone is in a room/floor? If you want to do it for an entire floor, make an aggregate sensor Floor Occupied that's an Or(Room1sensor.occupied = true, Room2sensor.occupied = true, etc)

For example, if my wife sits down to read a book in the living room, she might not move for an hour. A mmWave sensor would still know she's there, so it'll keep the lights on, but, she's not going to be hitting the light switch or adjusting the thermostat every 20 minutes because there shouldn't be a need for her to. If I expect her to do so, she's going to rip all the automated stuff out and throw it in the street!

[analog tide]

Hey, thanks but no idea fits my need. Of course in an ideal world there are mmWave sensors everywhere but this is not the case.
There is a bridge between the real world and the ha world and I cannot figure how to simply understand how to segregate events from real world from the others. I now doing it through appdaemon filtering events but I feel it should be something simpler.

- type: shelly.click
  filters:
    device: "shellyswitch25-E09"
    click_type: "btn_down"
  friendly_name: "inter et1_intdbl_entree_haut"


# Binary sensor state changes
- type: state_changed
  filters:
    entity_id: "binary_sensor.shellyswitch25_40f8f_channel_1_input"
  friendly_name: "inter et1_int_wc 1"