[roitheoden]

I'm pretty sure it's the wrong address. Up next is a script and the only place where up next is used in the skin are two files that are only slightly modified from the up next script. The error you get (Non-Existent Control 3014) is a harmless error. Only an element was removed, and not in this update, much earlier.

When I have time, and it's difficult, I'll go backwards to 2.0.3 and see if UpNext is working or not anymore. It's curious, there has been no update or modification on this addon, nor Netflix nor Disney nor Amazon. None of them works with UpNext anymore, and UpNext is up to date. I'm fed up with all that, I must admit.... I'm spending days and nights with a big headache !

If you suspect that the new season view is the real problem, try using another view. Certainly the new view uses some hacks. Also delete two files from the xml folder that are related to upnext. These are two files that only regulate the appearance of upnext, nothing else. I tell you again, upnext is a script and is used without integration into the skin code.

I'll do that. 3 machines, 2 windows machines with completely new installation of Kodi + skin titan bingie 2.1.0, 1 migrated, and 3 machines with UpNext kaputt. The problem is completely reproduceable. 

New update : I've deleted skin.titan.bingie then copied my old skin.titan.bingie skin (2.0.3) and previous userdata settings.xml as they are from my save directories. Without ANY other modification, after starting Kodi, Up-Next works again with Disney and Netflix as expected. I stop Kodi, remove again the directories, put the new 2.1.0 directories from another save directory, and... wtf no way, it sucks completely, does nothing under Disney (auto next episode configured) and throughs me an error with Netflix (NextItem doesn't exist). So there's a link somewhere with 2.1.0 and my problem; like the borders problem that I solved by myself.

So, if I don't find a solution tomorrow, I'll downgrade to the previous release, it's a pity.