Open mazzy89 opened 3 years ago
The bug seems that is due to the fact that the calculation is done looking at the tree on the same day. Approaching the end of the day, however, we should make a request to the next page (zitra) and find the right value.
I know that it's not a huge bug because the next day the sensor should pull the right value.
Thanks for reporting the issue. This fix requires major code change. I will keep this issue open.
No problem. I'm actively using this custom components. Overall it is working. It's not a big deal for the moment because it happens only at the end of the day.
I've noticed an error in the calculation. This screenshot is taken at 22.02 UTC+2
It says that the next tariff is in 1420 minutes which does not make much sense because it should be according to the schedules 00:20/01:00