Unable to Add IPTV XMLTV (m3u works fine)

[add45]

Subscribing to the announcements thread https://forums.nextpvr.com/forumdisplay.php?fid=18 rather then posting release question saves everyone time.

Martin

Kind of uncalled for there but okee dokee

[mvallevand]

Kind of uncalled for there but okee dokee

Everybody typically wants the new version for one reason or another, your reason is relatively insignificant and there is a work around.  Imagine if everyone posted that same question, whenever they wanted it actually takes time from away from getting the solution?  I can easily fix the spam by blocking your posts but that doesn't help others reading the forum.

Martin

[add45]

Kind of uncalled for there but okee dokee

Everybody typically wants the new version for one reason or another, your reason is relatively insignificant and there is a work around.  Imagine if everyone posted that same question, whenever they wanted it actually takes time from away from getting the solution?  I can easily fix the spam by blocking your posts but that doesn't help others reading the forum.

Martin

Come on man, what are you talking about!? Taking time away from getting the solution???

I've added a work around for the next build, where you can add "&contentType=application%2Fgzip" to the url and NextPVR will treat it as gzipped regardless of what google says it is. (effectively allowing you to override whatever google says the content type is)

I tried it here, and google is just ignoring this extra data on the url, but it's useful for us to flag that it is gzipped.

sub is actually being helpful and letting me know that the next version will have the workaround. There is no workaround in the current version for my issue. So it's completely valid for me to ask if sub had made the change available somewhere (e.g.on a dev branch or something a .dll file that I've seen for others with isolated issues on this forum), because it seemed like he wanted me to check from my side if the fix worked.

Obviously I know I can go look at the official release page and see when the latest version was released, that's super unhelpful.
I don't understand why for some reason you have made the decision to be disrespectful to me, I'm a big fan of NextPVR and by all accounts have been respectful in trying to solve this bizarre issue.


But I digress because this is "spam" and doesn't contribute to the issue at hand.
So to rephrase my original question so as to not seem like I'm begging for the next release, is there a workaround I can do in the meantime (whether this is a specific docker branch or a manual file I can use)? If not, that's fine. I would just like to know the next steps.

[mvallevand]

I thought I was being helpful pointing you to the announcement page so you could subscribe since sub can really only give you a general answer like a week or two, and then coming back and asking the question again.

If you don't want to use a raw xml on your google drive file, which is the simple solution in config/scripts create a file called UpdateEPG.sh make sure it is executable with chmod +x

curl --compressed https://drive.google.com... -o /config/filename.xml

Then in NextPVR change your XMLTV name to /config/filename.xml

Martin

[sub]

Sorry, I'm at a difficult stage of the release cycle, where my release isn't entirely compatible with the current production release, so not straight forward to supply individual .dlls. I'm away this weekend coming, but hoping to get the release out next weekend.

[add45]

Sorry, I'm at a difficult stage of the release cycle, where my release isn't entirely compatible with the current production release, so not straight forward to supply individual .dlls. I'm away this weekend coming, but hoping to get the release out next weekend.

 
Sure thing, appreciate it. I should probably look into a better option from google drive anyway.

[add45]

I thought I was being helpful pointing you to the announcement page so you could subscribe since sub can really only give you a general answer like a week or two, and then coming back and asking the question again.

If you don't want to use a raw xml on your google drive file, which is the simple solution in config/scripts create a file called UpdateEPG.sh make sure it is executable with chmod +x

curl --compressed https://drive.google.com... -o /config/filename.xml

Then in NextPVR change your XMLTV name to /config/filename.xml

Martin

I keep getting this with the method mentioned above.

Code:

EPG Update complete. [0 inserted, 0 updated, 0 skipped]

I have manually copied the file into the correct folder and I am even able to load the m3u which is in the same folder. All files have executable permissions. No errors seen...

Code:

[37] About to update EPG


[37] About to run /config/scripts/UpdateEPG.sh


[37] Starting: bash -c "'/config/scripts/UpdateEPG.sh' "


[184] Got request [192.168.0.1]: /services/service (system.epg.status)


[184] method=system.epg.status


[184] parameters:


[184]    method: system.epg.status


[184]    format: json


[184]    sid: 88744af3-c8de-4cf7-993b-3660e550d7c0


