Jellyfin Plugin like TvHeadend?

#1

I originally came across Channels as a great way to give my MIL a better DVR experience than she was getting from Comcast.
Turns out this is great for me too. I mainly use the Kodi add on and bring in the rest of my media with the jellyfin addon for Kodi.
I recently got into the Jellyfin Android TV app and I noticed they have a THV Plugin. I prefer Channels way more, but want to know if there were any plans to do a Jellyfin Plugin like you did for Kodi?
It seems like it could be done since there's TvHeadend support for JF and Kodi as well.

Also was wondering if there's a way to donate in addition to the monthly or yearly set price.

1 Like
#2

Doesn't Jellyfin take M3U and XMLTV input ?

#3

It does and I have it set up that way, but it would be way better if I could directly control the DVR and access the comskipped recordings, cleanly with a Plugin like I can in Kodi with the addon.

#4

I agree with this. I'd like to see a published API for the server. I know that is ever-changing and may be proprietary. But, if we had access to (at lease a subset of) the API that would be reasonably stable and shareable, we could do lots of things I think.

#5

browse the web admin using web developer tools and you’ll sniff out the API used in Channels DVR Server.

1 Like
#6

I concur with marcuscthomas. I hate writing documentation just as much as every other developer does, however relying on sniffing endpoints makes me nervous because I can't ever know if those endpoints are going to be there when I need them. The release notes tend to be a bit terse as well, even a list of commit messages would be great to see.

https://github.com/fancybits/pychannels and https://github.com/fancybits/rbchannels haven't been updated in a few years.

Edit: The KB category is very nice, thank you for working on that!

#7

And that is the exact reason why the server API is unpublished. If it is published, then it is codified. Making it private and "unsupported" allows the developers the ability to freely iterate without having to be tied to past decisions that may no longer suit their needs.

#8

That's why changelogs were invented.

And this is why we do things like deprecating endpoints that are no longer supported or used.

1 Like
#9

This is something done on public supported APIs. The Channels DVR Server APIs are not Public and we do not guarantee anything. If we did, we'd have full documentation for the API like we do for the client APIs.

We have no plans to make a fully supported public API. We have no qualms with anyone using these though, and honestly we don't change them much.

But what we will not commit to, is slowing our own client development down to support other things using it.

So, feel free to figure them out, use them, they don't change much if ever. But we can't be responsible if they change.