Threadfin & Jellyfin

[Goby]

I have IPTV providers with something like 6000 channels when I am interested in 60 at most. In order to sort all the chanlles I use Threadfin a fork of Xteve.
Everithing goes smooth with Threadfin :
- I manage to sort the 60 channels with the mapping tool

- the m3u link of Threadfin  (http://192.168.0.32:34400/m3u/threadfin.m3u) point to an .xml file which does include only my 60 channels.

The tricky thing is : when i create a new tuner in jellyfin with m3u option and put the m3u link of threadfin (http://192.168.0.32:34400/m3u/threadfin.m3u), I still have the 6000 channels as a result in Jellyfin...

I don't see what I am doing wrong...

Any ideas?

Thanks

[xaque]

It would be nice to know what os you're running.

My first suggestion is to point jellyfin not to the m3u that threadfin is using to load the m3u, but instead point it to the saved .xml file threadfin creates after you've made the edits.

So for example, with my docker instance of threadfin that location is at localipaddress:port/xmltv/threadfin.xml?username=username&password=password.

You can fine the location for this in the threadfin web ui by clicking the hamburger icon (three horizontal line) and then server information.

You will also need to go into the threadfin settings and check the web authentication, m3u authentication, xml authentication, and api authentication boxes to set up a username and password.

[Goby]

My bad, I am too much into it and I forgott the basics. My setup is:Jellyfin and Threadfin run with Docker on a Synology DS918+ with DSM 6.2 (Actually an Xpenology and I am too lazy to swith to DSM 7.x).

I don't use credentials to access to Threadfin to ease the process. (untick option in the Threadfin Settings)

I tried your solution, pointing to the Threadfin .xml file instead the .m3u file, tadaaaa! it works like a charm.

Thanks a lot for your help.