-
-
Notifications
You must be signed in to change notification settings - Fork 511
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
Improve Statistics Counters #2300
Comments
Good idea. I am just not 100% sure what happens to people with batteries on their inverter. |
I like the idea of some automatic mode which results in useful stats for 99% of users. Button, MQTT (? are the values even published)... all possible. |
Yes they are... (And reset via mqtt is already working in my local branch) |
Would it be possible to store the counters in a way that you can select by a range, e.g. last 5 min, last hour and last 6 hours? |
@mrueg that would require to store them in several round-robin / ring registers for the times / intervals you have given. |
Is your feature request related to a problem? Please describe.
Statistics are a great new feature! Thank you for the enhancement!
Unfortunately the stats get "poisoned" by the attempts to reach the inverters in the early morning hours.
These failure counts makes it impossible to justify the link quality between DTU and the inverter.
I was helping myself by rebooting the DTU. Now the values look fine and allow to check if the reachability is fine.
Describe the solution you'd like
Proposal:
The stats already get reset at midnight.
This will collect offline stats.
At the first successful response from the inverter, reset stats and set a flag.
Now we count fresh online stats.
First I like to collect feedback from other users and devs.
I'll be happy to code the required changes and issue a pull request on positive feedback :)
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: