ASUSWRT: "Download Speed" and "Upload Speed" sensors (and more) non functional

[m-scha1337]

The problem

Hi!

It seems like the "Download Speed", "Download", "Upload Speed" and "Upload" sensors included in the ASUSWRT integration don't seem to be working correctly as they display only "0.00 Mbit/s" and "unknown". However, other sensors such as "Devices Connected", various temperature sensors and load avg. sensors do work. It also flawlessly creates device trackers. Just in case people start arguing I should be using the Speedtest.net integration in order to measure up/down speeds, the RT-AX56U already has a speedtest.net integration (in web-interface: "Adaptive QoS"->"Internet Speed"). Besides: The Speedtest.net integration only measures up/down speeds at the home-assistance instance. The ASUSWRT integration should directly interface with the router and measure speeds directly at the WAN interface.

I am using an Asus RT-AX56U (Asuswrt-Merlin, v.388.2_2 (most recent version as of submitting this issue))

Attached are some screenshots:

Notice under "Sensors" the Download/Download Speed/Upload/Upload Speed sensors

History of all offending sensors

Notice also the "Devices Connected" sensor working flawlessly

What version of Home Assistant Core has the issue?

core-2023.7.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ASUSWRT

Link to integration documentation on our website

https://www.home-assistant.io/integrations/asuswrt

Diagnostics information

Device (RT-AX56U) Diagnostics fetched via "Device Info" dialogue: config_entry-asuswrt-2210d8ecfd05ab1f344e095db9488925.json.txt

I also let "Enable debug logging" run for about 10 minutes in the integration itself, although my untrained eye doesn't see anything out of the ordinary. home-assistant_asuswrt_2023-07-21T11-58-14.839Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @kennedyshead, @ollo69, mind taking a look at this issue as it has been labeled with an integration (asuswrt) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of asuswrt can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign asuswrt Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

asuswrt documentation asuswrt source _{^{(message by IssueLinks)}}

[home-assistant[bot]]

Hey there @rohankapoorcom, @engrbm87, mind taking a look at this issue as it has been labeled with an integration (speedtestdotnet) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of speedtestdotnet can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign speedtestdotnet Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

speedtestdotnet documentation speedtestdotnet source _{^{(message by IssueLinks)}}

[m-scha1337]

Hey there @rohankapoorcom, @engrbm87, mind taking a look at this issue as it has been labeled with an integration (speedtestdotnet) you are listed as a code owner for? Thanks!

Code owner commands (message by CodeOwnersMention)

speedtestdotnet documentation speedtestdotnet source (message by IssueLinks)

Whoops.. That was unintentional. There is no issue with your integration!! Just mentioned the link in my report, that's all.

[issue-triage-workflows[bot]]

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. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Dart2112]

Confirming that this is still an issue on the latest home assistant version

[DipsoNOR]

Same here

[ollo69]

With last HA release AsusWRT integration support http(s) protocol based on a new library. I suggest to reconfigure integration selecting https in config flow and check if this solve the issue. Of course to use https protocol must enabled router side.

[DipsoNOR]

With last HA release AsusWRT integration support http(s) protocol based on a new library. I suggest to reconfigure integration selecting https in config flow and check if this solve the issue. Of course to use https protocol must enabled router side.

Seems its going to be fixed in next HA release: https://github.com/home-assistant/core/pull/105247

[ollo69]

@DipsoNOR,

I think you are confusing the problems. This issue was opened 6 months ago, so I suppose is related to problems between router and library. The fix you mentioned is just related to a bug introduced with HA 2023.12.0 that will be fixed in 2023.12.1. Maybe moving to HTTP protocol could fix also this issue.

[DipsoNOR]

Ah ok, you might be right. I just saw that they both mention download and upload data missing, so thought they where the same issue.

[ildar170975]

2024.2.3 AC68U, Merlin 386.12_4

ASUSWRT connected via https (as suggested).

Recently observed this abnormal value:

Although I got a gigabit ISP, this value is rather high)))

[ildar170975]

One more example: About ~10GB were downloaded within last 10-15 minutes (uTorrent):

But the value is < 0.2GB:

---

I wonder shall I create a new issue or write here. Here is an entity created by ASUSWRT (added a graph for "HA uptime" just in case):

Note the total_increasing class. In fact, the entity is not increasing:

What we can see here:

1. Value is resetting after > ~4GB - there is a a separate issue https://github.com/home-assistant/core/issues/31404
2. A drop after ~06:00 (a router restarts at 06:00 every day).

Also, I saw a warning in Log: 24-02-22 22:25:10.392 WARNING (Recorder) [homeassistant.components.sensor.recorder] Entity sensor.ac68u_upload from integration asuswrt has state class total_increasing, but its state is not strictly increasing. Triggered by state 0.022258651 (0.023325757) with last_updated set to 2024-02-22T19:24:45.420165+00:00. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+asuswrt%22

[issue-triage-workflows[bot]]

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. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[ildar170975]

Still there. Here is a history (added HA uptime - i.e. HA was not rebooted):

And within last 1-2 hours about 20GB were downloaded (uTorrent).

[issue-triage-workflows[bot]]

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. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[ildar170975]

up

[issue-triage-workflows[bot]]

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. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[ildar170975]

The issue was closed automatically, but it is not resolved.