Those two times appear to be valid so we know that the system clock and timezone are correct. In other words, they will properly trigger a Time Trigger and Sun Trigger.
i edited the “off” automation at 6:15 to trigger at 6:45 and it just triggered as requested. Perhaps the “on hour” doesn’t work ? i will try to edit it for :5:45 tomorrow and see if that works better… and keep you updated if i still have issues
The fact it worked but only after you changed the time implies there’s something not quite right but what exactly is unclear. Effectively, the automation worked after it had been modified and saved.
Did you originally create the second automation using the Automation Editor or with a text editor? The reason why I ask is that if an automation is created or modified with a text editor, the changes aren’t registered until the automation integration is reloaded (Developer Tools → YAML → Reload Automations).
How do you have HA installed? There have been quite a few issues in the past with accurate time-based triggers on systems that used certain VM software. It often boils down to an issue with either the lack of an RTC, issues with Network Time Protocol, or incorrect paravirtualization settings.
FWIW, the OP had mentioned using a VM so my first question was to have him confirm that current time and next_setting time are correct. Apparently they are correct which adds to the mystery of why two time-related triggers are either misbehaving (triggers at sunset but without the offset) or failing (doesn’t trigger at 06:00:00).
Especially odd that the Time Trigger started working after its time value was modified. This isn’t behaving like a healthy system.