While the automation’s delay statement is counting down 20 minutes, Home Assistant must not be restarted, no automations should be reloaded and if you use the Automation Editor you must not create/modify any automations. If you do any of those things, it cancels all automations that are in progress and reloads all of them. That means the automation’s delay is cancelled and it never gets to execute the last two Device Actions.
Check the automation’s trace to determine if it actually executes the last two Device Actions.
If it does execute them, but the physical devices fail to turn off, there’s a problem with the transmission of the “turn off” command to the devices (might be a Zigbee integration/communication issue).
I believe the condition is wrong.
The trigger (time) has a start at 06:00… and everything next is supposed to act on that condition which is is placed between 0:00 and 0:00.
You should use Trigger ID’s. If something is on, than do this. If it’s off, do that… etc.
You’re right. The actions are already beyond the condition.
But a condition based on time stating before 0:00 and after 0:00 always make wonder what would happen. I would never use a condition like that.
After migrating from virtual box to a dedicated x86-64 machine i had the same problem with my automations. adding a delay also helped for me… strange though… it was just the switch.turn_off commands that were afected. turning off lights was working fine.