[184]    client_ip: 192.168.0.1


[184]    user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0


[184]    host_callback: nextpvr.huss.duckdns.org


2021-05-21 16:38:18    Renewing session: 88744af3-c8de-4cf7-993b-3660e550d7c0


[184] {"stat": "ok", "status": "Running UpdateEPG.sh", "updating": true}


[184] Got request [192.168.0.1]: /services/service (system.epg.status)


[184] method=system.epg.status


[184] parameters:


[184]    method: system.epg.status


[184]    format: json


[184]    sid: 88744af3-c8de-4cf7-993b-3660e550d7c0


[184]    client_ip: 192.168.0.1


[184]    user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0


[184]    host_callback: nextpvr.huss.duckdns.org


2021-05-21 16:38:19    Renewing session: 88744af3-c8de-4cf7-993b-3660e550d7c0


[184] {"stat": "ok", "status": "Running UpdateEPG.sh", "updating": true}


[168] Got request [192.168.0.1]: /services/service (system.epg.status)


[168] method=system.epg.status


[168] parameters:


[168]    method: system.epg.status


[168]    format: json


[168]    sid: 88744af3-c8de-4cf7-993b-3660e550d7c0


[168]    client_ip: 192.168.0.1


[168]    user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0


[168]    host_callback: nextpvr.huss.duckdns.org


2021-05-21 16:38:20    Renewing session: 88744af3-c8de-4cf7-993b-3660e550d7c0


[168] {"stat": "ok", "status": "Running UpdateEPG.sh", "updating": true}


[184] Got request [192.168.0.1]: /services/service (system.epg.status)


[184] method=system.epg.status


[184] parameters:


[184]    method: system.epg.status


[184]    format: json


[184]    sid: 88744af3-c8de-4cf7-993b-3660e550d7c0


[184]    client_ip: 192.168.0.1


[184]    user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0


[184]    host_callback: nextpvr.huss.duckdns.org


2021-05-21 16:38:21    Renewing session: 88744af3-c8de-4cf7-993b-3660e550d7c0


[184] {"stat": "ok", "status": "Running UpdateEPG.sh", "updating": true}


[37] /config/scripts/UpdateEPG.sh has completed


[37] No /config/scripts/PostLoadEPG.sh file found


[37] deleting old conflicts


[37] UpdateAllRecurringRecordings()


[37] Deleting existing pending season recordings


[37] UpdateEPG@5


[37] Exported 1 recordings to '/config/recording-backup.xml'


[37] Exported 0 recurrings to '/config/recurring-backup.xml'


[37] No /config/scripts/PostUpdateEPG.sh file found


[9] Reloading recording schedule


[182] Got request [192.168.0.1]: /services/service (system.epg.status)


[182] method=system.epg.status


[182] parameters:


[182]    method: system.epg.status


[182]    format: json


[182]    sid: 88744af3-c8de-4cf7-993b-3660e550d7c0


[182]    client_ip: 192.168.0.1


[182]    user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0


[182]    host_callback: nextpvr.huss.duckdns.org

[mvallevand]

Does the shell script create the xml file? Are you sure you used the correct filename for the EPG in NextPVR and that you remapped them correctly, entering it can be be a bit of a pain. Check Settings->Guide should show the full filename.

Your snippet didn't tell us as much a a log file would have.

Martin

[add45]

Does the shell script create the xml file?  Are you sure you used the correct filename for the EPG in NextPVR and that you remapped them correctly, entering it can be be a bit of a pain.  Check Settings->Guide should show the full filename.

Your snippet didn't tell us as much a a log file would have.

Martin

the shell script doesn't do anything currently since the file is manually copied in the correct folder. File name is 100% correct and I've retyped it over 10 times

When I checked settings -> guide I noticed it still had the old GDrive URL, so I remove that and added again the local path. Still no luck. I'll attach a truncated log file that **I promise** is the only logs that spit out from me attempting to reload the EPG. (I don't see the need to attach all the old log files from weeks ago)

Is there supposed to be a command in the shell script that actually imports the xml? nextpvr should just be looking for the file and the rest is automatic right? Do I need to add the file:// prefix for the EPG?

[mvallevand]

It is automatic if you have mapped the source to use the new XMLTV file perhaps the channels are still mapped to the http source.

Martin