Open marcoaddario opened 6 months ago
Battery hours left will remain at 48 if you have an upcoming charge slot, it will only drop below that if you are predicted to run out of battery before the next charge.
Is this behavior changed recently? this is the battery hours_left graph from the 1st of April (but unfortunately I cannot remember to which version I have upgraded around the 8th). the 2 ramps on 12th and 17th are after I restarted appdaemon. My charge plan is always more or less the same: charges during night following the intelligent octopus tariff
Its not change in a long time, maybe you stopped running out of battery?
You can look at predbat.battery_hours_left and predbat.best_bettary_hours_left to compare with and without the current plan
Thank you for your reply Trefor. I am struggling in understanding the result, now that I graphed them: These are the latest 45 days. Until mid March it looked like that the prediction was following the actual values. from there something (that I cannot uderstand) happened.
And this is the link to the snapshot: https://snapshots.raintank.io/dashboard/snapshot/8q5XGriFWeGM7M3FaM2E864b0JRPH64K?orgId=0&from=now-45d&to=now
Describe the bug battery_hours_left is stuck to 48 hours since the night charge. It already happened with a previous version of predbat and I fixed it restarting appdaemon. after that the value went up to 48h and did not update.
Expected behavior battery_hours_left should be evaluated and display the predicted time remaining on battery
Predbat version
currently on 7.16.15 but I got the same with the previous (at least 2) versions
Environment details
Screenshots
Log file
the notable events are: 2024-04-12 23:00:02.100769 INFO pred_bat: Battery has 3.5 hours left - now at 3.9
2024-04-12 23:00:25.977999 INFO pred_bat: Battery has 3.5 hours left - now at 3.9
2024-04-12 23:05:02.105113 INFO pred_bat: Battery has 48.0 hours left - now at 3.83
and it stayed to 48.0 since then:
full log in attachment log.txt