BottlecapDave / HomeAssistant-OctopusEnergy

Unofficial Home Assistant integration for interacting with Octopus Energy
https://bottlecapdave.github.io/HomeAssistant-OctopusEnergy/
MIT License
564 stars 55 forks source link

Zero-values on initialisation #85

Closed FalconUK closed 1 year ago

FalconUK commented 1 year ago

Describe the bug

When HA restarts, accumulating sensors return 0 for a period of time (I'm guessing until the next update from the API), during which, the sensor value is logged as 0, creating issues with graphs.

image

To Reproduce

Steps to reproduce the behavior:

Expected behavior

As the sensors are accumulative, I think it would be more correct to hold the previous value, until a new value is received.

Home Assistant Version

The version of Home Assistant is 2022.10

Integration Version

The version of the integration is 4.6.4

Fresh Install?

Upgrade

github-actions[bot] commented 1 year ago

This issue has become stale because it has been open for 30 days with no activity. If you still think it's an issue, please respond soon.

BottlecapDave commented 1 year ago

This should be fixed in the next update. I'll post here once it's available.

FalconUK commented 1 year ago

Great stuff. Thanks, much appreciated.

BottlecapDave commented 1 year ago

Hello @FalconUK These should now be fixed in https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/releases/tag/v4.7.0

lozzd commented 1 year ago

I know this was regarding the cumulative values, but after just installing 4.7.0 my rate values were £0.00 for 14 minutes. Is that expected? Should I open a new issue?

FalconUK commented 1 year ago

Hello @FalconUK These should now be fixed in https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/releases/tag/v4.7.0

Thanks! Downloaded this evening.

BottlecapDave commented 1 year ago

I know this was regarding the cumulative values, but after just installing 4.7.0 my rate values were £0.00 for 14 minutes. Is that expected? Should I open a new issue?

@lozzd This could has been a by product of when I added the restore feature. If you see the behaviour again, please do open a new issue.