HVR-2250 scan only finds 3 channels

[baj1]

I probably shot myself in the foot here. I checked the splitter in the basement and my office connection is the only RG59 left in my box, it's the original wiring in the house. I added 2xCAT5 and 2xRG6 quadshield to every major room 20 years ago, but apparently never terminated the RG6 cables to my office.

Anyway, my money is on this old cable being the source of my weird problems. :-\

[BrettB]

I would like to upgrade to v5 but can't.  v5 doesn't support the NMTs/PCHs, and I understand that it won't.  My wife is frustrated by change, and with her mom living with us due to C-19 and everything else going on in the world at the moment, converting her to Kodi right now isn't in the cards.  WAF -> 0.

You are correct that v5 does not (and will not) support the NMTs/PCHs. However, if you use Kodi with Knewc in Remote GUI mode, it is the exact same interface that you get on the NMT/PCH. I switched from the PCH to Kodi/xnewa on an RPi when my last NMT died many years ago. I don't have the RPi/Kodi go directly into the Knewc Remote GUI, but I know that is (or at least was) possible to configure if that's what you really want/need for the WAF.

[baj1]

I use Kodi with knewc, but when I tried to "role it out" the frustration factor was still too high for her. I have two ODroid N2's and one RPi4 that boot direct into knewc, but it's not perfect. It closes on it's own and dumps back to Kodi a fair amount. I suspect some of it is due to my dying NextPVR server PC, but right now the PCHs are more stable and a "known" for her. She won't take the time to learn Kodi right now. I had the idea the other night to program a remote button (maybe GREEN for "go") to launch knewc so she doesn't have to navigate to it if knewc closes. Still might not be enough though. As for PCH's, I had the Ethernet port on one PCH die, but have two more that I replaced with Kodi devices so I have spares if needed to support the two PCH locations she regularly uses.

I would love to get to v5 because that would be the end of Windoze in our house. Well, at least for host OSes.

[mvallevand]

knewc will exit on the context menu key if you have the context menu turned off. It's the equivalent of the Power key on the NMT remote.

If the issues are with the server, I suspect the NMT would suffer the same problems. The better solution is to send the logs next and I can see if I see anything.

Martin

[BrettB]

I use Kodi with knewc, but when I tried to "role it out" the frustration factor was still too high for her.  I have two ODroid N2's and one RPi4 that boot direct into knewc, but it's not perfect.  It closes on it's own and dumps back to Kodi a fair amount.  I suspect some of it is due to my dying NextPVR server PC, but right now the PCHs are more stable and a "known" for her.  She won't take the time to learn Kodi right now.  I had the idea the other night to program a remote button (maybe GREEN for "go") to launch knewc so she doesn't have to navigate to it if knewc closes.  Still might not be enough though.

It would probably be worth it for you to open a support thread in the kodi client forum with logs from some of the cases of "closes on it's own and dumps back to kodi a fair amount."

Also, do you have it set up so that there is a main menu item in kodi that goes right into knewc and the remote GUI?

[baj1]

Thanks Martin and Brett. I didn't want to waste anyone's time when I know my server has issues, but had planned to post logs if it continued to happen with the new server. The new server just got back-burnered for more urgent issues. I did some "offline" testing with one Kodi/knewc box with the new server (with no tuners set up, just a playback server) and didn't have the issue in a couple binge-watch sessions, so while a limited test at least the results were promising.

My old server with NextPVR will hang for 30 seconds on a regular basis, I've see it go almost 2 minutes without responding. This is using the GUI for playback on the server, which we've been doing since I set this one up back in 2011. It will happen after stopping playback (get a black screen for 30+ seconds), or when navigating the NextPVR GUI interface (we get the Win7 spinning circle cursor). My wife uses it more than I do, especially since my mother-in-law moved in as she has kind of taken over the family room. Anyway, I figure if the server goes out to lunch and doesn't respond, knewc might bail out. Further evidence, when knewc closes and drops back to Kodi, if I immediately re-run the knewc add-on it blinks the screen and returns right back to Kodi. If I let it sit for 30-60 seconds, it will usually run okay. Maybe this is of interest, but you guys work hard enough to support everyone else, I didn't want to pile-on when I know I have other issues which, to me, see likely to be the cause.

I did HDD and RAM tests on the old server and everything passed, for whatever that's worth. It has been at least 5 years since I wiped the OS and reinstalled (or restored from backup), and there has been a BSOD here and there recently, which never use to happen. NextPVR is all this box does, so it should be (and has been) much more stable than any other Windoze computer we've had.

A new issue I just recently noticed in copying files. I have a new "Recordings" HDD in my new Win10 server and have been mirroring with the old server Recordings drive before my attempts to switch from old-to-new. Twice during these file syncs I've had the network connection "die" (wired RJ45 port) on the old server. When it happens I can't ping the old server from the network, and if I hook up a keyboard to the old server and run ipconfig, it doesn't report any network connection either. A reboot corrects the problem.

My wife often uses the PCH in our bedroom to watch TV if she wakes and can't fall back to sleep (it seems to help put her to sleep) and she says she's had to get up in the wee hours and go to the family to reboot the server more frequently lately. So that could be the network connection crapping out or something else entirely.

So yep, I have old server problems. The case fans (3rd set?) are starting to make some noise again too. It really seems like it's time to retire this old box.

[mvallevand]

My point was the PCH should also drop out and have the same delay reconnecting. How is that different?

Martin

[baj1]

My point was the PCH should also drop out and have the same delay reconnecting.  How is that different?

Martin

The PCH may do the same thing, I've never tried to see if there's a correlation to any other device when it happens.  I'll have to ask the boss about that tomorrow to see it that's gotten worse lately, she uses the PCH more than I do.  I'll keep that in mind though when I'm using Kodi/knewc and see it happen, I'll check other clients and the server.  I'm often watching after everyone else has gone to bed, so it might be tough to catch it if it's not being used elsewhere.

The PCH's do lock-up from time to time.  That's nothing new, that's been happening for as long as I can remember.  I put the one in our bedroom on an old X10 appliance module w/remote I had laying around so if it locks up we can power-cycle the PCH without getting out of bed.  :-)