epg . n**** - development and discussion

Status
Not open for further replies.

psycon

enlightened one
Feb 25, 2015
0
10
0
In the hills
12/31/16 This EPG method is no longer supported.

---
New Feb 14:vGet the ********** updater and repo from http://**********

Note: The 24 hour pull does not show details and is for devices with lower ram.. the 72 hour has the show details.

See Here for install instructions : http://iptvtalk.net/showthread.php?13053-How-To-Set-up-pvr-stalker-nfps-with-epg-ninja

Note: if you cannot seem to connect to the ********** site, its because your current client has been trying to connect to the old links non stop and the site has banned your IP.. Dont worry, its only temporary. Just remove the old links from your client, or disable it, or close just kodi for an hour and you will be unbanned..

Note 2: If you have set up the version of Stalker Client that is included with kodi, switching to this version isn't really necessary, you wont gain anything different with it, this is just the easiest way to new users to get up and running





Code:
Advanced  Alternative setup:  for use with version of Stalker that is included with Kodi only. If you dont know what your doing.. dont use this method. install pvr.stalker.nfps instead. Do not ask for support for the advanced method in this thread

Set your EPG remote URL to hxxps://papiao.is/main/EPG/mac/00:1A:78:XX:XX:XX/donation/XXXXXXXXX/fname/NFPSF1

Leave all  the value headers in the URL (do not remove the words mac, donation, or fname leave them there, only change the X's)
Replace all the XX's with  your Mac or Donation
NFPSF1=24 hour, title only. (use this on fire tv stick or other low ram devices)
NFPSF2=24 hour title only offset one hour, for those having issues.
NFPSF3=72 hour with details
NFPSF4=72hour with details offset one hour, for those having issues.

For IPTV66, replace "papiao" with IKS66
 
Last edited by a moderator:
Not All TV Guide Data Loads

So after all my channels\guide info loads...I open TV Guide. Some channels have info and some dont. Alot of them have data pulled from time that has already past but not anything current or future. Ive closed out kodi and tried reopening to reload everything but i get the same outcome. Any thoughts?
 
i'm curios. since dvbken does not seem to have integrated login/password in the "nfps" pvr client 1.01; won't it stop working feb. 1st as announced elsewhere on this forum? or does anyone know if something is in the works? and is the date finally confirmed? I know the subject is kinda on the edge but it is tied somewhat to this thread also.

regards
 
Last edited:
@ djlopez92: if your guide has "data pulled from time that has already past but not anything current or future" it sounds like the problem I got help fixing here yesterday. At least your description of the appearance of your guide is similar, as mine had channels with no data (actually, no current data, if I scrolled far enough left there was old data). Try the steps in that thread, couldn't hurt.

@ tuxen: I'll be interested in the answer to this as well, as I assumed that the latest version of PVR Stalker NFPS would assemble the login/password under the hood like it does all the other credentials. All it needs is the donation number, and it has that.
 
Hi alls

Having an issue with epg data not being offset - some shows are wrong for the time on the listings .. Ive tried NFPSF2 AND 4 and its still the same .. ive cleared data, disabled live tv and rebooted but still the same on some channels ..

Just wondering if anyone has encountered this ??
 
@ tuxen: I'll be interested in the answer to this as well, as I assumed that the latest version of PVR Stalker NFPS would assemble the login/password under the hood like it does all the other credentials. All it needs is the donation number, and it has that.
to my knowledge all the current version does is set the serial number for you, it has the credentials already yeah but it is not using them. a little check box to enable the donation number to login would have be needed to make it future proof. lets hope dvbken updates the addon, but it probably wont happen until the login is required since the date seems to be pushed back. which leads to the second question; is feb. 1st finally confirmed?
these questions seems to span multiple threads, and this might not be the most appropriate. but I don't want to clutter the same questions all over, and think i'm not the only one wondering about these things. oh well I think we just have to wait 2 days and see what happens, it's not the end of the world. :)
 
Hi alls

Having an issue with epg data not being offset - some shows are wrong for the time on the listings .. Ive tried NFPSF2 AND 4 and its still the same .. ive cleared data, disabled live tv and rebooted but still the same on some channels ..

Just wondering if anyone has encountered this ??
yeah I have and several friends. change your mac address (link a new mac) use NFPSF1 or 3 and it will correct itself.
remember to change the mac in the epg url also.

also remember the client fails for some reason at first attempt to load channels after changing mac, just re-enable the addon or tv function.
 
Last edited:
It depends on what 'latest' version of the pvr.stalker.nfps you are using. I don't think 0.8.4 autofills the login/password, nor does the expermentals in epg.ninja. The newest version 1.0.3 isn't out yet for the public, but I believe it will work going past 1 February, as it does take the donation number and autofills the login/password, at least in the debug log.

The February 1 date as far as I know isn't pushed back, but it isn't set in stone either.
 
Hi alls

Having an issue with epg data not being offset - some shows are wrong for the time on the listings .. Ive tried NFPSF2 AND 4 and its still the same .. ive cleared data, disabled live tv and rebooted but still the same on some channels ..

Just wondering if anyone has encountered this ??

use pvr.stalker.nfps instead. it shoudl fix the offset for you..

if you cant though.. when you switch from NFPS 2 to NFPS 4. you have to go into file manger>profile directory and delete the epg cache from the userdata/addon_data/pvr.stalker . as well as delete EPG11 and TV29 from your database folder, then restart kodi
 
use pvr.stalker.nfps instead. it shoudl fix the offset for you..

if you cant though.. when you switch from NFPS 2 to NFPS 4. you have to go into file manger>profile directory and delete the epg cache from the userdata/addon_data/pvr.stalker . as well as delete EPG11 and TV29 from your database folder, then restart kodi
sure it will coz he will have to change mac address for the new serial.
just link a new mac and the standard pvr addon will also fix itself. delete db files and if using kodi 16 delete cached epg file to be sure.
what puzzles me is why you guys do not test it. I just did again.. oh well, i'm not gonna argue this or say this anymore.

edit: it seems the client does not fail anymore at first attempt after changing mac. if its the standard 1.0.3 client or nfps that fixed something, I dunno.
(I dont have the 1.0.3 nfps client but I assume they have the same behavior)
 
Last edited:
use pvr.stalker.nfps instead. it shoudl fix the offset for you..

if you cant though.. when you switch from NFPS 2 to NFPS 4. you have to go into file manger>profile directory and delete the epg cache from the userdata/addon_data/pvr.stalker . as well as delete EPG11 and TV29 from your database folder, then restart kodi

Hi - Thanks for the reply - tried what you said and still the same ... I'll try the other pvr you mentioned in the morning

Will also try a new mac as mentioned ****EDIT - tried new mac and changing to nfps 3 and no change

Thanks for the replys
 
Last edited:
changing mac does not affect time offset. selecting the right xml file and resetting your database does..
yeah you are correct but there are cases where nfpsf1 or 2 wont work anymore, depends on what has gone wrong. if the local time or the timezone affects the time at some point for example, there are cases where nothing helps but resetting the mac. (DST or screwing with the emulator is a good example) but it looks like the error is located :), although the provider data should match nfpsf1?.
 
Last edited:
Status
Not open for further replies.