Channels Can't Find my HDHomerun Devices

[freway01]

I did a firmware (QTS 5.1.0.2444) update on my QNAP NAS yesterday, and after doing it, I checked for updates to Channels. I installed Version 2023.07.06.1740. After I did that, I noticed the local guide information was missing data, so I tried stopping the Channels DVR Server (1.1.0), then restarting it, but after doing that, both of the two HDHomeRun devices I have on my home network, weren't listed as a sources. I checked Plex and it wasn't able to connect to the shared HDHomeRun devices either.

Tried adding one of the HDHomeRun devices it using the devices internal IP address and it says there were no channels detected on this HDHomeRun. Clicked on the 'scan for channels', which opened the HDHomeRun FLEX channel lineup, and clicked on 'Detect Channels' and it scanned the channels, but when it was completed, I went back to Channels, and clicked on 'click here' to continue. Still no channels showing up.

Running the HDHomeRun app on my Fire TV cubes & 4K sticks. Channels sees all of my TVE channels but even when I manually try to attach the device, no channels. I am able to run the HD (HDHomeRun) app on Fire TV, I can watch local TV. Both HDHomeRun are running firmware version 20230713.

[Morris_Altman]

Have you tried removing the HDHomeRun from channels and then adding it again?

[freway01]

I did. I think there is a home theater setting in QNAP that might have got changed, but I need to find out where it is

[freway01]

FYI, I did open a ticket with QNAP and provided them with all of the info they requested. Apparently they've made a few changes to networking and multimedia in this version so if you are running Channels DVR on a QNAP NAS, would you let me know if you have any problems after updating the firmware to QTS 5.1.0.2444.

For me, because Channels DVR isn't seeing the two HDHomeRun tuners, I tried the adding a source option and selected the HDHomeRun Device option which asks for the IP address of the device. After entering it and scanning for channels, it can't find any. If I click on 'scan for channels', it opens the HDHomeRun window that shows info for the tuner and lists all the channels. I tried using the scan on that screen but when I go back to Channels DVR settings, it still shows no channels detected.

I did notice that since adding the device via the IP address, when I go into the 'Settings' section of the client Channels app running on Windows or on one of my Fire TV cubes/sticks, if I go to 'Manage Sources', the IP address for the tuners I manually added in the Channels DVR settings show up. When I first select one of the tuners, it shows 'Found 0 channels'. If to select 'Scan for Channels' it will search the device, and when complete, it will tell you how many channels it found and will list them at the bottom of the page. If you go back to the guide, the channels you selected will be listed and guide info will show up. Unfortunately, once you leave the client app, the next time you go in, you have to scan the tuner again.

Like I've said, I'm not a QNAP expert, nor a networking expert but I can see that there is something that is preventing the NAS and the services running on it, like Channels, from seeing any broadcasting information the HDHomeRun devices are broadcasting.

Anyone have any suggestions?

[chDVRuser]

Have you tried Reload Lineup from the Channels DVR web UI?

There's also a confirmed bug in the web UI guide display (hasn't been fixed yet).

Guide Data Missing on 1 Tunner

I have 2 HDHomeRun OTA tuners, a Quatro and a Duo. Both tuners use the same guide source. When I view the Guide in a web browser and filter it to a single source, the Quatro is missing most of the channels. Only the Duo shows the correct guide data. The attached images show what I am seeing. These are the steps I have taken to try and fix the problem. Under Quatro Source Reloaded Lineup Redownload Guide Sync Station Mapping Under Guide Database Re-Download Entire Guide Delete and Recrea…

[freway01]

I've tried everything. It is defiantly something on the QNAP side. In addition to Channels DVR and Plex Media Server not seeing either of the HDHomeRun tuners, the QVR Pro surveillance app (QNAP app) that I use to record 2 weeks of video from my network attached security cameras (Reolink), can't see/find the cameras that the QVR Pro has been recording from for almost 2 years. When I run the Reolink app on my PC or smartphone, I can see the video from the cameras.

This what I see in Channels DVR settings:

[chDVRuser]

Definitely sounds like some kind of network communication issue.
Strange to see your HDHR's reported as just the device id in parenthesis without the Model Name.

Is it possible to install Channels DVR in a docker container on the QNAP to see if it behaves differently?

I think Channels DVR uses something similar to this to get the channel lineup. If you can get to an SSH command line and have curl on the QNAP, see if this returns the lineup.json for one of them.
curl -v http://192.168.1.135/lineup.json?show=all
curl -v http://192.168.1.225/lineup.json?show=all

