`update_entity` triggers speedtest when used from a button, but not from an automation (edit: at top of hour)

[jason-curtis]

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:

id: '1687990373473'
alias: Speedtest
description: >-
  runs a speed test hourly but only if the internet hasn't been in use in the
  last ~minute
trigger:
  - platform: time_pattern
    minutes: 0
condition:
  - condition: and
    conditions:
      - condition: numeric_state
        entity_id: sensor.xe75pro_kib_s_sent
        below: 500
      - condition: numeric_state
        entity_id: sensor.xe75pro_kib_s_received
        below: 100
action:
  - service: homeassistant.update_entity
    data: {}
    target:
      entity_id: sensor.speedtest_download
mode: single

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:

  - show_name: true
    show_icon: true
    type: button
    tap_action:
      action: call-service
      service: homeassistant.update_entity
      target:
        entity_id: sensor.speedtest_download
      data: {}

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

id: '1687990373473'
alias: Speedtest
description: >-
  runs a speed test hourly but only if the internet hasn't been in use in the
  last ~minute
trigger:
  - platform: time_pattern
    minutes: 0
condition:
  - condition: and
    conditions:
      - condition: numeric_state
        entity_id: sensor.xe75pro_kib_s_sent
        below: 500
      - condition: numeric_state
        entity_id: sensor.xe75pro_kib_s_received
        below: 100
action:
  - service: homeassistant.update_entity
    data: {}
    target:
      entity_id: sensor.speedtest_download
mode: single

Anything in the logs that might be useful for us?

nothing obvious in the logs. It seems like the `homeassistant.update_entity` fires but then nothing happens. I've tried turning on debug logging.

Additional information

No response

[home-assistant]

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)}}

[davidrustingha]

Same here.
The automation runs smoothly, but doesn't actually update the sensor. Manually triggering the automation does trigger an update.

- alias: Speedtest Check
  id: speed_test_check
  trigger:
    - platform: time_pattern
      minutes: 30
  action:
    - service: homeassistant.update_entity
      data:
        entity_id: sensor.speedtest_download

[DarthSonic]

Gott the very same issue in my HA installation. Using Integration reload to get new measurement.

[JN-Jones]

Looks to me like this, #85375, #80290 and possibly #89854 are all the same issue, updates at full and possibly half hours fail because of an issue in the underlying cli tool. Moving the update check two minutes after the full hour worked for me.

[DarthSonic]

Yes. Triggering every 4 hours on the second minute of the hour works! Thx!

[jason-curtis]

@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!

[dirrgang]

Ah, sweet. In the meantime this is how I added randomness to the test:

alias: Speedtest
description: ""
trigger:
  - platform: time
    at: "01:00:00"
condition: []
action:
  - delay: "{{ (range(1, 5)|random|int) }}:{{ (range(1, 60)|random|int) }}:00"
  - service: homeassistant.update_entity
    data: {}
    target:
      entity_id:
        - sensor.speedtest_ping
mode: single

[issue-triage-workflows]

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.

[JN-Jones]

Yep, still an issue

[issue-triage-workflows]

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.