This situation (although usually only 2-3 recordings) occasionally happens to me, but it's been infrequent and I generally don't notice in time to grab logs. This time I did.
In the log .zip, I added a HDHR_Log_2025-12-05.txt file which is the System log from the HDHR Quattro. The tuner there shows errors like
Code:
20251205-04:35:01 Tuner: failed to tune 4.1 WCCO-DT (8vsb:581MHz-1)
20251205-04:35:01 HTTP: rejecting request from 192.168.143.10 - tune failed
each time, so I believe that the root cause may be something in the HDHR. I was running a 2023 version of the firmware and there was a 2025 version available. I thought that I had updated to that 2025 version when this happened the las time, but apparently not. I have done that now, so maybe that will resolve the issue on the HDHR side. We'll see.
The problem doesn't appear to be tied to any specific HDHR tuner or channel. In the log, I am seeing all 4 tuners being used successfully. And on any given night when the problem occurs, it affects different channels, but the same channels will also sometime records successfully the same night.
One interesting thing is the on the NextPVR recording end, I get 2 different failure messages/reasons: "HDHR stream not available" and "Recording interrupted". I feel like every time that this has happened, I've gotten a combination of these 2 failure messages. I'm not sure what the difference is.
It does appear that when the failure occurs, NextPVR is attempting to tune the channel multiple times using different tuners:
It appears that at 04:34:00, NextPVR first attempts to tune 4.1 on tuner0, the HDHR doesn't give a "tune failed" error, but NextPVR immediately (also at 04:34:00) closes the connection ("20251205-04:34:00 Tuner: tuner0 http stream ended (remote closed)") and immediately attempts to tune 4.1 on tuner2 which also immediately closes that connection ("20251205-04:34:01 Tuner: tuner2 http stream ended (remote closed)"). Then it immediately attempts to tune the same 4.1 channel a 3rd time which results in the "tune failed" error from the HDHR at 04:34:01.
Hi everyone,
I just installed a fresh copy of LibreElec 12.2.1 on a Raspberry Pi 2. I have the DVB-T2 Hat. I installed the NextPVR backed and I connected to the web interface. I can see the device "adapter0/frontend0 (Sony CXD2880)", but when I open the "Scan Channels" form, the combo box with the country list is empty and is not possible to start the channel scanning.
Using TVHeadEnd the channel scanning is succesful and it's possible to see the TV, so the hardware seems to work correctly.
How can I fix this problem?
I was scrolling ahead in the program guide overlay (live TV showing in the background), when at some point the display stopped and then the NextPVR.exe window disappeared a couple of seconds later.
Because this happened at least once before, now I know it's not a one-off situation so I'm attaching the log .ZIP for investigation.
FWIW, at the time I was using the right-arrow on a WMC remote to move through the guide.
Thanks in advance for any insights or solutions you might suggest.
When I tried to switch a program in the Client's TV Guide to Live TV it basically got stuck and froze same when I clicked on "Live TV".
Thought maybe the program was corrupted since I thought Live TV came from the TV Tuner card in my PC and not the Internet. So I used the NPVR Setup installation .exe file to reinstall it but forgot it needs an internet connection to download the latest version .exe file and I had a older version downloaded of NPVR.exe file on my drive.
Live TV did work in Firefox NPVR web app though but not in the client.
Today I got my DSL Broadband working again and now NextPVR Live TV is working normally again. A little slow to start but works fine.
KODI was working normally as far as recording TV shows and playing the recordings except with KODI Extensions that requires a Internet connection to work.
So I was just curious as to why "Live TV" stopped working in the NextPVR Client when i lost my Broadband connection.
I noticed my guide was way out of date, so I attempted to do a manual update and got this error "Server offline for maintenance" My guide currently has only 1 week of programing. However, that isn't entirely do to the issue, since I use Ethernet tethering with my phone for home internet and sometimes fail to hook up for a few days. However, I was hooked up a couple of nights ago, so the problem must have been there at that time. My SD account is paid through February. What could be wrong? Here's a link to the logs https://drive.google.com/file/d/1DgEIr-W...drive_link I tried deleting all older logs from the zip, but it's still over 2mb.
Current setup as per signature all using NextPVR v7.0.3.250920
On this occasion the recording was made, correctly (kind of), on the RPi4 server.
The issue that is causing me problems is not with the recording itself but why the recording was made ?
As you can see the recording started at 15:59 on Nov 28 and completed at 17:05. However this recording was not scheduled by me and the path/filename is completely incorrect for any of my NextPVR recordings:
From the recorded filename used however I can tell that this is a previously imported recording (from my old Humax box) which I transferred to NextPVR some 3 years ago.
So what caused this programme to get recorded again with an old file name ?
