Latest NextPVR 7.0.3.250920 not working with Jellyfin

[ManicsMan]

Hi,

The previous version of NextPVR was fine with Jellyfin. I recently updated NextPVR (around 2 weeks ago) and today I suddenly noticed this in Jellyfin's logs:

Error opening input file http://192.168.137.10:8866/live?channelo...7e4f533e08
Error opening input files: Server returned 404 Not Found

Unfortunately,  I can't revert back to the previous NextPVR. What has changed that could have caused this issue?


Thanks,

M

[mvallevand]

I expect the Jellyfin problem is more related to the many channel scans you have been doing and it simply is out of sync.

You didn't explain why you are scanning channels so many times today. Based on another post you re-enabled one tune after six months and it looks like you may have also added another new one to give you 3 tuners. I don't think it is the version, If you aren't finding channels or the reception is bed I think it is how you are splitting the signal.

Martin

[ManicsMan]

I expect the Jellyfin problem is more related to the many channel scans you have been doing and it simply is out of sync.

You didn't explain why you are scanning channels so many times today.  Based on another post you re-enabled one tune after six months and it looks like you may have also added another new one to give you 3 tuners.  I don't think it is the version, If you aren't finding channels or the reception is bed I think it is how you are splitting the signal.

Martin

I bought a couple of USB tuners so I was performing lots of channel scans, which kept failing. Everything failed including playback of TV with my old tuners and new tuners. I cleared everything, rescanned and found Kodi was able to play live TV. Jellyfin failed so I uninstalled the NextPVR plugin and added it back in. It still failed with the http 404 error. I have reduced the number of tuners to a single tuner and it still fails with the same issue, although Kodi was successful in playing Live TV.

There are some numbers in the url that is giving the 404 errors. What do the numbers mean?

[ManicsMan]

I expect the Jellyfin problem is more related to the many channel scans you have been doing and it simply is out of sync.

You didn't explain why you are scanning channels so many times today.  Based on another post you re-enabled one tune after six months and it looks like you may have also added another new one to give you 3 tuners.  I don't think it is the version, If you aren't finding channels or the reception is bed I think it is how you are splitting the signal.

Martin

Looks like the channel ID parameter in the url. I noticed it's different in Jellyfin compared to playback in the web browser. I don't know if it's a Jellyfin plugin or NextPVR server issue so probably something I'll have to look at myself. With time and bit of playing with browser development tools and inspecting the database, I'll probably be able to find the problem.

[mvallevand]

NextPVR reports a 404 to Jellfyin because the channel Jellfyin is asking for is no longer in the NextPVR database after you cleared it. Unlike Kodi Jellyfin uses a very poor interface and so changes in the guide, recordings or channels are not reflected immediately. These are sometimes updated on a Jellyfin server restart but other times they need a run scheduled tasks to reload them.

Martin

[ManicsMan]

NextPVR reports a 404 to Jellfyin because the channel Jellfyin is asking for is no longer in the NextPVR database after you cleared it.  Unlike Kodi Jellyfin uses a very poor interface and so changes in the guide, recordings or channels are not reflected immediately.  These are sometimes updated on a Jellyfin server restart but other times they need a run scheduled tasks to reload them.

Martin

Yes, the 404 error was the big clue. I noticed the channel ID from the jellyfin logs do not exist in the NextPVR server, despite removing the Jellypin plugin and adding it back in. I am now almost certain that this isn't a NextPVR update, but the way that Jellyfin may have cached the channel IDs. I'll figure it out. Thanks for your input.

[ManicsMan]

For those who are interested, the issue is the database. It appears that removing the plugin and adding it back does not clear the NextPVR settings in Jellyfin's database. I know that because upon a clean install of Jellyfin, the channel IDs are different to those of an existing Jellyfin configuration (and the Live TV played correctly from a clean Jellyfin install, due to having correct channel IDs). Incorrect channel IDs would give the 404 error that I saw earlier.

The SQLLite tables are not easy to understand and do not adhere to "normal forms" with lots of repeated data. I'll contact the developers of the plugin to fix this because I'm not spending weeks going through the database and cleaning it up.

EDIT: Refresh Guide Data in Jellyfin fixed it!

[mvallevand]

I am the developer of the Jellyfin plugin and as I said the API is terrible and that you might need to run a scheduled tasks to reload them.

Martin

[ManicsMan]

I am the developer of the Jellyfin plugin and as I said the API is terrible and that you might need to run a scheduled tasks to reload them.

Martin

ok, thanks for that. I'll take a look at the API too. The database design in JF isn't much better.

[mvallevand]

Most of the database add API code came from the MediaPortal port before the Emby and it didn't receive any love since then so don't expect much.

Martin