Automation not firing - help!

Configuration
1

Hey guys - I am trying to create a set of automations to control my thermostats, but none of them are firing. Below is one of them as a sample. Does anyone have any ideas why this wouldnt work? The YAML passing linting and HASS does not complain at all in the logs. I’m running 0.64.3 using the official Docker image

- action:
  - data:
      entity_id: climate.kitchen_thermostat_224
      temperature: '20'
    service: climate.set_temperature
  - data:
      entity_id: climate.home_theater_thermos_219
      temperature: '20'
    service: climate.set_temperature
  - data:
      entity_id: climate.basement_thermostat_209
      temperature: '20'
    service: climate.set_temperature
  alias: Turn on thermostats - weekends
  condition:
    - condition: time
      weekday:
        - sat
        - sun
  id: '1514360980746'
  trigger:
  - at: '08:30:00'
    platform: time
2

Any errors in the log?

3

None :frowning: and logbook doesn’t show them starting and they are enabled

5

You sure the action is not triggered? Or is it just doing nothing, because they are hidden errors in the actions? For example: Do the target temperature really needs to be a string (temperature: ‘20’)

6

These were built with the automation editor, but the conditions for weekday added manually - so I ASSUME, the fact that they use string is fine. As for if they are triggering, nothing is showing up in the logbook for them. I will set my logs to debug and see if anything happens.

7

I have a similar issue, also my automations won’t work. Mystery here is that they used to work, but after some update, they no longer worked. Workday_sensor is a custom component using workalendar to find out if it’s currently a local holiday or not, and that component is working as shoulds.
Here’s contents of my automations:

- id: '15150090066001'
  alias: Oikea tolppapaikka - ON
  initial_state: true
  trigger:
  - at: 09:11
    platform: time
  condition:
  - condition: state
    entity_id: binary_sensor.workday_sensor
    state: 'on'
  - condition: state
    entity_id: binary_sensor.holiday_sensor
    state: 'off'
  - condition: state
    entity_id: switch.right_car
    state: 'off'
  action:
  - data:
      entity_id: switch.right_car
    service: switch.turn_on
- id: '1516692766093'
  alias: Oikea tolppapaikka - OFF
  initial_state: true
  trigger:
  - at: 07:40
    platform: time
  condition:
  - condition: state
    entity_id: binary_sensor.workday_sensor
    state: 'on'
  - condition: state
    entity_id: binary_sensor.holiday_sensor
    state: 'off'
  - condition: state
    entity_id: switch.right_car
    state: 'on'
  action:
  - data:
      entity_id: switch.right_car
    service: switch.turn_off
- id: '1516693069695'
  alias: Oikea tolppapaikka - AUTO-OFF
  initial_state: true
  trigger:
  - entity_id: switch.right_car
    from: 'off'
    platform: state
    to: 'on'
    for:
      hours: 3
  condition: []
  action:
  - data:
      entity_id: switch.right_car
    service: switch.turn_off

There are 3 automations which should automate vehicle heating.
Right car on: if it’s a workday and clock is 5:00 - turn switch on (turn on heating).
Right car off: same conditions as right car on, but at 7:40, turn it off.
Right car auto-off: if switch(heating) is turned on manually, or even by automation, turn it automaticly off after 3 hours.

None of these events fire or show anything in logs.

8

Is the automation actually active? When was the last time it worked?

You also might want to consider to add initial_state: true to your automations.

9

I have made changes (and updated my previous post). Is there anything else to do to ensure that automations work as intended?

10

Did you check the state of those automation?

11

From dev states? All there seem to be on.

12

I’d look to the conditions and verify that your sensors are working properly and displaying the correct states. If those all look good, I’d check the switch and verify that it works as intended. Lastly, i’d check your system time.

13

All seems good now. Time is often updated from ntp servers and local time comes is derived from rtc chip, so all should be okay about time. Sensors return correct values and switch works.

Now I am testing it and I should see tomorrow if all works as intended. Maybe it was lack of initial_state…