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)…
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.
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.
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.
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…
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.