Numeric_state "Condition" FOR isnt working

Configuration
1 
- id: deactivate_bluetooth_sensors
  alias: deactivate bluetooth sensors
  trigger:
  - entity_id: sensor.home_occupancy_bridget
    platform: numeric_state
    above: '25'
    for:
      minutes: 2
  - entity_id: sensor.home_occupancy_benji
    platform: numeric_state
    above: '25'
    for:
      minutes: 2
  action:
  - service: shell_command.stop_bluetooth_18
  - service: shell_command.stop_bluetooth_19
  - service: shell_command.stop_bluetooth_20
  condition:
  - condition: numeric_state
    entity_id: sensor.home_occupancy_benji
    above: '25'
    for:
      minutes: 2
  - condition: numeric_state
    entity_id: sensor.home_occupancy_bridget
    above: '25' 
    for:
      minutes: 2

The following code isn’t working and im pretty certain that it is correct. Could someone verify that I am not doing something wrong please?

did some research and someone else posted the same feature but another user said it was a duplicate which it is not.

2

Things in quotes are strings. You want numbers for numeric_state.

You’ve also duplicated the triggers for the conditions, but according to the docs there is no “for” for the numeric_state condition currently.

If that duplication was intentional you’ll need to use templates instead.

Hope this helps.

3

Thats not the reason that it isn’t working… The single quotes are irrelevant in this situation. I have many Numeric_State and State triggers that have single quotes.

Its the FOR statement in the Numeric_State Condition that doesn’t work. Is this by design?

There is also nothin being duplicated. When you have multiple triggers they count as OR. So right now if the sensor says that Benji OR Bridget is home for 2 minutes the automation occurs.

When I stack multiple conditions like this it counts as AND. so basically Both have to be true. My issue is that since I cant add the For statement in the numeric_state CONDITION so right now only one person has to be home for 2 minutes rather than BOTH people

4

Re-read my reply, I can’t help you any more by repeating myself.

5

Is there a better way to do this that im just completely missing? Or do I just have no other choice but to use a template sensor?

6

Either a template sensor, or a template trigger/condition.

Or you can look at it from a different perspective and daisy chain a few bits together to get the same effect (like setting input booleans based on the triggers, and using them as the conditions)

I quite like doing the latter because I can visualise it better, but a lot of it is personal choice over ‘best practice’.

Based on the names of the sensors it appears this is an occupancy based logic, so numeric_state is not ideal and converting that to some kind of home/away (boolean or otherwise) early on is going to be a lot easier.

So, if it was me I would have an input_boolean that sets on for each of you when the numeric state is over 25 for 2 minutes, and off for whatever you use to define ‘away’, and then use the state of the input_booleans for the trigger and condition of the automation.

Hope this helps.