-
-
Notifications
You must be signed in to change notification settings - Fork 32.6k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
update_entity
triggers speedtest when used from a button, but not from an automation (edit: at top of hour)
#96441
Comments
Hey there @rohankapoorcom, @engrbm87, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) speedtestdotnet documentation |
Same here.
|
Gott the very same issue in my HA installation. Using Integration reload to get new measurement. |
Yes. Triggering every 4 hours on the second minute of the hour works! Thx! |
update_entity
triggers speedtest when used from a button, but not from an automationupdate_entity
triggers speedtest when used from a button, but not from an automation (edit: at top of hour)
@JN-Jones your workaround works for me too so I added it to the issue description, thank you! It looks like like sivel/speedtest-cli/#796 would fix this, but in the meantime we can just stop hammering the speedtest servers all at the same time! |
Ah, sweet. In the meantime this is how I added randomness to the test:
|
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. |
Yep, still an issue |
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. |
Can corfirm this issue persists in 2024.03.1 |
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. |
The workaround seems to work OK but afaik the issue of speedtest silently
failing when run on the hour, still exists.
<https://optionzero.co>
…On Fri, Jun 14, 2024 at 4:08 AM issue-triage-workflows[bot] < ***@***.***> wrote:
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.
—
Reply to this email directly, view it on GitHub
<#96441 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZPVU7FYLONCROSSIHZBI3ZHLFJDAVCNFSM6AAAAAA2HZTO7WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRXG44TGMZRGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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. |
still relevant; good to have this marked as "open" so that folks can find it and the workaround. |
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. |
The problem
I can't get speedtest to reliably trigger from an automation running at the top of the hour.
edit: workaround per @JN-Jones: adjust the minute to not be 0 or 30.
Here's my automation config:
Here's an example trace from 8am on July 10:

Looks like it worked, right? But when I actually check the data, there is no speed test conducted at that time:

I included the network activity in that view so you can see there was a successful test at 10 AM but nothing happened at 8 AM.
Usage with a lovelace button is working
At the same time, I have a lovelace button set up that successfully triggers a speed test every time:
What version of Home Assistant Core has the issue?
core-2023.7.1
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
speedtestdotnet
Link to integration documentation on our website
https://www.home-assistant.io/integrations/speedtestdotnet/
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: