Next Up widget only shows episodes when there is a previous played episode of that show present on server.

[listy-bit]

Describe the bug The Next Up widget only displays next episodes for shows that currently have a played episode in the Jellyfin server. This is contrary to Jellyfin Web and JellyCon, which display next episodes for shows even when played episodes have been deleted, as long as there was at least one played episode and an unplayed episode co-existing on the server at some point.

To Reproduce

Play e01 Keep played episode Add e02 == At this point, Jellyfin Web, Jellyfin Kodi and JellyCon all display e02 in the Next Up listing Remove played episode e01 == At this point, Jellyfin Web and JellyCon retain the listing for e02 in Next Up, but it is removed from Next Up in Jellyfin Kodi.

Expected behavior To follow in line with Jellyfin Web and JellyCon, and retain the Next Up listing even after played episodes have been removed.

System (please complete the following information):

• OS: Android
• Jellyfin Version: 10.8.0
• Kodi Version: 19.4
• Addon Version: 0.7.8
• Playback Mode: Add-On

[oddstr13]

I suspect that when you delete e01, Kodi no longer knows that the series is being watched.

[listy-bit]

I had assumed the widget populated from a call to the server rather than an internal Kodi thing.

[mcarlton00]

Basically everything about this addon is piggy backing off of internal Kodi things. The only time the server is directly consulted is during the user selection/library selection and if you access a library through the menu that's labeled (dynamic). Otherwise, everything is going through Kodi's local database. If vanilla Kodi doesn't do this, I'm not sure it's even possible for us to do it here.

[listy-bit]

I understand. It's a bit frustrating that I'd have to run JellyCon in parallel just to get the one widget to behave consistently with the rest of the eco system. Perhaps there's a place for a standalone widget addon but that's probably out of the scope of this project's aims.

[mcarlton00]

Removed the duplicate comment.

In theory, it's possible to make a menu option that will always match the server's "next up" view, but it would basically be a one off, so I'm not sure how much sense it makes to do so. And it will be several orders of magnitude slower than the rest of the addon, which may not be the greatest. It's hard to say exactly how much, but doing an API call and processing data coming back from the server is always going to be slower than accessing a local database. It's why this addon is so much faster than JellyCon once the metadata has been synced.