Add Jellyfin integration

[RunC0deRun]

Proposed change

Add an integration for Jellyfin media system. The integration provides the content of a user's libraries as a media source with Home Assistant. This initial pull request is intentionally limited in scope, supporting only a single Jellyfin server at a time and supporting only music libraries. This is done to keep this initial submission small.

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

Additional information

• Link to documentation pull request: Add Jellyfin documentation home-assistant.io#15967
• Link to brands pull request: Add Jellyfin logo and icon brands#2099

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

To help with the load of incoming pull requests:

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

[homeassistant]

Hi @j-stienstra,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[Kane610]

Isn't the emby integration sufficient?

[RunC0deRun]

Jellyfin has forked from Emby around two years ago now and although the Emby integration can at this moment still be used with Jellyfin servers, there is no guarantee it will remain working. Therefore using the jellyfin provided Python API provides a more stable platform to build on.
Next to this, the two integrations provide different features. The Emby integration provides clients to the Emby server as Media Players. This proposed integration provides a Jellyfin server as a Media Source.

[Kane610]

Thanks for clarifying

[anthonylavado]

@j-stienstra Thanks for this. Feel free to ping me (or the greater Jellyfin team) if you need any assistance (that goes for any HA maintainers too).

[milanmeu]

See comments

[RunC0deRun]

@milanmeu, thanks for the review! I rebased my fork and applied the suggested changes to the import and string formats.

[milanmeu]

Have another look at the comment #44401 (comment).

[KapJI]

With #49762 strict type checks are now opt-in.

Seems you already annotated everything, please add it to .strict-typing to enable these checks.

[KapJI]

Thanks!

[KapJI]

#49847 renamed FlowResultDict, please rebase one more time 🙂

[RunC0deRun]

@KapJI Done! I'm getting quite handy at this rebasing by now :)

[MartinHjelmare]

There are some build errors. You may need to rebase again and then address the things that are related to this integration.

[RunC0deRun]

Sorry about the closing and re-opening. Hit the wrong button in the Github app....

[MartinHjelmare]

Looks good!