Unable to setup/discover HDHR3-DT tuner

General Discussions
1

I’ve just decided to switch from MythTV to Plex using the same network connected HDHomerun HDHR3-DT.
When I DVR Setup the circle just spins on the “Looking for compatible devices…” screen. If I enter the IP address of the HDHR3-DT it says “There was a problem adding the device: 10.0.0.9”.

Looking at the debug log for plex I can see “ERROR - Grabber: No tuner key exists for device, couldn’t obtain device status”:

Feb 04, 2020 20:01:11.836 [0x7fb927fff700] DEBUG - HTTP 200 response from GET 10.0.0.9/discover.json
Feb 04, 2020 20:01:11.836 [0x7fb927fff700] ERROR - Grabber: No tuner key exists for device, couldn’t obtain device status.

The discover.json page of the HDHR3-DT displays:

{“FriendlyName”:“HDHomeRun DUAL”,“ModelNumber”:“HDHR3-DT”,“Legacy”:1,“FirmwareName”:“hdhomerun3_dvbt”,“FirmwareVersion”:“20170930”,“DeviceID”:“1110C3C2”,“DeviceAuth”:“PiAiHr1NdeRkQSZdGS6E0VNG”,“TunerCount”:2,“BaseURL”:“10.0.0.9:80”,“LineupURL”:“ipv4-api.hdhomerun.com/api/lineup?DeviceAuth=PiAiHr1NdeRkQSZdGS6E0VNG”}

(I’ve had to remove all http:// in the links as new users can’t post more than 2 links)

I’m running plex inside a container but can access 10.0.0.9 using curl inside the container successfully (using host networking).

I’ve updated to the latest HDHomerun firmware available (as far as I know) and I’m running the latest version of plex server ( 1.18.5.2309).
Plex Media Server Logs_2020-02-04_20-01-25.zip (3.2 MB)

2

What is your Base OS?

My first suggestion would be to not run it in a container to see if it works.
Next suggestion would be to update to the latest beta so you can set “Preferred network interface” since you have multiple interfaces.
Last would be to make sure port 32600 is open on the host/network for the grabber to connect to the HDHR.

These old models have been having issues since version 1.14, I personally gave up and bought a new one.

3

I’ve just tested running outside of a container on the same sever and it has the same issue. The tuner is on the same network as the server and the server has iptables default accept for input table, so nothing blocking any ports.
I’m hoping I don’t have to buy a new tuner as the one I have already works (just not with plex).
I’ve installed the latest plex via downloading and installing the deb file (1.18.6.2368) and set the network interface to my local LAN one (eth0) but still won’t discover/connect to the HDHR3.
I’m not sure what you mean by “Last would be to make sure port 32600 is open on the host/network for the grabber to connect to the HDHR.” I can see the server listening on this port but only on localhost so it’s not accessible from other machines on the network.

4

As another test, I’ve installed plex media server on an imac on the network and that discovers the HDHR3-DT straight away. So it appears it’s an issue with plex running on my debian server.

5

I have Debian 10.2, plugged in my HDHR2 and it showed up right away in the ‘Plex Tuner Service.log’ and I could add it under the Live TV & DVR.

Looked at your logs again and the /usr/lib/plexmediaserver/Plex Tuner Service isn’t picking up the tuner when you try to add it which goes back to a probably port access issue.

What happens if you open a shell session and run a curl against the ip of the HDHR?

6

Here’s the output from running curl to the hdhr from the plex server:

server:plexmediaserver fherbert $ curl http://10.0.0.9/discover.json
{“FriendlyName”:“HDHomeRun DUAL”,“ModelNumber”:“HDHR3-DT”,“Legacy”:1,“FirmwareName”:“hdhomerun3_dvbt”,“FirmwareVersion”:“20170930”,“DeviceID”:“1110C3C2”,“DeviceAuth”:“r8tkRzTEZBNXvYuyvofXf9mV”,“TunerCount”:2,“BaseURL”:“http://10.0.0.9:80”,“LineupURL”:“http://ipv4-api.hdhomerun.com/api/lineup?DeviceAuth=r8tkRzTEZBNXvYuyvofXf9mV”}

So the plex server can access the tuner via port 80, does the discovery use another port?

7

Port 32600

8

The tuner isn’t listening on port 32600:

server:plexmediaserver fherbert $ curl http://10.0.0.9:32600
curl: (7) Failed to connect to 10.0.0.9 port 32600: Connection refused

Only the plex tuner server is listening on localhost on 32600. But another plex media server running on a different machine discovers the tuner straight away so I’m guessing the issue is with the server rather than the tuner.

I’ve compared tcpdumps between the 2 machines running plex and there is some UDP traffic from the tuner to the plex server that I don’t see on the non-working plex server. It looks like responses from the tuner to SSDP queries.

9

I’ve downloaded and compiled the hdhomerun_config tools from silicon dust (Linux - SiliconDust) and using hdhomerun_config from the plex server it discovers the tuner:

server:plexmediaserver fherbert $ hdhomerun_config discover
hdhomerun device 1110C3C2 found at 10.0.0.9

Anyone have any more ideas on how I can debug this further?

I know the tuner works with plex as it gets discovered fine on the osx version of plex server on the same network, from the Plex Tuner Service log on the working server:

Feb 06, 2020 08:14:45.011 [0x70000d10a000] INFO - [I] device_manager_t::get_device_list. Device HDHomeRun 1110C3C2 (10.0.0.9) - 0, id dvb#hdhr#0#286311362, tuners 1, state 0, standards 1
Feb 06, 2020 08:14:45.011 [0x70000d10a000] INFO - [I] device_manager_t::get_device_list. Device HDHomeRun 1110C3C2 (10.0.0.9) - 1, id dvb#hdhr#1#286311362, tuners 1, state 0, standards 1

10

I managed to figure out my issue. My networking config wasn’t quite correct on the debian server. My subnet mask is 255.255.0.0 (/16), but I had 255.255.255.0 (/24) configured on my debian server. I’ve fixed this now and the device discovery works.

11

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