I would suggest you rewrite it completely.
Your idea of having an automation waiting for hours is prone to not work.
Delaying can be done for a few minutes, but more than that is not recommended.
I think it might be something like this. I had a “wait” function before checking the dishwasher_gettin_hot and i think it waited too long. By the time dishwasher_gettin_hot started looking, the temperature was stable and not taking any readings, and then the first reading it took was already below -0.1. I’ve changed it so it waits less time and should take more readings and will be able to see the dishwasher_gettin_hot go from above 0 to below -0.1.
As I said. I do not recommend the method you use.
It will fail on you. It really will.
This is not an automation you can’t live without, and if it fails it really doesn’t matter.
But you should always think about not delaying for long periods when creating automations since a reload of the automations or restart of HA will break your automations.
Sorry for the long wait on response, new users can only post so much on their first day.
Ok so it was that I was waiting too long. Reduced the timer so the second trigger could get a few readings.
However took into consideration the comments about the long waits and decided to just split the automation into 3 stages. A trigger when it gets hot, a first stage complete when it cools down the first time (turns on a Boolean), and then a final cooling down
Mmm…
Can’t you change the trigger to below 0 for 30 minutes?
That is a very big improvement.
If you restart HA after 29 minutes then this automation will fail completely.
But with for 30 will just be delayed with 30 minutes.
Really?
Around here the plug is usually below the sink.
What he means is essentially create a fourth automation.
So stage 3 starts a timer for 30 minutes.
And stage 4 triggers on timer done.
That way each automation is very short in time, just the way they should.
And timers continue when HA restarts.