Climate power off triggered by timer doesn't work properly

Configuration
,
1

Hi all!
i’ve 3 toshiba AC working in HA with toshiba integration.
i’ve created 4 timer helper so i can shut down the ac after a timer finish.
successively i’ve created an automation that call service climate.turn_off on my climate entity when timer.finished event occurs on these timer.

The automation works, but, after power off, the climate come back on in last state.

if i look at the automation trace i can see that the timer.finished event correctly invoked the power of, but a second after, the same timer finished invoke the power on state (in the last climate preset)

if i call the power off service via developer option this will not happen!

the climate power on is triggered manually trough the lovelace climate card, and the timer was stsrted manually in lovelace too.

here my automation code(i’ve create it trough ui, and try to poit the climate power off both on device or entity, with same result!)

alias: AC_OFF_studio
description: ""
trigger:
  - platform: event
    event_type: timer.finished
    event_data:
      entity_id: timer.ac_studio_30
  - platform: event
    event_type: timer.finished
    event_data:
      ententity_id: timer.ac_studio_60
  - platform: event
    event_type: timer.finished
    event_data:
      entity_id: timer.ac_studio_120
  - platform: event
    event_type: timer.finished
    event_data:
      entity_id: timer.ac_studio_180
condition: []
action:
  - service: climate.turn_off
    metadata: {}
    data: {}
    target:
      entity_id: climate.haori_studio
mode: single

here the automation flow from the ui (sorry it is in italian!)

Schermata 2024-04-17 alle 11.32.40
Schermata 2024-04-17 alle 11.32.40921×363 30.1 KB

Schermata 2024-04-17 alle 11.33.19
Schermata 2024-04-17 alle 11.33.19770×250 26 KB

i can’t understand why the climate come back on!!!
can somene please help me?

2

What came next in the logbook?

You have not shown the turn on entry in the logbook. Does that have any context?

My guess is that the turn off service failed but that is just a guess without seeing the logbook entry for it turning back on.

3

i was wondering the same…
what triggered the power on?

4

Hi @tom_l and @aceindy, there aren’t any other entry in the logbook after the state change to dry mode!

Schermata 2024-04-17 alle 12.52.11
Schermata 2024-04-17 alle 12.52.11842×482 29 KB

as i can see, the event timer.finished activate the climate power off, but after a second it activete the power on

5

integration issue?

Can’t help with this much more, as i don’t use the integration .
But since there is no log on the turning_on action, i suspect it is not an issue with HA, but the integration itself

6

yes maybe integration related issue, i’ll try to power on the AC and run the service climate.turn_off via developer settings after 30 min (the timer has a duration of 30 mins). i’ve tried to create a new timer helper with 1 minute duration, then i add this helper as a trigger to my previous automation and in this case the AC stay OFF!

7

i’ve done some other test! i’f i turn on the climate via lovelace climate card, and after 30 mins i call climate.turn_off service via developer tools the AC turn off and after a second come back on like with the automation!
This not happen when i call the service after a minute!

So i double the climate.turn_off call in my automation and now work!
this is the working code:

alias: AC_OFF_studio
description: ""
trigger:
  - platform: event
    event_type: timer.finished
    event_data:
      entity_id: timer.ac_studio_30
  - platform: event
    event_type: timer.finished
    event_data:
      ententity_id: timer.ac_studio_60
  - platform: event
    event_type: timer.finished
    event_data:
      entity_id: timer.ac_studio_120
  - platform: event
    event_type: timer.finished
    event_data:
      entity_id: timer.ac_studio_180
  - platform: event
    event_type: timer.finished
    event_data:
      entity_id: timer.test_timer_ac
condition: []
action:
  - service: climate.turn_off
    metadata: {}
    data: {}
    target:
      entity_id: climate.haori_studio
  - service: climate.turn_off
    metadata: {}
    data: {}
    target:
      entity_id: climate.haori_studio
mode: single
8

Looks to me like an issue with the integration (as there is no climate_on call in your automation)

But good find…:thinking: