-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
FRITZ!Box Net Monitor negative transmission_rate_up/down values #23717
Comments
Hello, Could you share more of your code that I can see how to configure the component |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
I have the same problem with Home Assistant and my Fritz!Box 7590. configuration.yaml:
Home Assistant release with the issue: Last working Home Assistant release (if known): Operating environment (Hass.io/Docker/Windows/etc.): Component/platform: |
I also still experience this problem. |
Inquired over at fritzconnection which is the underlying package. The behavior is known and will be fixed in an upcoming release. |
Version 1.3.0 of fritzconnection was released with a supposed fix for the issue. I manually updated my installation but still see spikes, however. Anybody else my feel free to give it a spin, though. |
Home Assistant release with the issue:
0.92.2
Last working Home Assistant release (if known):
None
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Component/platform:
FRITZ!Box Net Monitor
Description of problem:
I'm using the Fritz!Box Net Monitor component sensor to show a graph of the Upload and Download speed. I noticed that sometimes big negative values are reported. This makes no sense because Upload or Download cannot be negative. Also it destroys the scaling of the graph.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Additional information:
The text was updated successfully, but these errors were encountered: