We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When in the dasboard page, the "bandbreite" graph doesn't show any values. Also "Download" and "Upload" always shows 0.00 MBit/s (see image)
The docker log shows a lot of these errors:
[03.11.2024, 15:41:16] [ERROR] ==> query networkMonitor.getStats in 2766ms ❌ tRPC failed on networkMonitor.getStats: Cannot read properties of undefined (reading 'sync_groups')
This behaviour is there regardless if a stress the bandwidth to the fullest (1000mb/s up & down) or have normal Internet use.
I would expect the "Bandbreite" graph to be normally filled and the "Download" and "Upload" to have the expected value.
The text was updated successfully, but these errors were encountered:
BTW: I love your project! Very nice interface and I also was fed up with the very slow GUI of the Fritz!box
Sorry, something went wrong.
Hi @carel, Thanks for reporting this. I haven’t actively worked on this project in a while, but I’ll take a look at it this week.
lukesthl
No branches or pull requests
Current Behavior
When in the dasboard page, the "bandbreite" graph doesn't show any values. Also "Download" and "Upload" always shows 0.00 MBit/s (see image)
The docker log shows a lot of these errors:
[03.11.2024, 15:41:16] [ERROR] ==> query networkMonitor.getStats in 2766ms
❌ tRPC failed on networkMonitor.getStats: Cannot read properties of undefined (reading 'sync_groups')
This behaviour is there regardless if a stress the bandwidth to the fullest (1000mb/s up & down) or have normal Internet use.
Expected Behavior
I would expect the "Bandbreite" graph to be normally filled and the "Download" and "Upload" to have the expected value.
Steps to Reproduce the Problem
Environment
The text was updated successfully, but these errors were encountered: