EPG wont update, device not correct, channels won't import

[LateNightCat]

I had previously installed NextPVR with a Hauppauge Collosus 2 PCIe card in 2023.  I had successfully imported channels from xmltv at the time and I believe it was auto updating.  I was unable to get Hauppauge IR Blaster to control my Bell (Arris) 2502 STB however and gave up for a long while.  

This week I tried harder and I was able to get the Hauppauge IR blaster to learn the IR codes from my Bell remote.  
And I wanted to use the NextPVR IR blaster wrapper to PVR but I soon found I was unable to update the NextPVR channel listings.

I foolishly emptied my EPG and then tried to setup the device and update the channels and listings.  Nothing was imported (0/0/0). I then noticed that the Hauppauge device was showing as a HDPVR (Sienna Crossbar) and not the Colossus.  I updated Hauppauge Capture and WinTV10 to be sure I had the latest drivers.  Windows device manager is showing I have the latest drivers for the Colossus.  I uninstalled NextPVR and reinstalled only to fail again at importing channels and the device in NextPVR is still showing as HDPVR.  Hauppauge Capture and WinTV10 are both working as they should.  NextPVR will not import channels for my device.  NextPVR is even saying no devices are active even though it appears in the device list.
I am stumped.  Any suggestions appreciated.
Log file attached.
Thanks

[mvallevand]

I think that you misunderstand the problem the h/w device is for 3 HDPVR/Colossus/Sienna tuners

What I expect is the problem is the problem that you original scanned your channels with and is used for the daily update no loner exists.

2025-11-05 22:48:22.202 [DEBUG][23] Unable to process xmltv file: C:\Users\reglo\Downloads\xmltv-4384.xml (file not found)

Martin

[LateNightCat]

Thanks for responding. 
If I understand you correctly, you are saying NextPVR sees HDPVR/Colossus/Sienna tuners as the same device.  (I only have the Colossus installed with the correct drivers)
And because I may have changed my device from an HDPVR to a Colossus the channel scanning no longer works.
I tried an uninstall, restart and reinstall of NextPVR after updating both Hauppauge WinTV 10 and Capture (correct up to date drivers for Colossus.)
XMLTV seems to be having issues and timing out without delivering downloads so I tried schedules direct.
Schedules Direct does not import any channels either.
I have attached a new log after the schedules direct attempt to add channels to the Colossus device.
Any more suggestions?

[mvallevand]

No I am not quite saying that but lets' restart and ignore you blaster for now.

Stop the nextpvr service and go to c:\user\public\npvr-data and rename your npvr.db3 to something. The follow the steps on the wiki https://github.com/sub3/NextPVR/wiki/setup-set-top-box

If that fails send the zipped logs from the main web setting page.

Martin

[LateNightCat]

Thank you again for responding.

A bit of success to report.  (I saw your post after I tried some other things so I have not yet followed your advice yet)

After failure to download listings from XMLTV in two web browsers or from within NextPVR I contacted XMLTV support.
They suggested I try XMLTV Grabber.
Unfortunately, Grabber would not install.

So I tried downloading the XMLTV data from a web browser on a Mac and that worked!
I transferred it over to my windows 10 computer and I was finally able to update the channels and schedule within NextPVR.
At least I have a manual process to load schedule data.
(BTW, ScheduleDirect did not work for me in NextPVR either)

I don't know why my pc times out on the XMLTV download whether in a browser or in the NextPVR app.
And I will try to sort out why the grabber did not work.  I am probably missing some required files.

NextPVR is sending IR codes through the Hauppauge IR wrapper.
Colossus is working as an HDPVR in NextPVR with one exception. 

My Bell (Arris) 2502 STB requires a "Select" or "Enter" code to wake the STB from sleep and to change channels.
While I was able to "learn" the "Select" code as "Enter" in Hauppauge IR BlasterConfig and send it in test, when I press the "OK" button that is mapped to "Enter" on my Hauppauge remote, no IR code (or the wrong code) is sent to my STB.
As a result, the NextPVR cannot change channels or execute a scheduled recording unless I manually wake up my STB which is ok if I am watching a show but not yet helpful in terms of unattended recording of shows.
(The Bell STB also goes to sleep after 4 hours unless you press any remote button before that time runs out which is very annoying)

Any thoughts on how to solve:
a) xmltv download timeouts from within NextPVR?
b) how to get the Hauppauge remote OK button (or a unassigned coloured button like the green button) to send the right code to my STB to wake up? 

(I have looked at IRRemote.ini but I am not sure how to edit it or how those entries are mapped to specific codes.  I have reached out again to Hauppauge support but they have not responded in 3 days and appear to be offline)

[mvallevand]

I'm sure Schedules Direct will work fine once you set it up properly it could be related to why you can't download XMLTV (firewalls VPNs etc) We might be able help with Schedules Direct if you send the zipped logs, but you would need to get your UpdateEpg.bat file running first.

To send the enter you should create a batch file that takes the parameters from NextPVR. Confirm the batch file works and then remove the channels with the trash can and call that batch file as the blaster script. That is how I do it with Rogers and an Arriis box.

Martin

[LateNightCat]

I found a KeyMappings.xml file but I have yet to find the UpdateEpg.bat file. Where would I find that?
The KeyMappings.xml file does not seem to have an "Ok" or "Enter" in it....

[mvallevand]

KeyMappings.xml will have nothing to do with the blaster.

As for finding scripts rather than poking around I've already shown you where the wiki was so read it before posting.

Martin