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
If there are gaps in the meter readings available from Octopus the logs files can be quickly overwhelmed by huge numbers of "[OctopusAgile] Unmatched consumption ..." , errors.
I may be unlucky but I have had gaps of at least a day in every month I've been on the Octopus Agile rate , sometimes it has been weeks before Octopus has done something about it.
Currently I can suppress the errors by commenting out lines 377-380 in custom_components/octopusagile/OctopusAgile/Agile.py but I think it would be better if the code could simply handle this with a single daily message to the effect that consumption figures are approximate due to gaps in the meter readings.
Thanks
The text was updated successfully, but these errors were encountered:
If there are gaps in the meter readings available from Octopus the logs files can be quickly overwhelmed by huge numbers of "[OctopusAgile] Unmatched consumption ..." , errors.
I may be unlucky but I have had gaps of at least a day in every month I've been on the Octopus Agile rate , sometimes it has been weeks before Octopus has done something about it.
Currently I can suppress the errors by commenting out lines 377-380 in custom_components/octopusagile/OctopusAgile/Agile.py but I think it would be better if the code could simply handle this with a single daily message to the effect that consumption figures are approximate due to gaps in the meter readings.
Thanks
The text was updated successfully, but these errors were encountered: