Add YouTube integration

[joostlek]

Proposed change

Add YouTube integration. First you login via Google, after which you can select channels from your subscription list. It will fetch the latest video and the amount of subscribers for a youtube channel.

This is a very early draft, please take a look and give some feedback for code and for how it works.

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 #
• This PR is related to issue:
• Link to documentation pull request: Add Youtube documentation home-assistant.io#27378

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
• I have followed the perfect PR recommendations
• 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.

[tkdrob]

Thanks for the PR. Please provide return types for all functions and methods. We also require tests for the config flow. See the Google Mail example.

[joostlek]

Thanks for the PR. Please provide return types for all functions and methods. We also require tests for the config flow. See the Google Mail example.

Yea working on it, but I thought I'd throw it out for other to give some preliminary feedback :)

[joostlek]

@tkdrob Are you maybe able to help me out with the test for triggering a reauth after setup? I can't get the method to work.

[tkdrob]

@tkdrob Are you maybe able to help me out with the test for triggering a reauth after setup? I can't get the method to work.

It is good practice to limit the first PR to the minimum needed to provide the user functionality. Let's leave to reauth step for a followup PR to keep things small. This is only an issue when the user changes the password which likely revokes the oauth authorization.

[joostlek]

@tkdrob Are you maybe able to help me out with the test for triggering a reauth after setup? I can't get the method to work.

It is good practice to limit the first PR to the minimum needed to provide the user functionality. Let's leave to reauth step for a followup PR to keep things small. This is only an issue when the user changes the password which likely revokes the oauth authorization.

What would you suggest, since I took google mail as basis (as you obviously noticed), what's the best way to keep that out of here?

[tkdrob]

See below

[joostlek]

Do you have an example json response for the unit test?

[tkdrob]

Do you have an example json response for the unit test?

This is printed with ex.args

({'vary': 'Origin, X-Origin, Referer', 'content-type': 'application/json; charset=UTF-8', 'date': 'Mon, 15 May 2023 21:25:42 GMT', 'server': 'scaffolding on HTTPServer2', 'cache-control': 'private', 'x-xss-protection': '0', 'x-frame-options': 'SAMEORIGIN', 'x-content-type-options': 'nosniff', 'alt-svc': 'h3=":443"; ma=2592000,h3-29=":443"; ma=2592000', 'transfer-encoding': 'chunked', 'status': '403', 'content-length': '947', '-content-encoding': 'gzip'}, b'{\n  "error": {\n    "code": 403,\n    "message": "YouTube Data API v3 has not been used in project 0 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=0 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.",\n    "errors": [\n      {\n        "message": "YouTube Data API v3 has not been used in project 0 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=0 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.",\n        "domain": "usageLimits",\n        "reason": "accessNotConfigured",\n        "extendedHelp": "https://console.developers.google.com"\n      }\n    ],\n    "status": "PERMISSION_DENIED"\n  }\n}\n')

[tkdrob]

See below

[allenporter]

Optional: I'd suggest extracting constants for these large dicts.

[joostlek]

To what place would be the best?

[allenporter]

I don't know, maybe a constant somewhere? I don't have a strong opinion about this so feel free to do later or not.

[allenporter]

Thanks @joostlek 👍🏼

[MartinHjelmare]

Please address the comments in a new PR. Thanks!