Jellyfin Repository Is empty on CoreELEC 21+

[Muffkiss]

Hello!

I have a new Dune HD HBR 4K+ that I'm trying to use Jellyfin on. I am trying to use CoreELEC 21+ so as to utilize the Dolby Vision capable hardware. I've tried to use both the stable and nightly versions.

However, the repository is empty when I try to install either Jellyfin for KODI or JellyCon.

I use the typical process; connect to https://kodi.jellyfin.org, add the repository (repository.jellyfin.kodi.zip), install by ZIP, and then I should have a pair of add-ons to choose from.

However, there's nothing there.

Is Jellyfin capable of being used with CoreELEC 21+? Am I doing something wrong?

Any assistance these shiny new forums can provide will be greatly appreciated.

[JeroenED]

Since this is probably not fixed yet I took a quick look in the issue and seems that the repository plugin got invalid in that way that the repository itself got split into 2 repositories for python2 and python3 without updating the plugin.

I took the liberty to update it myself. I it completely untested as I don't have kodi available right now but I think i will just work as it was only updating some urls.\\


  repository.jellyfin.kodi.zip (Size: 85.96 KB / Downloads: 89)

[mcarlton00]

Kodi 21 is not officially supported yet because we don't bother chasing alphas.  They simply introduce more issues that we spend a bunch of time trying to chase down and then they're fixed in the next version anyway.

That being said, the repository should be working regardless, but it's possible we need to update the regex to match something new.  Or they changed the useragent in the new version and broke our toys again.  50/50 odds, really.

[Deleted User]

fwiw @mcarlton00 i had to fix the same on my own several months ago

the addon.xml in the repository addon points to https://repo.jellyfin.org/releases/clien...addons.xml

but the path is https://repo.jellyfin.org/releases/clien...addons.xml

see https://repo.jellyfin.org/releases/client/kodi


so i am not sure where or what or when things changed but it is a valid issue for *some*

[mcarlton00]

So the TLDR is when Kodi switched from python 2 to python 3, they didn't provide the best upgrade path and the only real guidance at the time was "just distribute two repository files" which leads to lots of user error and manual intervention to upgrade between versions. We solved this by matching useragents and routing things to the correct location on the repository server. If you're on Kodi 18 or lower, you get routed to /py2. If you're on Kodi 19 or newer, you get routed to /py3. However, certain Kodi forks and custom builds like to play with the useragent because reasons and make our lives complicated.

Everything should be working as intended right now, however I can't test at this exact moment, because the kodi-git aur package is refusing to build (as is tradition), and the flatpak version that's supposed to be following the beta channel is still pointing to Kodi 20. I'll need to either track down one of my Pis later and flash a newer version onto it or figure out how to compile kodi manually again.

[Deleted User]

as of 5 minutes ago i can confirm works for me

Kodi (21.0-ALPHA1 (20.90.101) Git:20230321-124023d6ff). Platform: Linux x86 64-bit
Kodi compiled 2023-03-22 by GCC 10.2.1 for Linux x86 64-bit version 5.10.158 (330398)

[mcarlton00]

Great, thanks for checking