Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Daily Energy steps up massively every time consumption resumes from 0 #598

Open
kineticscreen opened this issue Sep 25, 2024 · 5 comments
Open
Labels
no-stale This issue or PR is exempted from the stable bot.

Comments

@kineticscreen
Copy link

kineticscreen commented Sep 25, 2024

After having stabilised the instantaneous consumption data errors I was getting by adding the internal filter: as well as ensuring no feedback from flashing LEDs, this has revealed a different issue, where the Daily Energy increases by huge numbers every time the unit starts to detect consumption again, after a period of 0 flashes due to adequate solar generation:
image

As you can see, this not the result of an incorrect reading of the Consumption - only momentary modest pulling from the grid is accompanied by massive instantaneous jumps in the daily total.

Has anyone experienced this? My only thought it is somehow connected to the 4-5 minute lag the unit has to changing power consumption to 0 once the flashing has stopped. And somehow when it kicks back in, it's assuming a value across the time that should be 0?

@kineticscreen
Copy link
Author

kineticscreen commented Sep 28, 2024

So further to this, it seems like the size of the step up is connected to how long the sensors has been 'off' or detecting zero, because this is the ridiculous jump it did today, a day of continuous solar production, and then when the Glow kicked in at the end of the day, it instantaneously added nearly 18kWh to the total.

image

Copy link

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Oct 29, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 6, 2024
@kineticscreen
Copy link
Author

This issue continues, and renders the Glow useless for daily power consumption, and only useful for instantaneous power monitoring. This issue shouldn't be closed off, even if there is no solution, because people need to be able to find that it as a serious limitation of the platform.

@klaasnicolaas klaasnicolaas reopened this Nov 6, 2024
@klaasnicolaas klaasnicolaas added no-stale This issue or PR is exempted from the stable bot. and removed stale There has not been activity on this issue or PR for quite some time. labels Nov 6, 2024
@klaasnicolaas
Copy link
Owner

klaasnicolaas commented Nov 6, 2024

I think the best solution at this point is to put a note somewhere in the documentation that it is best not to use glow if you also have solar panels. What you also can try is using a different method: left or trapezoid.

./Klaas

@kineticscreen
Copy link
Author

What you also can try is using a different method: left or trapezoid.

Happy to try this out - is there a way I can make this change onboard the Glow itself, rather than making a Template sensor in HA - would be good to still get the advantage of the 'always recording' glow, even during a system reboot, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-stale This issue or PR is exempted from the stable bot.
Projects
None yet
Development

No branches or pull requests

2 participants