New EPG Updater plugin

Status
Not open for further replies.
instead of downloading to the pvr dir if you run the normal nfps client i 'modified' the script to download to the service.stalkerEpgUpdate directory and then just load it as normal in pvr.stalker 16 or 15 this feels more natural to load the file this way. also since i couldn't get it to think it had a cache file no matter what did, the same happened from some of my family, i honestly dont know why maybe because some had the cache function off to start with. (i of cause turned it on)

pointing to the file worked as a charm the first time. it does seem to have some obvious advantages.

anyway i'm loving the simplicity of the addon, the cron function. and of cause the obvious ingenuity that comes with it, i really hope you keep it for the built in stalker, even if it becomes integrated in stalker nfps.
using the method above works really good with it, i only moved the file to not interfere with kodi 16 natural cache function, so it wont matter if its off or on. and the addon's data dir seemed obvious.

thanks
 
Last edited:
nice work i just set the url in the 15 version of kodi with pvr stalker from remote to local same link and the epg fire up without any issues and my kodi has a setting of -1 for logging so i get no logs cache is always at zero, it was the link that got me thinking why remote url when the epg is downloaded lol
 
yeah but since kodi 16 (i use kodi 16) has caching and kodi 15.2 does not and this addon originally relies on updating that cache file to make the client think that the epg has been updated, i was affraid what oddities might happen if you at the same time pointed it to load it's own cache file as epg if caching also was turned on. maybe nothing heh but now not much will happen and it seemed more logic. i would barely call it a modification though lol.
 
Last edited:
I am getting an error on start up after installing the Stalker EPG Updater and im running Kodi 16 RC2 with the stalker NFPS Client on android. What is this pointing to the local path that everyone is talking about? Is that what i need to do? If so how?

Thanks in advance!

EDIT: By the way i have looked for the how to threads and couldnt find them so sorry
 
Last edited:
I am getting an error on start up after installing the Stalker EPG Updater and im running Kodi 16 RC2 with the stalker NFPS Client on android. What is this pointing to the local path that everyone is talking about? Is that what i need to do? If so how?

Thanks in advance!

Check the tutorials for the client's epg integration that psycon has posted.
 
Thanks for the reply but all i could find in that thread was how to configure stalker nfps client related questions and answers nothing about epg.....

It's clear as day on what to use for the "remote" path. psycon's instructions are not subject to interpretation... if you follow them, you will link, and get your guide. The path is necessary for Kodi 15, but it only has to be filled in with a dummy value for Kodi 16.
 
It's clear as day on what to use for the "remote" path. psycon's instructions are not subject to interpretation... if you follow them, you will link, and get your guide. The path is necessary for Kodi 15, but it only has to be filled in with a dummy value for Kodi 16.

Ok, i get it now, the instructions are for the BUILT IN Stalker client under the XMLTV Scope: you can change the values there. I am using the Slalker CLIENT NFPS, there are none of those settings for that in the CLIENT NFPS. I guess i will change over to the BUILT IN stalker client and my issues will be resolved.
Sorry for all the confusion and thanks for the heads up!
 
Ok, i get it now, the instructions are for the BUILT IN Stalker client under the XMLTV Scope: you can change the values there. I am using the Slalker CLIENT NFPS, there are none of those settings for that in the CLIENT NFPS. I guess i will change over to the BUILT IN stalker client and my issues will be resolved.
Sorry for all the confusion and thanks for the heads up!

Actually, the loader will work with the NFPS client in Kodi 16, just fine. The problem today is that the updated 1.0.3 client isn't available in the epg.ninja repo, so if you have an earlier version, you may not get it to work. Anyway, do try it with the built in client, and you later see how much easier it is to set up the NFPS version.
 
EDIT: dont know why i replied to your message dara, i miss read it and looking it over it was quite messy and out of context. sorry, i'll shorten it up lol.

it seems the client does not even cache the file if its set to point to a local location or a local file. heh. that explains the issues i and some others experienced here, it has point to a remote dummy file at least.

so trying using the 15.2 method if you have trouble is ok with the built in kodi 16 client. while we all wait for the new stalker 'nfps'. :)
 
Last edited:
Actually, the loader will work with the NFPS client in Kodi 16, just fine. The problem today is that the updated 1.0.3 client isn't available in the epg.ninja repo, so if you have an earlier version, you may not get it to work. Anyway, do try it with the built in client, and you later see how much easier it is to set up the NFPS version.

Just a quick update for those looking for the 1.0.3 version... the zip files are now available via the epg.ninja site. The repo still doesn't have the jarvis versions though.
 
Status
Not open for further replies.