Automation triggers don't go after manual stop switch

Configuration
21

By default the conditions are always ‘anded’ together, the automation editor is verbose but I suppose that it does give people an idea how to nest conditions into multiple ands/ors or groups of both.
So it is correct (but mines not wrong, just hand coded to have what is required only - notice how much more compact mine is). And I’ve put the extra trigger in for the time start as yours would not have triggered from 15:59 had it been already below 18 degrees and power below 1600.
Also I have listed the entities in a structured manner rather than just alphabetically, makes it much easier to read and maintain.
“-” the dashes, show list items and they are written to show what they do.
This is much easier to maintain, but probably will not survive further AE mangling.
Do you know how to paste this into your automations ?

Note: if at (say) 16:10 the temp is still below 18, power below 1600 and you THEN turn the switches off, they will stay off until one of the conditions crosses a trigger threshold again. This is why I wanted you to check what else was switching stuff off.
We ‘could’ get round this by just firing the automation every minute and have it then check the conditions, but this is a failure / get out of jail / poor coding technique.

Should I do the same for the off automation?

Just making sure - you have reloaded the automations before each test haven’t you ?
Also, what does your config check say ?

Side note: the above 0 wasn’t doing anything (as I tried to imply earlier).

22

Yes, yes, thanks, I just edited them but when I restart hassio it tells me that they are not correct.

23

Okay , so it passes config check but HA (hassio is the docker environment) complains ???
I don’t understand

Try cut and paste what config check says and any error messages on a restart

(why are you restarting ? Relaod automations should be sufficient).

Here is the off auotmation, yours had anded conditions (won’t work)
And you don’t really need time conditions as switching off is valid any time

- id: '1578344146920'
  alias: SPEGNI RISCALDAMENTO NOTTE
  description: ''
  trigger:
  - platform: numeric_state
    entity_id: sensor.aeon_labs_zw100_multisensor_6_temperature
    above: '18.2'
  - platform: numeric_state
    entity_id: sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_power
    above: '2900'
  - platform: time
    at: '08:59:00'
  condition:
    condition: or
    conditions:
    - condition: numeric_state
      entity_id: sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_power
      above: '2900'
    - condition: numeric_state
      entity_id: sensor.aeon_labs_zw100_multisensor_6_temperature
      above: '18.2'
  action:
  - service: switch.turn_off
    entity_id: switch.fibaro_system_fgs223_double_relay_switch
  - delay: '00:00:59'
  - service: switch.turn_off
    entity_id: switch.fibaro_system_fgs223_double_relay_switch_4
  - delay: '00:00:59'
  - service: switch.turn_off
    entity_id: switch.fibaro_system_fgs223_double_relay_switch_3

power - 1600 to 2900 is a big jump, can you remind me why it’s okay to be cold if your current usage is high ?

24

Yes Hassio.
The following components and platforms could not be set up:

Please check your config.

25

or give a screen shot

26

2020-01-09 21:32:59 ERROR (MainThread) [homeassistant.config] Invalid config for [automation]: [conditions] is an invalid option for [automation]. Check: automation->condition->0->conditions. (See ?, line ?). Please check the docs at …

27

If I write this is correct:

- id: '1578343605997'
  alias: ACCENDI RISCALDAMENTO NOTTE
  description: ''
  trigger:
  - platform: numeric_state
    entity_id: sensor.aeon_labs_zw100_multisensor_6_temperature
    below: '18'
  - platform: numeric_state
    entity_id: sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_power
    below: '1600'
  - platform: time
    at: '16:00:00'
  condition:
    - condition: numeric_state
      entity_id: sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_power
      below: '1600'
    - condition: time
      before: '8:59:00'
      after: '16:00:00'
    - condition: numeric_state
      entity_id: sensor.aeon_labs_zw100_multisensor_6_temperature
      below: '18'
  action:
  - service: switch.turn_on
    entity_id: switch.fibaro_system_fgs223_double_relay_switch
  - delay: '00:00:59'
  - service: switch.turn_on
    entity_id: switch.fibaro_system_fgs223_double_relay_switch_4
  - delay: '00:00:10'
  - service: switch.turn_on
    entity_id: switch.fibaro_system_fgs223_double_relay_switch_3

But does this only work if all conditions occur together?

28

In my opinion it is more correct with “AND” … am I wrong?

- id: '1578343605997'
  alias: ACCENDI RISCALDAMENTO NOTTE
  description: ''
  trigger:
  - platform: numeric_state
    entity_id: sensor.aeon_labs_zw100_multisensor_6_temperature
    below: '18'
  - platform: numeric_state
    entity_id: sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_power
    below: '1600'
  - platform: time
    at: '16:00:00'
  condition:
    condition: and
    conditions:
    - condition: numeric_state
      entity_id: sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_power
      below: '1600'
    - condition: time
      before: '8:59:00'
      after: '16:00:00'
    - condition: numeric_state
      entity_id: sensor.aeon_labs_zw100_multisensor_6_temperature
      below: '18'
  action:
  - service: switch.turn_on
    entity_id: switch.fibaro_system_fgs223_double_relay_switch
  - delay: '00:00:59'
  - service: switch.turn_on
    entity_id: switch.fibaro_system_fgs223_double_relay_switch_4
  - delay: '00:00:10'
  - service: switch.turn_on
    entity_id: switch.fibaro_system_fgs223_double_relay_switch_3
29

As I said there are multiple ways of doing things, you have to go with what you are happy with.
I did get some lines out of order, I’ve checks with the docs : -


And I have corrected the automations above
30

Great I corrected everything thanks!
Now let’s try it and see what happens.

31

Just check config then reload automations.
I said I’d corrected them but it was done a couple of minutes after that, so make sure you have the latest