Massive usage of network data

Hi everyone,

Just an information post about the “speedtestdotnet” integration.
Watch out for massif data-usage of this integration. In the past i’ve used it for some simple results showing up. But since it has been changed to speedtestdotnet it uses a lot of data, which concluded in all of my network data for this month has gone. In the past 2 days it has consumed over 800Gb (was speed testing every 10 seconds)…

So people, watch out of using this integration!

You should have read the documentation:

If [ran]sic frequently, this integration has the ability to use a considerable amount of data. Frequent updates should be avoided on bandwidth-capped connections.

1 Like

I know, afterwards i’ve read it too. Personally i think no one reads the bottom of an integration before using it. This post is meant to be a warning to users (like me), just picking cool integrations and using them.

But thanks for re-mentioning it :wink:

Now we know who made the internet so slow! :rofl:
Sorry! Just kidding.

Just to be curious, can you post some of your data traffic to see what’s a normal traffic for a configuration?

At the moment my traffic looks like this:

image

A speed test every 10 seconds !
I’m sure they take longer than that to complete…

Unless you’re on GB connection speeds, yeah. Even so it’s a horrid waste of network resources.

The data use is actually dependant on the connection speed.

Your poor router…
I run a test every 15mins and I’ve been considering changing it to 30mins, purely because I dont ‘really’ do anything with the data.

I use manual mode and only run it hourly during peak times when there’s likely to be problems:

- id: speedtest_peak_time_check
  alias: 'Speedtest Peak Time Check'
  initial_state: true
  trigger:
  - platform: time
    at: '18:02:00'
  - platform: time
    at: '19:02:00'
  - platform: time
    at: '20:02:00'
  - platform: time
    at: '21:02:00'
  - platform: time
    at: '22:02:00'
  - platform: time
    at: '23:02:00'
  action:
    service: speedtestdotnet.speedtest

wouldn’t that be equal to:

- id: speedtest_peak_time_check
  alias: 'Speedtest Peak Time Check'
  initial_state: true
  trigger:
    platform: time_pattern
    minutes: 2
  condition:
    condition: time
    after: 18:00:00
    before: 00:00:00
  action:
    service: speedtestdotnet.speedtest

:slight_smile:

2 Likes

Yes except your automation triggers a lot more often than needed and relies on conditions to prevent the actions occurring. Mine just triggers when needed.

the automation triggers,according to the docs:

# Matches every hour at 5 minutes past whole

in this case 2 minutes.
considering the conditions, this would make this automation only trigger at the times of your original automation?

trigger= fire the action (you can check that on the attributes last_triggered, which won’t be set in my automation either)

don’t know it the system feels a difference between that, since sensor time is running always…maybe a few micros of …capacity? 18 checks less per day …
your probably right… just thought id add the possibility of a shorter automation with the same end-effect…

Probably not, but it makes me feel better to know I only trigger when needed.

Yes,. I run it manually every three hours during the day and it uses close to a TB per day, but fuck Comcast since they’re making me buy their unlimited data plan.

Sometimes the automation fails to get data as its a scrape.