Original HDHomerun HDHR-US

Channels DVR Server
#1

My understanding is that Channels still supports this ancient tuner. I have one and it'll scan channels with the hdhomerun_setup and can tune channels with the HDHomerun Config GUI and display them via VLC on a Windows PC. The NVIDIA Shield's HDHomerun app brings up a guide and I can tune the channels.

Channels DVR finds the source but shows 0 channels. It says to use the Channels app to update to the latest firmware which I've done (it's on 20230505 which is the latest for the hdhr-us). The Channels Client on the Nvidia Shield will see the channels on the source but trying to tune them will give a not found message. The server source never shows any channel available.

Is this device really supported? Is there a secret to getting the server to see channels.

#2

Google's AI is telling me that the Channels DVR server stopped supporting this tuner around 6/2/2024 so maybe that's it.

1 Like
#3

What device are you using for a server? Channels DVR no longer supports the NVIDIA Shield as a server. I think the Shield can still run the Android client.

1 Like
#4

Runs it fairly well here. Still the best Android streamer out there, although that isn't saying too much. The upcoming Vega OS Amazon products look to be even worse than the current generation of 1-2gb devices.

#5

I'm using a Debian server with Channels DVR as a Docker container; my client is an Nvidia Shield. I have no issues using other HDHomerun tuners except one which won't scan channel 14 and a power adapter issue on a newer 4-tuner model but the server itself has no issues with them. It's only on this original HD-HR that it's an issue.

#6

The channel scan needs to happen from Channels on iOS/tvOS, or from the HDHR player app.

This old model doesn't have an on-board channel scan storage, so it has to be synced with SD servers.

2 Likes
#7

Can you dumb this down just a bit more. I don't have an iOS/tvOS server -- nothing Apple. What do you mean synced with SD servers? I'm using a docker server setup in network host mode on a Debian server. I have a Windows 11 device using the HDHomerun setup software to do the scanning. I actually have it working at the moment but am not entirely sure how.

It may have been a conflict with how other software that I have installed but wasn't really using such as Emby/Jellyfin/Plex. Somehow the Channels server finally got the Channels list which enabled things to work. It's funny that the channels list that it got was from a scan last night when there was more available than today's scan.

#8

The Setup software on windows is the correct way. Maybe after running the scan you need to quit and restart the Channels app.

#9

Restarting channels dvr does not update the channels on the tuner source. The client sees the proper channel layout on it's sources but the server does not. Rebooting the HDHomerun doesn't do it either -- no big surprise if the channels aren't stored on it. The Windows HDHomerun Setup program sees the proper number of channels.

I really don't understand how the Channels DVR server gets the channel layout from either the Windows server, the tuner, or the client. I'm pretty sure that on newer tuners that it gets it directly from the device but what does it do on this old one that doesn't have the channel list stored on it?

I tried the Reload lineup on the server source but it doesn't do anything.

#10

The channel scan is stored on SiliconDust servers. Their software uploads it there. Maybe something changed because it has been years since we tried this.

#11

Assuming that's true then the Channels DVR would have to query that. If my experience from last night is any indication, it may only do that once a day. It would be helpful to know a way of initiating it on demand. The client on the Nvidia shield has no problem getting that data but the server behaves completely differently.

#12

Reload Lineup on the server is supposed to refresh it.

You could check Support > Log if there are any errors. Maybe something like "[ERR] Failed to load HDHR ..."

Or submit diagnostics under Support > Troubleshooting

#13

Nothing like that in the logs. The logs don't appear to show anything after doing a reload on that tuner. The only errors in the log are related to remote access because I haven't setup the server for remote access so have this:

2025/10/24 02:07:48.686173 [TRS] Remote Access: ERROR: Could not connect to 6772563636ca.u.channelsdvr.net. Check if the port is mapped.

#14

I can confirm that the HDHomerun application talks to Silicondust at 217.149.102.110 via TLSv1.2 when you do a scan so that's probably when it saves the channel lineup. The server source reload command doesn't seem to be working properly but the client does grab the channels when you refresh the source and it apparently gets the lineup from Silicondust. The client does have an import and export function which is presumably to/from the Channels DVR server but the export doesn't seem to reliably update the server.

#15

It looks like no update with respect to channels happens on the Channels DVR server with respect to the HDHR source because the reload lineup function is not actually working. So even if I delete and disable the source and reboot the server, as soon as I add the source back via manual IP then the channels originally associated come back with it. I even tried using the curl function: curl -XDELETE http://127.0.0.1:8089/devices?ip=192.168.1.187 command but that basically only deletes the source like the "remove provider" option does. As soon as you add it back, you have the same channel listing. I could live with that but the problem is that the client will query from the server and retrieve that channel listing which in effect corrupts the guide. I can quickly fix it by using refresh source button on the client which presumably does what the reload lineup SHOULD do on the server but it's only a temporary fix since the client app will eventually query the server and get a new bad channel listing.

#16

^^

1 Like
#17

This was done under 247a82ed-11ad-494e-9b56-54efd59e3c25.

1 Like
#18

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.