[im85288]

No problem, thanks I will take a look and post back when I have more information, just one last quick question are you using strm files (as they often do not work correctly with this addon)?

[im85288]

Looking quickly at your log I see the following:

media{"id":1,"jsonrpc":"2.0","result":{"item":{"episode":-1,"label":"Brooklyn Nine-Nine S01E01","playcount":0,"season":-1,"showtitle":"","tvshowid":-1,"type":"unknown"}}}

The key problem here is the tvshowid being -1, this normally from my experience occurs with strm files, in fact the episode and season are also -1 so the data is not scraped correctly in Kodi.

Unfortunately I do not have a solution for strm files, it has been proved to work if you add your strm files to Emby and get Emby to scrape the data but I'm not sure if you want to go that route.

Cheers

[Vonspiel]

Ha! This is what I did. Everything is handled by Emby now, but it seems nothing changed.

[im85288]

Ha! This is what I did. Everything is handled by Emby now, but it seems nothing changed.

To be honest I have never tried it myself but if you look back earlier in the thread somebody successfully got strm files working using Emby. As you can see from what I posted in your log it is supplying this addon with incorrect values so cannot select the next episode to play.

[Vonspiel]

Yes, I read the whole thread and it seemed Emby was the solution. However, it doesn't work for me. Maybe one day it will
Anyway, thanks for trying to help.

[Razze]

Ha! This is what I did. Everything is handled by Emby now, but it seems nothing changed.

Care to give another logfile?

[Vonspiel]

There you go: http://pastebin.com/AY3w77Xr

[Razze]

There you go: http://pastebin.com/AY3w77Xr

Your still missing the data in Kodi, have you scraped the strm to the library?

[Vonspiel]

all my tvshows are now scraped by Emby... I do not know what to do...
(I sent you a PM)

[paradix]

Cool addon but noticed something funny. Not sure if mentioned before but when you partially watch next episode for a few minutes only and stop, nextup thinks it's fully watched. So when the next time nextup kicks in it will skip that episode and will ask you to play 1 episode ahead (or further to one that has never been watched before)

The same issue has been happening on my setup. Any idea if/when this can be fixed?
As I browse through the code of the .py scripts I don't really see the cause, so maybe there is a bug in the JSON method that's called to play the next episode.

[Vonspiel]

Updating to Isengard actually fixed the issue, Next Up is now working on my setup. It's freaking awesome!
However, the box where the fanart is supposed to appear remains empty.





I found this in the log that may explain this:

Code:

13:05:39 T:4788   ERROR: EXCEPTION: Non-Existent Control 3009
13:05:39 T:4788   ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
                                             - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                            Error Type: <type 'exceptions.RuntimeError'>
                                            Error Contents: Non-Existent Control 3009
                                            Traceback (most recent call last):
                                              File "C:\Users\VONSPIEL\AppData\Roaming\Kodi\addons\service.nextup.notification\resources\lib\NextUpInfo.py", line 45, in onInit
                                                self.getControl(3009).setImage(image)
                                            RuntimeError: Non-Existent Control 3009
                                            -->End of Python script error report<--

Here is the full log in case you want to take a look at it: http://pastebin.com/MAJ7AS14

[im85288]

Thanks! It is pretty cooll

That error looks like the skin your using has not defined control 3009 in the XML. Have you tried it on a skin (such as confluence) that uses the default skin XML?

[im85288]

Actually it was an error in the latest version.

Can you try this version to see if that fixes it: 1.0.10

[Vonspiel]

Yes, both screenshots are from 2 different skins: Eminence 2.0 for the first one and Confluence for the second one. I also tried to uninstall NextUp and reinstall it but got no success.

EDIT: we posted at the same time! Trying 1.0.10 now.

[paradix]

I had a similar issue when I was making the NextUp Dialog for my CirrusExtended skin.
This problem occurs when the image 3009 (or any other that is being set by the script) has a bordertexture.
Check if the skins custom dialog is coded with a border.