Automations combined with LG Aircon units

Configuration
1

Good day everybody,

I have been busy with automating my home for a few months now and I have to admit that I am a bit stuck now. After reading numerous topics, websites, mediums etc. I have to admit that I need help :slight_smile:

The problem

I live in a fairly old house (1950’s) and I have the luxury to have quite some flooring thanks to an addition from the 70’s. Unfortunately the heating system was designed in the 50’s and the placement of the radiators also. To have a comfortable house we first renewed the HVAC and placed a fireplace. Second step was to install AC’s on the three floors we have. We selected systems that could be controlled by HA and/or other apps.

The environement

Home assistant is running with the latest build (Core 2023.11.3 Supervisor 2023.11.3 OS 11.1) on a virtual machine. Dashboard etc. is working perfect.

The 3rd party devices
I am using a Lyric T6, 3 sensors (Generic Tuya, Wifi sensors) and 2 LG’s Airconditioners (S3M12JA2PA / S3M24K22PA).

The issue

I tried to automate a few things and it actually worked! I was able to turn the AC’s on at specific times. Nothing fancy here. I made four separate automations. Two for turning the AC’s off (Ground floor and First floor) and Two to turn the AC’s on. This worked perfectly! I even made some conditions in it (Only when temp sensor kitchen is below 19, only when AC is not turned on etc.)

Now I tried to be more clever and I wanted to turn the AC’s on at specific times in the morning and when the sensor of the first floor reported that the temp was 19C that the whole automation would switch to fan_only mode with the ionizer on. The last one just to spread the heat. This…worked…almost

Why almost?
The issue is with the controlling in the automation. It simply does this one time and then, when running the next time. I can’t change any state anymore. In other words. My setup is ending with fan_only mode, and no matter what I try. I can’t run the automation NEXT time on HVAC mode = heat.

I know the issue is here…me…I am doing something wrong, but I can’t find to understand what.

ps:
I have been reading - in the dark corners - all the time, so this is my first post and account. If I did something not correct, just let me know.

alias: "Eerste Etage : AC Aan"
description: >-
  Zet de AC aan wanneer de badkamer sensor een veranderende status heeft.
  (Temperatuur). Als deze temperatuur onder de 19 graden is, dan moet de AC
  aangaan.
trigger:
  - platform: time
    at: "06:10:00"
condition:
  - condition: state
    entity_id: climate.gryffindor_house_dormitory
    state: "off"
  - condition: time
    after: "06:00:00"
    before: "09:00:00"
  - condition: numeric_state
    entity_id: sensor.wifi_temperature_humidity_sensor_2_temperatuur
    below: 19
action:
  - service: climate.turn_on
    data: {}
    target:
      entity_id: climate.gryffindor_house_dormitory
  - service: climate.set_temperature
    data:
      temperature: 23
      hvac_mode: heat
    target:
      entity_id: climate.gryffindor_house_dormitory
  - service: climate.set_fan_mode
    data:
      fan_mode: HIGH
    target:
      entity_id: climate.gryffindor_house_dormitory
  - delay:
      hours: 1
      minutes: 0
      seconds: 00
      milliseconds: 0
  - service: climate.set_hvac_mode
    data:
      hvac_mode: fan_only
    target:
      entity_id: climate.gryffindor_house_dormitory
  - service: climate.set_fan_mode
    data:
      fan_mode: NATURE
    target:
      entity_id: climate.gryffindor_house_dormitory
  - delay:
      hours: 0
      minutes: 30
      seconds: 0
      milliseconds: 0
  - service: climate.turn_off
    data: {}
    target:
      entity_id: climate.gryffindor_house_dormitory
mode: single
2

As it stands, I think the automation will run once at 06:10 - that’s the trigger.

If you want it to do something else later when the temperature is 19C, that’s another trigger and you need either another automation or a wait for trigger action. Personally, I would go with another automation (with the time condition) - long delays in automations can lead to problems.

What’s a gryffindor? Just joking :grin:.

3

Ah yes! Forgot to mention that perhaps :slight_smile:

I have this automation running and after it starts it will be completed. The actual “shutdown” of the program is done via another automation. This automation works perfectly since it will check a state change from the temp sensor and when that’s the case shutsdown “gryffindor” when it is running.

For this specific automation there is no other trigger apart from time. When I wake up it should execute only 1 time.

The issue is more the following

  • system is running a program
  • this program ends with fan_only mode

The next time another program is started, I can’t get it from fan_only mode.

1 Like