Jellyfin Integration Dead

[coolhand72]

The problem

Ever since the Jellyfin 10.9 upgrade, the integration does not communicate any information at all from my jellyfin server. When I delete the integration, I am able to re-install it with the appropriate credentials, so that part works. But after that, no media players are populated, and the integration reports 0 watching. Please refer to this issue for some history. I currently have Jellyfin at the core of my multimedia entertainment automations, but if it is no longer being supported, I will need to rework those automations. Just looking for some guidance on the future of this integration.

What version of Home Assistant Core has the issue?

core-2024.10.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Jellyfin

Link to integration documentation on our website

https://www.home-assistant.io/integrations/jellyfin

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @j-stienstra, @ctalkington, mind taking a look at this issue as it has been labeled with an integration (jellyfin) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `jellyfin` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign jellyfin` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

jellyfin documentation jellyfin source _{^{(message by IssueLinks)}}

[joostlek]

Please add more info about what your issue is, this issue doesn't add a lot of information that can help solving the issue you have

[coolhand72]

Please take a look at this thread all the way to the end for greater context, but ever since the Jellyfin 10.9 upgrade, the integration does not communicate any information at all from my jellyfin server. When I delete the integration, I am able to re-install it with the appropriate credentials, so that part works. But after that, no media players are populated, and the integration reports 0 watching.

I am running Jellyfin on a docker container and home assistant also on a docker container on the same host. There are no logs.

[joostlek]

Please enrich the issue itself instead of linking to other resources, this way issues can be picked up easier

[coolhand72]

I would be happy to provide you additional information if you can tell me what you need to troubleshoot?

One user in other thread pointed out there were probably some API changes, at least looking at the TypeScript API client project, it is listed as "breaking changes" for the new 10.9.x releases of Jellyfin.

https://typescript-sdk.jellyfin.org/index.html#md:breaking-changes

And further, looking at https://github.com/jellyfin/jellyfin-apiclient-python/issues/43 there might be a general issue with the latest pything client, so I assume there is a bit more work to be done.

And further that, after updating from 10.8.x to latest 10.9.x HA always reported "0 watching", which was used for some server shutdown automation but broke after the Jellyfin update 😸 thats why I took a look into this. Sorry for not having any clue how to solve this issue.

Then PixelPusher247, " changed to a webhook implementation and hadn't tried the integration again. After testing it right now it added a new media player on playback. All seems to work again. Closing issue. "

I don't know what pixelpusher247's solution was, but they closed the issue. Myself and other users continue to experience the same problem.

[joostlek]

Okay so just update the issue for what you're experiencing and then someone can take a look.

[coolhand72]

updated