I would try pinging them from the QNAP first
ping 192.168.1.135
ping 192.168.1.225

Also check what discover.json returns. Here's my HDHR Prime as an example

curl -v http://192.168.1.7/discover.json
*   Trying 192.168.1.7:80...
* Connected to 192.168.1.7 (192.168.1.7) port 80 (#0)
> GET /discover.json HTTP/1.1
> Host: 192.168.1.7
> User-Agent: curl/8.0.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: HDHomeRun/1.0
< Connection: close
< Content-Type: application/json; charset="utf-8"
< Content-Length: 331
< Cache-Control: no-cache
< Access-Control-Allow-Origin: *
< Date: Sat, 22 Jul 2023 22:29:13 GMT
<
{"FriendlyName":"HDHomeRun PRIME","ModelNumber":"HDHR3-CC","FirmwareName":"hdhomerun3_cablecard","FirmwareVersion":"20221205","DeviceID":"<REDACTED>","DeviceAuth":"<REDACTED>","UpgradeAvailable":"20230713","BaseURL":"http://192.168.1.7","LineupURL":"http://192.168.1.7/lineup.json","TunerCount":3,"ConditionalAccess":1}* Closing connection 0

[chDVRuser]

I assumed you looked at the Channels DVR log for errors, but since you haven't mentioned it, did you?

[freway01]

I did and sent a copy of the log to support to see if they have any suggestions. I have pages of these messages:

[chDVRuser]

Yep, networking messed up.
connect: no route to host

Sounds like you just need to figure out how to configure it.
(Network & Virtual Switch | Flexibly allocate network resources on NAS | QNAP (US))
Network & Virtual Switch | QTS 5.1.x

[freway01]

Sorry, I'm not a QNAP or network expert, but I went through the two documents and checked/compared them to my settings. I didn't see anything that jumped out at me so do you have any suggestions?

I'm waiting on QNAP support to get back to me on the ticket I opened with them. Like I said, in additions to Channels and Plex no longer seeing the tuners, the QNAP QVR Pro surveillance app can no longer see the security cameras it used to be able to see.

[tmm1]

How many Ethernet cables are attached to the NAS?

What's on the other side of the cable?

[freway01]

I have two (2) internet cables running from a Netgear Gigabit network switch, that connects back to a port on the Orbi router. This is the same setup that was working prior to doing the NAS firmware upgrade. The NAS no longer can see the the two HDHomeRun tuners, and the 5 network attached security cameras that fed the QVR Pro surveillance system running on the NAS.

I used the Putty app on my Windows PC to connect to the NAS and ran a ping to 8.8.8.8 and got responses, but when I tried any of the addresses for the tuners or cameras, nothing.

[tmm1]

Try with only one cable

[freway01]

Why would that make a difference? This setup has been working right up until I upgraded the firmware on the NAS. I'm not near the NAS at this time, but when I am, I'll try disconnecting on of the cables.

[Edwin_Perez]

By any Chance are you running Docker ? and did you use net host

[johnluber]

I don't have a QNAP device and have never owned one. But, looking at your screenshot it appears as though your Virtual Switch 1 and Adapter 2 have duplicate IP addresses. In addition to having the same IP addresses there are also yellow alert symbols on those two devices indicating an issue.

Duplicate IP addresses will cause all sorts of networking issues. It's my guess that if you correct the duplicate addresses then you will likely regain access to the devices that you can't access now.

[slampman]

I've never worked with one either but I've worked in IT for 20 years and have some comments/suggestions

Disconnect 1 NIC. you don't need redundant NIC's connected to the same physical switch. The only thing you are protecting yourself from is the physical port going down on your NAS.

Never upgrade something just for the fun of it,, only to solve a problem. If it ain't broke....

Realize that upgrades sometimes bring architecture changes. Things that used to work sometimes quit when you upgrade. So the argument of its always worked before doenst hold water. Doesn't matter what worked before, you changed a variable.

Have you contacted QNAP support? This doesn't sound like a channels issue.

[freway01]

Thanks for everyone's suggestions and help but, after working with QNAP support, they had me disable port trunking and disable the Service Binding. Once I did that and rebooted the NAS (to get a clean boot), the NAS was able to see all of the devices on my network.

Tech thinks that when the new firmware was installed, it was having a problem with setting up the virtual adapter with port trunking and service binding enabled (recommendation in the past by QNAP, and was working prior to the new firmware).