2021-03-30, 05:31 PM
Instructions for this have been added to the wiki
https://github.com/sub3/NextPVR/wiki/Extra-PlutoTV
Martin
https://github.com/sub3/NextPVR/wiki/Extra-PlutoTV
Martin
2021-03-30, 05:31 PM
Instructions for this have been added to the wiki
https://github.com/sub3/NextPVR/wiki/Extra-PlutoTV Martin (2021-03-30, 05:31 PM)mvallevand Wrote: Additionally there a is on optional parameter In any respect, I was not able to get this working this morning. I will re-try later this afternoon when I have more time, and more coffee in my system.
2021-03-31, 03:00 PM
Right I meant 180 minutes. I screwed up the instructions, to it is a dash not underscore too. Importantly I also missed the part that you need to span this a new task typically
start /b "" python C:\Users\Public\NPVR-data\scripts\plutotv\pluto.py xmltv-update 180 or nohup python3 /var/opt/nextpvr/scripts/plutotv/pluto.py xmltv-update 180 & It is a bit of a nuisance for me documenting this for Windows since I work with a linux installation Martin
2021-04-01, 01:35 PM
I forgot to mention that there is an additional feature in this script where updates are not scheduled if the current time after the update is after 10pm or before 7:00 am. In that time the range is deferred until 8 am, but nightly updates will still happen. Feel free to edit the times to suit your needs. The 10pm cutt-off allows EPG data until around 2am.
Martin
2021-04-01, 01:44 PM
Martin,
My server is set go to sleep when there is no activity (watching live, recording) after a period of time, then wakes upon a request from a scheduled event or request from a client. How are updates handled once the server wakes?
2021-04-01, 02:19 PM
I assume your question is related to the timed wait option. The started thread doesn't care about NextPVR and the wait is based on clock time, not a counter. If the PC sleeps past the scheduled time then it will do an update starting in pre-padding time after the wake. There is an assumption, right or wrong, that the NPVR-data drive and the network are available after wake. If the script fails to schedule an EPG update for any reason, there won't be any further timed updates until there is a manual update or the daily update is perforrmed.
A timed update can of course happen anytime even during a recording. The xmltv-update parameter can also be used alone so you can schedule tasks to do this however you want. Martin
2021-04-01, 02:29 PM
All good! gives a lot of flexibility! thanks
2021-04-03, 04:35 PM
Martin:
I have been unable to get this to work. Here's what I have done so far: - upgraded to NextPVR Version: 5.1.1.210329 - downloaded and expanded plutotv.zip into the scripts directory. - created PostLoadEPG.sh with one line: "nohup python3 /var/opt/nextpvr/scripts/plutotv/pluto.py xmltv-update 180 &" - moved the sh file into the scripts directory and chmod a+x and confirmed permissions. Watching the manual EPG update, I can see where it reports that it is reading the PostLoadEPG.sh file. But the update does not run 3 hours later. I do not find any nohup output files which I believe would indicate a reported error. Where do I go next to troubleshoot this? Logs attached. Bob
2021-04-03, 04:59 PM
If you run from the command line
sudo nohup python3 /var/opt/nextpvr/scripts/plutotv/pluto.py xmltv-update do you get an immediate update or any error messages? Martin
2021-04-03, 06:52 PM
Thank you! That showed me where the problem was.
Since I had already set up plutotv in a /scripts/plutotv directory, I must have expanded the zip files into /scripts/plutotv/plutotv directory. There was already a pluto.py file in the path but it was the wrong pluto.py file! Correcting the path did the trick. And now nohup.out reports the update was successful. Maybe I should rename the new pluto.py file so there won't be two of them. Thank you very much, Martin! Bob |
|