Everything was fine yesterday. Today, the devices have disappeared. Re-scanned devices multiple times. Update to the latest software. Still no devices. Log file attached.
Two Windows updates this week KB5066835 and KB5065789 break NextPVR's ability to communicate with digital tuners on Windows. A good starting reference on the issue is here https://learn.microsoft.com/en-us/answer...-10-cumula with
If you haven't installed them yet I would pause your Windows updates until more information is available. I will try updates when they come out, fortunately I only use Windows for testing so it doesn't hurt my production servers.
I have traced the behavior of the NextPVR Kodi addon when initiating a series recording from the Kodi EPG.
In Kodi, this is done from the EPG screen with an episode highlighted, and pressing the "t" key on the keyboard or initiating ActionID "ShowTimerRule".
In Kodi Omega, this is the dialog that appears with the listed settings pre-selected.
At these default settings, the pvr.nextpvr addon creates a recurring_type=3 entry which corresponds to "Record Series (Daily, this timeslot)" in NextPVR.
Changing the "Prevent duplicate episodes" option from All to New when Type=Recording: Repeating (guide) as shown does not affect the recording type that gets created in NextPVR.
Changing the Channel from the specified one to "All" changes the recording type to "Advanced by Keyword"
However, after playing around with the various options circled, I did observe the following resulting behavior.
1. Changing the Type to "Recording: Repeating (all episodes)" has an effect. Alone, it changes the passed recording_type=2 and causes "Record Series (All Episodes)" in NextPVR.
(Too bad this isn't the default option in the dialog).
2. With the Type set to "Recording: Repeating (all episodes)", now the "Prevent duplicate episodes" option works as expected. Changing it as well from all to "New Only" changes the passed recording_type=1 and causes "Record Series (NEW Episodes)" in NextPVR.
3. With the Type set to "Recording: Repeating (all episodes)", if the Channel is also changed to "ALL", no recording is possible and a Kodi error is thrown.
I also noticed in the Kodi logs, that when the ShowTimerRule is initiated it appears that the system is trying to load defaults from somewhere, but I don't know where that is.
See:
Code:
2025-10-15 12:12:15.168 T:5456 debug <general>: CInputManager::HandleKey: t (0xf054) pressed, window 10702, action is ShowTimerRule
2025-10-15 12:12:15.168 T:5456 debug <general>: ------ Window Init (DialogSettings.xml) ------
2025-10-15 12:12:15.168 T:5456 info <general>: Loading skin file: DialogSettings.xml, load type: LOAD_EVERY_TIME
2025-10-15 12:12:15.172 T:5456 debug <CSettingsManager>: requested setting (timer.type) was not found.
2025-10-15 12:12:15.172 T:5456 debug <CSettingsManager>: requested setting (timer.active) was not found.
2025-10-15 12:12:15.172 T:5456 debug <CSettingsManager>: requested setting (timer.name) was not found.
2025-10-15 12:12:15.172 T:5456 debug <CSettingsManager>: requested setting (timer.epgsearch) was not found.
2025-10-15 12:12:15.172 T:5456 debug <CSettingsManager>: requested setting (timer.fulltext) was not found.
2025-10-15 12:12:15.173 T:5456 debug <CSettingsManager>: requested setting (timer.channel) was not found.
2025-10-15 12:12:15.173 T:5456 debug <CSettingsManager>: requested setting (timer.weekdays) was not found.
2025-10-15 12:12:15.173 T:5456 debug <CSettingsManager>: requested setting (timer.startanytime) was not found.
2025-10-15 12:12:15.173 T:5456 debug <CSettingsManager>: requested setting (timer.startday) was not found.
2025-10-15 12:12:15.173 T:5456 debug <CSettingsManager>: requested setting (timer.begin) was not found.
2025-10-15 12:12:15.173 T:5456 debug <CSettingsManager>: requested setting (timer.endanytime) was not found.
2025-10-15 12:12:15.173 T:5456 debug <CSettingsManager>: requested setting (timer.endday) was not found.
2025-10-15 12:12:15.173 T:5456 debug <CSettingsManager>: requested setting (timer.end) was not found.
2025-10-15 12:12:15.173 T:5456 debug <CSettingsManager>: requested setting (timer.firstday) was not found.
2025-10-15 12:12:15.173 T:5456 debug <CSettingsManager>: requested setting (timer.newepisodes) was not found.
2025-10-15 12:12:15.173 T:5456 debug <CSettingsManager>: requested setting (timer.startmargin) was not found.
2025-10-15 12:12:15.173 T:5456 debug <CSettingsManager>: requested setting (timer.endmargin) was not found.
2025-10-15 12:12:15.173 T:5456 debug <CSettingsManager>: requested setting (timer.priority) was not found.
2025-10-15 12:12:15.173 T:5456 debug <CSettingsManager>: requested setting (timer.lifetime) was not found.
2025-10-15 12:12:15.173 T:5456 debug <CSettingsManager>: requested setting (timer.maxrecordings) was not found.
2025-10-15 12:12:15.173 T:5456 debug <CSettingsManager>: requested setting (timer.directory) was not found.
2025-10-15 12:12:15.173 T:5456 debug <CSettingsManager>: requested setting (timer.recgroup) was not found.
If anybody has any insights on how to set the defaults, and whether this is coming from the Kodi code or from within the pvr.nextpvr code, I would appreciate it.
Ideally the goal is to press record on the remote and get a Series recording from the guide without having to fuss changing options in the dialog.
I'm "almost" certain the problem lies in the XML file I upload to the EPG sources section. I had to change my guide system some time ago. Since then, the problems have started. NextPVR freezes and becomes almost unusable. I'm attaching the log files to confirm and identify the offending source.
Thanks, Marco.
It appears that this is a similar bug that was reported in the Kodi section originally last January, but I have determined that it is wholly a NextPVR issue easily reproduced with just a new NextPVR instance and no other client.
Symptom: When a series is scheduled with the "Record Series (Daily, this timeslot)". The entry shows up in the Scheduler tab under recurring as expected, but nothing is queued to record under pending (and the expected entry in the guide is shown unrecorded).
The NPVR logs show a string of error messages:
Code:
2025-10-13 15:50:51.159 [DEBUG][27] LoadListingsMatchingTitle(channel=7154,title=Bob Hearts Abishola)
2025-10-13 15:50:51.188 [DEBUG][27] - ignoring episode at: 10/13/2025 5:00:00 PM (other exact match in timeslot exists at 10/13/2025 5:00:00 PM)
2025-10-13 15:50:51.189 [DEBUG][27] - ignoring episode at: 10/13/2025 5:00:00 PM (other exact match in timeslot exists at 10/13/2025 5:00:00 PM)
2025-10-13 15:50:51.189 [DEBUG][27] - ignoring episode at: 10/13/2025 5:00:00 PM (other exact match in timeslot exists at 10/13/2025 5:00:00 PM)
2025-10-13 15:50:51.189 [DEBUG][27] - ignoring episode at: 10/13/2025 5:30:00 PM (other exact match in timeslot exists at 10/13/2025 5:00:00 PM)
2025-10-13 15:50:51.189 [DEBUG][27] - ignoring episode at: 10/13/2025 5:30:00 PM (other exact match in timeslot exists at 10/13/2025 5:00:00 PM)
2025-10-13 15:50:51.189 [DEBUG][27] - ignoring episode at: 10/13/2025 5:30:00 PM (other exact match in timeslot exists at 10/13/2025 5:00:00 PM)
2025-10-13 15:50:51.189 [DEBUG][27] - ignoring episode at: 10/13/2025 5:30:00 PM (other exact match in timeslot exists at 10/13/2025 5:00:00 PM)
Reproduction:
Brand new Version: 7.0.3.250920 installation on Windows 10. Configure channels and guide data.
Click on a show in the guide, select Advanced, then under Recording type choose Record Series (Daily, this timeslot), Then Save.
The corresponding entry in the guide will remain unrecorded and does not record.
Logs are attached. I've also included the database file in the zip if that helps.
I also think this may be a regression since it does not appear that the prior version 7.02 suffers from this issue.
I have the current version of NextPVR operating on Windows 10. I am using two HDHomerun tuners: one the old HDHomerun Dual (HDHR3-US), and the other is the newer HDHomerun Connect Duo (HDHR5-2US). Most of the channels are configured to use Schedules Direct, but in a few cases I need to rely on the 8VSB PSIP for EPG data due to it not being available from Schedules Direct. Generally that works, but lately the schedule information is wildly incorrect on one specific channel (31-3... HNI). I have tried Emptying the EPG and Updating it, as well as rebooting the computer. I have confirmed that the schedule data for that channel is actually being broadcast correctly, both by looking at the EPG display on my TV, as well as using TSReader to monitor the HDHomerun output directly. Note that the older tuners are first in the list of devices due to their being slightly more sensitive than the newer model.
Any ideas on how to resolve this issue? I don't know exactly when this problem started, so I can't say for sure whether it started after I upgraded to v7.0.3 on October 2 (from v7.0.2). I attached the logs, captured shortly after manually updating the EPG after verifying I had good reception of channel 31.
I have used these forums in the past but just registered to post, I have used NextPVR ever since Microsoft quit supporting updates for Windows Media Center. I am moving from an old Win10 computer to a new Win11 computer.
My old original 5.0 install on my old Win10 computer, updated regularly and recently to 7.0.3.250920, is working fine updating its program schedules manually and automatically correctly using Schedules Direct. This computer is using a very old Hauppauge 4 tuner card from 2 computers ago with a second hard drive for storage.
The new computer is using a HD Homerun 4 tuner device and I installed the HDHR software scanned for channels and it works as it should, but I prefer NextPVR. I then installed NextPVR 7.0.3.250920, scanned for channels and all looked well on all 4 tuners with my normal lineup of channels. I put in my username and password to get updates but it will not update its programs schedule. One odd thing is when I go to put in the password in NextPVR the default display has a blank something like ** *****. I doubt that has anything to do with this, but its odd.
I can log into my Schedules Direct account and my username and password are working on the old computer so they must be correct. But, when I try to update my program schedules I get the finished indication, but it shows 0 loaded, 0 updated and nothing appears in the guide. As per one post here I did Automap the channels first to none and then to local lineup on Schedules Direct, but that did not help. I am guessing from there being nothing to map. I had read that having both HDHR and NextPVR will likely work, but is this creating a problem that is messing up the NextPVR's ability to update? My next move may be to uninstall HDHR, but I would prefer not dong that. I am reluctant to copy the data files from my old computer to my new one since it is using completely different tuners which might cause issues.
One last thing. I went to the before you post instructions on posting my logs. I could not find a "Go Advanced" button to push so I zipped the files and copied them to the Attachments box.
Ever since the update on all my TV computers, the 1-minute forward and fast forward features no longer work. I no longer have a 1-minute fast-forward. I used it a lot. I miss it very much. When I click on fast forward, it sometimes skips all the way to the very end of the program or back to the beginning. I have to guess with my arrow to skip the commercials. It takes a lot of time and rarely starts at the program segment. How do I fix it? I would like to have these features back on the screen and functioning correctly.
I am used to work in windows 10 but since it is going to be abandoned by Microsoft I am switching to linux for my NPVR backend.
I have a problem where the UpdateEPG.sh script that is in /var/opt/nextpvr/scripts/ is not creating the XML when executed from the WEB admin page.
It is WORKING if I call it manually from the command line, but then if I do that, the EPG in NPVR will not get updated even if the xmltv.xml was created...
I am going nuts over this
here is the content of my script located
here:
/var/opt/nextpvr/scripts
with following permissions:
-rwxrwxrwx 1 nextpvr nextpvr 142 Oct 8 17:26 UpdateEPG.sh
Code:
#!/bin/bash
cd /zap2xml/zap2xml
node /zap2xml/zap2xml/dist/index.js --lineupId=CAN-0004590-X --timespan=180 --country=CAN --postalCode=XXXXXX
