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).
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 …
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 : -