You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I seem to get the cheapest hours put on the wrong day (1.1.1970).
It also seems like our math between the me and the automation varies a bit. I don't know if it just default time in UTC (TZ: Europe/Helsinki) and it's completely confused, or what might be the case.
Expected behavior: Calendar event added for tomorrow (2024-11-09) between time 01:00 - 04:00 (localtime)
Result: Calendar event created for 1970-01-01 from 02:00 - 05:00
Anyhow, I've created a new (easier) approach for the cheapest hours so I don't really maintain this one that much anymore.
You might want to check out the new integration at https://github.com/kotope/aio_energy_management
I seem to get the cheapest hours put on the wrong day (1.1.1970).
It also seems like our math between the me and the automation varies a bit. I don't know if it just default time in UTC (TZ: Europe/Helsinki) and it's completely confused, or what might be the case.
Expected behavior: Calendar event added for tomorrow (2024-11-09) between time 01:00 - 04:00 (localtime)
Result: Calendar event created for 1970-01-01 from 02:00 - 05:00
Additional information:
Output of this step of the trace is:
The script as a whole is from repo:
The nordpool sensor has currently this value:
Current version:
Home Assistant
I think this broke few weeks ago and it has been just fallback that I've been given.
TTV 189 for reference.
The text was updated successfully, but these errors were encountered: