Next runtime zeigt "gestern"
jellyneck84 opened this issue · 10 comments
Sorry, my German is very bad, can you translate for me.
Cheers Pete
Ok thanks, I thought that this issue was fixed, I will look into it, I am getting inconsistent results.
What hardware are you using? Raspberry pi?
Has the train sensor been active? This was the mode where the next run was not recalculated when the zone was not run.
@petergridge I'm using a rasperry pi, yes.
What do you mean with "train sensor" ? Or do you mean rain sensor?
It seems the time is correct, when the next run is on the same day, because this morning the time was then displayed correctly "Next run: in 9 hours". But yesterday evening, as you can see in the screenshot, it showed "Next run: yesterday"
Yes rain sensor, auto correct 😀.
Are you on the latest version?
@petergridge is it possible that it's just a translation issue? Where can i check the translated words and original terms? Maybe the term "tomorrow" is just wrong translated?
like you mentioned, i'm also not able to reproduce this , but i will have an eye on the values to see if i can find any reason/pattern behind.
The translation comes from HA for yesterday/tomorrow... I have had issues that I have struggled to resolve as they are not occurring in the development environment but pop up on the final hardware. One issue has been in the inconsistent handling of timezone when comparing dates, I thought I had that one fixed. I will review it again. Sometimes I can over complicate my code and it leads to issues, time to take a scalpel to my code again.
I have found one case that makes the next runtime not update, if you have manually started a zone and the start time of the is during that run time the next run is not maintained for the zones that were not processed.