Closed Rhysgh closed 11 months ago
Hello. 22:30 has been set as the end time, whereas the slot you're referring to starts at 22:30 so wouldn't be picked.
I assumed that but I can't choose 23:30 because of error handling
is there a reason you are using end time and not start time? is it not more natural to use start time? conversationally you woudl say leccy is 3p at 10 ... not leccy is 3p ending at 10:30
im an idiot, i just realised it .. it works perfectly ignore me sorry.
Describe the bug
It looks like there may be a bug in its calculation, see images.
Current rates sensor has data untill -
this can also be seen in the UI on the dashboard.
with target sensor set 09:00 - 22:30 for 0.5 I would assume the 22:30 slot to be the one chosen but its missed.
at the moment I cant get into vs code so i cant remove the error for agile times and test 23:30..
Reproduction steps
as above
Expected behaviour
as above
Tariff Code
agile
Integration Version
9.2.1
Home Assistant Version
latest
Fresh Install?
Not specified
Home Assistant Logs
n/a
Confirmation