Add config flow to transmission

[engrbm87]

Breaking Change:

The Transmission integration can now be configured through a config flow via Integrations in the GUI. Once configured all sensors and switches will be created and available for the user.
monitored_conditions has been removed so existing users need to update their configuration in configuration.yaml and remove monitored conditions. The existing configuration will be imported as an entry under Integrations.

Description:

In addition to the previous sensors and switches that were available under monitored_conditions a new switch to start and stop all torrents has been added.
The update Interval is now an option that can be altered under options.

Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#10293

Example entry for configuration.yaml (if applicable):

transmission:
  host: 192.168.1.1

Checklist:

• The code change is tested and works locally.
• There is no commented out code in this PR.
• I have followed the development checklist

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

• Documentation added/updated in home-assistant.io

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

• The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

[engrbm87]

Open Issue : 26334

[MartinHjelmare]

Since the library doesn't support asyncio, we have to think about sync vs async context all the time in this integration. Please take care, especially when calling api functions.

I think we have a good separation now, considering this complication. All the methods on the TransmissionClient class are async. All the methods on the TransmissionData class are sync.

[MartinHjelmare]

Please run python3 -m script.hassfest.

[engrbm87]

Please run python3 -m script.hassfest.

There is an issue with this script and the black pre-commit (issue#26334). transmission is already in the list in this file

[MartinHjelmare]

Good!

[MartinHjelmare]

Sorry, we require tests of the config flow too. It should be included in coverage calculation.

[MartinHjelmare]

Please fix the CLA error.

[MartinHjelmare]

File config_flows.py is not up to date. Please run python3 -m script.hassfest.

[engrbm87]

File config_flows.py is not up to date. Please run python3 -m script.hassfest.

I am not able to commit after running the script. Black is adding a comma to the last line.

[MartinHjelmare]

Try rebasing on latest dev branch if that problem persists. We should have fixed it in the dev branch by turning off formattting of the generated files.

[MartinHjelmare]

Looks good! Please update .coveragerc and don't exclude the config flow module from coverage calculation.

[frenck]

Thank you for your contribution thus far! 🎖 Since this is a significant contribution, we would appreciate you'd added yourself to the list of code owners for this integration. ❤️

Please, add your GitHub username to the manifest.json of this integration.

For more information about "code owners", see: Architecture Decision Record 0008: Code owners.

[engrbm87]

Thank you for your contribution thus far! 🎖 Since this is a significant contribution, we would appreciate you'd added yourself to the list of code owners for this integration. ❤️

Please, add your GitHub username to the manifest.json of this integration.

For more information about "code owners", see: Architecture Decision Record 0008: Code owners.

Thanks for the opportunity to contribute in HA which I really like. I have added my username as code owner.

[MartinHjelmare]

Please add tests of the options flow too, to reach 100% test coverage of the config flow module.

[MartinHjelmare]

Looks great!

[MartinHjelmare]

Please add a breaking change paragraph in the PR description and update the description with the current changes in the PR. The breaking change paragraph should describe briefly what changed and what the user needs to do to cope with the breaking change.