-
-
Notifications
You must be signed in to change notification settings - Fork 17
-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
[DEVICES] Not reporting WAN traffic / speed <- add in here, please #30
Comments
Add info on missing WAN sensors for some devices [issue #30]
An RT-AX88U (FW: 3.0.0.4.386_48631) does NOT show such a problem. Could it be related to the AiMesh? The one with the problems in the original issue was using it. This one does not 🤔 |
Hey, @leonidfeldman1977, Can you please enter the web panel of your device and go to the Then you would need to open Developer Tools in your browser (F12 on keyboard), there tab I would need the response for one of such requests. It includes something similar to:
This could help in solving the problem of the WAN absence from the integration. Thanks! |
Unfortunately, this issue cannot be solved from the integration point of view. If a device is not reporting some data in the API endpoints, the only way to troubleshoot it will be to get direct access to the device for tests. Other devices of the same models and/or firmware versions are working well. In case this issue happens to any other user and device, I suggest updating the firmware to the latest version and performing a factory reset (all the settings will be lost in this case). |
🐞 Some Asus devices are known to not report WAN traffic. That means also the speed cannot be calculated. I am currently looking in the walk-around to get this data for the full user experience.
In case, you are experiencing this issue, please add your device model and firmware version in the comments.
List of known devices not reporting WAN data:
The text was updated successfully, but these errors were encountered: