EPG Update problem

[jcjefferies]

I bought a SAT>IP tuner several years ago but NextPVR & EPG Collector both don’t work with it on my server. It was not important as I had a twin DVB-S2 and twin DVB-T2 tuners and use the SAT>IP tuner for live TV with TVheadend! However one of the DVB-S2 tuners failed recently so investigated the SAT>IP tuner on a clean install of Windows 10 on another PC and the tuner worked as it should with both NextPVR and EPG Collector. The SAT>IP tuner still worked when the disk was put in the server with the DVB-S2 tuner in place and drivers installed.
 
So back to testing with the disk on the separate PC with no connected tuners so not to interfere with daily recordings. I edit UpdateEPG.bat to remove the DVB-T2 related entries just leaving the very basic DVB-S2 related entries. If I run UpdateEPG.bat in a command prompt or double click in file manager it runs as expected and creates the xml EPG file!. However if I login to web admin and click "Update EPG" it stops almost immediately with "No tuners detected" error! Under Devices on Web Admin 4 SAT>IP are listed and not disabled!
  
Enclosed is the log file.

I run updateEPG.bat 16:27:00
Finishes 16:30:04 success! Xml file saved to directory C:\EPG
 
Log onto web admin and click Update EPG 16:35:00
16:35:01.017 “No tuners detected”
 
This is now the only data in the file “UpdateEPG.bat” which has worked with the original tuners in the server for many years!
"C:\Program Files (x86)\Geekzone\EPG Collector\EPGCollector.exe" /ini="C:\EPG\EPG Collector Freesat.ini"
 
Chris

[mvallevand]

These messages appear to be coming from EPG Collector not NextPVR so NextPVR is running your script.

2023-10-16 16:05:59.520 [DEBUG][28] > Number of devices: 0
2023-10-16 16:05:59.520 [DEBUG][28] >
2023-10-16 16:05:59.521 [DEBUG][28] >
2023-10-16 16:05:59.524 [DEBUG][28] > <e> No tuners detected
2023-10-16 16:05:59.524 [DEBUG][28] > <e> Exiting with code = NoDVBTuners

You also have a problem in your post update EPG script

2023-10-16 16:06:07.490 [DEBUG][21] > 'dotnet' is not recognized as an internal or external command,

And I note that output is set to C:\EPG\TVGuide_Freesat.xml but in NextPVR you seem to be reading from C:\EPG\TVGuideFS.xml Maybe your post update script renames it when it works?

Martin

[jcjefferies]

Yes I know EPG Collector is not finding any tuners so was hoping you could see a NextPVR error or problem to explain why. What is so different about running UpdateEPG.bat from within NextPVR that prevents EPG Collector finding tuners when it otherwise finds them as I showed in the logs.

The two problems you noted at the end of your message are not relevant as I am testing on several test disks but only setting up the parts relevant to just running UpdateEPG.bat.

Chris

[mvallevand]

NextPVR is running fine, detecting SAT>IP but also no tuners and running the batch file which seems to run and exit immediately. There is nothing in the stdout from your batch file showing an error, or an attempt to scan SAT>IP and we don't see the stdout from when you run it manually to compare.

The only suggestion might be to run the NextPVR service as a user.

Martin

[jcjefferies]

Running NextPVR as user did not help so I posted the problem to "EPG Collector". Not much help there as "EPG Collector" scans seem to crash immediately when using the SAT>IP tuner and started from NextPVR Web App but produces no log file to examine!

However the simple work around is to run "UpdateEPG.bat" with the Windows "Task Scheduler" and everything seems to work as expected! Not ideal but it seems to work!

Chris