Whats wrong with this ez automation?

Configuration
1

Hi guys, I have this automation to turn on my AC when above 26 degree or 60% humidity:

alias: Accendi clima salotto quando caldo o umido
description: >-
  Quando la temperatura raggiunge i 26 gradi o quando l'umidita va sopra i 60
  accende il clima
trigger:
  - platform: numeric_state
    entity_id:
      - sensor.livingroom_office_temperature_mean
    for:
      hours: 0
      minutes: 5
      seconds: 0
    above: 25.9
  - platform: numeric_state
    entity_id:
      - sensor.salotto_ufficio_umidita
    for:
      hours: 0
      minutes: 5
      seconds: 0
    above: 60
condition: []
action:
  - service: switch.turn_on
    target:
      entity_id: switch.livingroom_plug_mitsubishi
    data: {}
  - service: climate.turn_on
    target:
      entity_id: climate.livingroom_air_conditioning
    data: {}
  - service: climate.set_swing_mode
    target:
      entity_id: climate.livingroom_air_conditioning
    data:
      swing_mode: swing
  - service: climate.set_fan_mode
    target:
      entity_id: climate.livingroom_air_conditioning
    data:
      fan_mode: "1"
  - service: climate.set_temperature
    target:
      entity_id: climate.livingroom_air_conditioning
    data:
      temperature: 26
      hvac_mode: cool
mode: single

It doesnt work, could be the mode: single?
I insert 2 trigger so if temp is below 26 but humidity goes higher it will turn on or vice-versa.
Thanks for help

2

A Numeric State Trigger will trigger when the monitored value crosses the threshold value.

The temperature has to change from below 25.9 to above 25.9 to trigger it. It’s the crossing of the threshold value (25.9) that causes it to trigger.

If the temperature is currently above 25.9, it won’t trigger until it first decreases below 25.9 then increases above it.

It works the same way for the Numeric State Trigger monitoring the humidity.

Reference

Numeric State Trigger

image
image695Ă—146 24.7 KB

3

Yes, thats what I want. When crossing that value it should turn on my AC and lower that values… But it doesn’t… So the mode isn’t a problem?
I’m doing a test with a light

4

If either the temperature or humidity crossed its threshold value then it will have triggered the automation and produced a trace. Check the trace to determine why it failed to control the AC.

If there’s no trace then it’s highly likely that the automation was not triggered.

The automation’s mode is not an issue for this particular application (single is fine).

5

I tested manually, the first one is temperature, when my hand hold it and goes above it get triggered.
I did the same test for humidity and when it crosses the threshold nothign happens. In this case the temp was above 27. Its like that check the first trigger and if it is already satisfied didnt check the second one.

image
image1218Ă—655 28.1 KB

6

It did work now…
Its a mistery… I will try again with the AC and checking the traces.
If I put restart on mode what will be different, the doc isnt super clear to me

7

That isn’t how it works.

Can you post the history graph for your humidity sensor where you think it crossed the threshold? Is it possible that its state is from 0 to 1 and you have it displaying in %? In that case, the trigger point would be 0.6.

8

No no, its int with 2 decimal.
Its fine now, I tested both manually, probably I did change the entity name cause I noticed that one was called sensor.blabla, usually this happens when the names are wrong :slight_smile:
Thanks for the fast reply

2 Likes