Trigger and action we have diffrent (yours look more complicated) but the condition is the same.
I have the problem with condition.
To make it more complicated. It dosen`t start only in the morning. When I turn on the air-conditioner then … during the day the automation works. It turns on and offe at specific temperature values.
Your problem is that it goes below 20 at night, then the condition prevents it from running, all good so far.
Then in the morning, it is already below 20 so it will not trigger again.
You need another trigger in the morning as @WebPower suggested.
Recommended solution would be to add time as trigger, for example at: 06:30.
But then also the temperature as condition, below: 20.
So if triggered by time, it checks if the time slot is valid (your original condition) but also checks if the temperature really is below 20 at that time.
If triggered by temperature below 20, it check if the time slot is valid but also double checks if the temperature is really below 20 which is not a problem.
Basically something like this and then your desired action after:
description: ""
mode: single
trigger:
- platform: numeric_state
entity_id: climate.daikin
below: 20
- platform: time
at: "00:06:30"
condition:
- condition: time
after: "00:06:30"
before: "00:22:00"
weekday:
- mon
- tue
- wed
- thu
- fri
- sat
- sun
- condition: numeric_state
entity_id: climate.daikin
below: 20
action: []
I’m on mobile so above is just a quick example to get you in the right direction