Timed automations not triggering

Configuration
,
1

Hi-

I have been attempting to set up Home Assistant to manage a Powerley Zwave thermostat. I have gotten it to the point that I can change the temperature setting through HA using ZwaveJS. I would like to set up a simple timer through automations which I attempted to do through the HA UI. My problem is that the automations don’t seem to trigger at the set times, though. I can change the setpoint temperature by hitting execute on the automation in HA, so that part works, it just seems to be the trigger.

Can anyone see what my problem is? I have done a bunch of searching and see a lot of scheduling tools that seem more complicated than I need.

Here is the automations.yaml file:

- id: '1612888521572'
  alias: Wake up set heat temperature
  description: ''
  trigger:
  - platform: time
    at: 05:45:00
  condition:
  - condition: device
    device_id: 1efdce95056b29a0f7d9191d470dd12e
    domain: climate
    entity_id: climate.none_thermostat_mode
    type: is_hvac_mode
    hvac_mode: heat
  action:
  - service: climate.set_temperature
    data:
      temperature: 68
    entity_id: climate.none_thermostat_mode
  mode: single
- id: '1612888683942'
  alias: Bedtime set heat temperature
  description: ''
  trigger:
  - platform: time
    at: '22:30:00'
  condition:
  - condition: device
    device_id: 1efdce95056b29a0f7d9191d470dd12e
    domain: climate
    entity_id: climate.none_thermostat_mode
    type: is_hvac_mode
    hvac_mode: heat
  action:
  - service: climate.set_temperature
    data:
      temperature: 60
    entity_id: climate.none_thermostat_mode
  mode: single

I don’t know why the time has quotes in one case but not the other, I tried to set up the two the same way. Neither one triggers automatically.

2

Documentation says, time pattern needs to be in quotes.

1 Like
3

Do the automations work when you execute them manually?
When you go to Developer Tools -> Templates and enter the following:

{{ now() }}

does it show the correct time?

1 Like
4

Go to Developer Tools > Services and trigger the automation in the following manner. Don’t overlook to include skip_condition: false.

Screenshot from 2021-02-15 12-19-39

  • If it works then the trigger is at fault.
  • If it fails then something is wrong with either the condition or the action. Repeat the test but remove the line containing skip_condition: false.
  • If it works, the condition is at fault.
  • If it fails, the action is at fault.
2 Likes
5

Thanks, that narrows it down to the condition part.