Open LiveMike78 opened 3 months ago
Have been experiencing the same issue and in my case, it was the host's timezone that was causing the problem, it uses it for calculation resulting time instead of timezone configured in HA (as I assumed at first).
In the attribute "Next_alarms" for the next_alarm_time entity the first listed alarm has the correct time - for example "20 April 2024 at 07:20:00". However, in the next_alarm_time entity the corresponding time is incorrect - using the same example it would show "20 April 2024 at 08:20".