Increase Netgear speedtest period to 2 hours

[starkillerOG]

Breaking change

Proposed change

Increase Netgear speedtest period from 30 minutes to 2 hours to decrease data usage, see issue: #85137

When speedtest sensors are added for the first time and no last sensor data is available, do a speedtest emidiatly.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #Netgear integration speed test causes excessive data usage #85137
• This PR is related to issue:
• Link to documentation pull request: Netgear add notes about speedtest data usage home-assistant.io#25597

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @hacf-fr, @Quentame, mind taking a look at this pull request as it has been labeled with an integration (netgear) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of netgear can trigger bot actions by commenting:

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

[frenck]

Thanks, @starkillerOG 👍

[MartinHjelmare]

The entity state is always updated by default when the entity is added to Home Assistant. We don't need this line.

What was the goal with this change?

[starkillerOG]

Actually in this case the update coordinator does not fetch new data from the API when the entity is added to prevent large bandwidth usage of speedtest during boot of homeassistant.

So the goal is to have the update coordinator fetch data from the API only if no previous values are available (so this is a new entity).

@MartinHjelmare did I use the wrong command?
I think so...
Schould I have used await self.coordinator.async_request_refresh()?

[MartinHjelmare]

Yes, that's correct. 👍