Add Speedtestdotnet config_flow

[engrbm87]

Breaking change

Integration is now configured through the UI. To successfully import from configuration.yaml please remove monitored_conditions. If server_id is mentioned it will checked against the list of servers before importing.

Proposed change

• Configure Speedtestdotnet through UI.
• Select test server from list or choose "*Auto Detect" option
• Set scan interval in minutes (Default = 60 minutes)
• Choose option to disable auto update (manual)
• Service to run speed test

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)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Update speedtestdotnet.markdown home-assistant.io#13697

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.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

[probot-home-assistant]

Hey there @rohankapoorcom, mind taking a look at this pull request as its been labeled with a integration (speedtestdotnet) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[MartinHjelmare]

We need to register a listener for the config entry and have a callback change the update interval on the coordinator.

https://developers.home-assistant.io/docs/config_entries_options_flow_handler#signal-updates

[rohankapoorcom]

Hey @engrbm87 - thanks for putting the work in to convert this to a config flow. I've been wanting to do it myself, but have other things take priority over much of open source contributions!

I'm glad to have to join as a code owner for the integration, but I would appreciate not being removed from it.

Thanks again for your contribution. I haven't formally reviewed all of it, but overall, it looks good to me.

[engrbm87]

Hey @engrbm87 - thanks for putting the work in to convert this to a config flow. I've been wanting to do it myself, but have other things take priority over much of open source contributions!

I'm glad to have to join as a code owner for the integration, but I would appreciate not being removed from it.

Thanks again for your contribution. I haven't formally reviewed all of it, but overall, it looks good to me.

Hello @rohankapoorcom , sorry for removing your name by mistake. I will sure add it now.

[MartinHjelmare]

Great!

[MartinHjelmare]

Could we try to import the config yaml to a config entry to ease the transition for users?

[engrbm87]

Could we try to import the config yaml to a config entry to ease the transition for users?

Currently the config yaml includes monitored_conditions which will not be used anymore. So the user will need to update the config yaml entry.
Also the server_id is parameter is no longer required as the user can choose from a list in the UI or choose the Auto Detect option. Importing the server_id means we need to verify that the value is valid.

[MartinHjelmare]

I'm thinking we just import the server_id and validate that against available ids. If good, create the entry, if not good, abort.

[engrbm87]

Ok, let me work on that.

[MartinHjelmare]

Nice!

[MartinHjelmare]

Sorry, one comment more.

[MartinHjelmare]

Please update the breaking change paragraph and mention what options from the config yaml will be imported.

[MartinHjelmare]

Are we ready to merge?

[rohankapoorcom]

Woo-hoo! Nice work @engrbm87!