HDHomeRun Dual HDHR3-US can not be added

Server Version#: 1.20.3.3437
Player Version#: 4.44.2
Tuner Make/Model: HDHomeRun Dual HDHR3-US
Guide/Lineup name: Broadcast TV Omaha OTA
Using XMLTV?: no
Channel number/Name:

I can’t add an HDHomeRun HDHR3-US to Plex. I manually enter the IP address and Plex says it can not connect. It works with SD HDHomeRun software for Windows 10, Mac and the command line. Is this device still supported?

Logs: https://www.dropbox.com/s/qnxgmwyx16mq32c/Plex%20Media%20Server%20Logs_2020-10-15_22-17-20.zip?dl=0

Log snippet:
Plex Media Server.2.log:Oct 15, 2020 21:09:55.744 [0x7fdaea7ec700] DEBUG - Request: [192.168.1.38:63853 (Allowed Network (WAN))] POST /media/grabbers/tv.plex.grabbers.hdhomerun/devices?uri=192.168.1.33 (24 live) TLS GZIP Signed-in Token (double16)
Plex Media Server.2.log:Oct 15, 2020 21:09:55.746 [0x7fdaea7ec700] DEBUG - Grabber: Checking device URI http://192.168.1.33
Plex Media Server.2.log:Oct 15, 2020 21:09:55.748 [0x7fdaea7ec700] DEBUG - HTTP requesting GET http://192.168.1.33/discover.json
Plex Media Server.2.log:Oct 15, 2020 21:09:55.751 [0x7fdaea7ec700] DEBUG - HTTP 200 response from GET http://192.168.1.33/discover.json
Plex Media Server.2.log:Oct 15, 2020 21:09:55.760 [0x7fdb2d41d700] DEBUG - Completed: [192.168.1.38:63853] 404 POST /media/grabbers/tv.plex.grabbers.hdhomerun/devices?uri=192.168.1.33 (24 live) TLS GZIP 16ms 458 bytes (pipelined: 11)
Plex Media Server.log:Oct 15, 2020 22:15:03.072 [0x7fdae3fdf700] DEBUG - Request: [192.168.1.10:51457 (Allowed Network (WAN))] POST /media/grabbers/tv.plex.grabbers.hdhomerun/devices?uri=192.168.1.33 (11 live) TLS GZIP Signed-in Token (double16)
Plex Media Server.log:Oct 15, 2020 22:15:03.073 [0x7fdae3fdf700] DEBUG - Grabber: Checking device URI http://192.168.1.33
Plex Media Server.log:Oct 15, 2020 22:15:03.073 [0x7fdae3fdf700] DEBUG - HTTP requesting GET http://192.168.1.33/discover.json
Plex Media Server.log:Oct 15, 2020 22:15:03.081 [0x7fdae3fdf700] DEBUG - HTTP 200 response from GET http://192.168.1.33/discover.json
Plex Media Server.log:Oct 15, 2020 22:15:03.081 [0x7fdb2d41d700] DEBUG - Completed: [192.168.1.10:51457] 404 POST /media/grabbers/tv.plex.grabbers.hdhomerun/devices?uri=192.168.1.33 (11 live) TLS GZIP 74ms 458 bytes (pipelined: 18)

I’ve had the same issue for more than a year. I don’t think they will ever fix this.

My original post:

Just saw this post in my email from the last response. I pulled my old HDHR3-US out of a drawer and hooked it up to see if I encountered any issue connecting the device to a Plex Server. Unfortunately, I did not have any problems once I updated the firmware on the device.

2020-12-19_16-00-25

This PMS is on one of my Shield devices and is currently running the 1.20.5.3551 version of Plex Media Server.

From looking at your logs I am guessing you are running this in a Docker. I know nothing about running PMS inside a Docker but found this line in your logs interesting.

Oct 15, 2020 22:15:03.072 [0x7fdae3fdf700] DEBUG - Request: [192.168.1.10:51457 (Allowed Network (WAN))] POST /media/grabbers/tv.plex.grabbers.hdhomerun/devices?uri=192.168.1.33 (11 live) TLS GZIP Signed-in Token (double16)

Seems like PMS believes the device is on the WAN and not a local LAN.

In my case, the log entries are simply:
HTTP requesting GET http://192.168.1.61/discover.json
HTTP 200 response from GET http://192.168.1.61/discover.json
Grabber: No tuner key exists for device, couldn't obtain device status.

Does anyone know what the error above actually means?

Even with a restart of the HDHR3, so nothing else could be using the tuner, I get the same error.

Out of curiosity @johnm_ColaSC, what firmware version do you have? Mine is 20200225

Here’s another question. Why isn’t there any information how to manually configure an HDHomeRun tuner for Plex DVR?

Those of us that are using containers to run the server are probably savvy enough to edit config files as needed. But to hack a solution to the problem together without Plex providing some guidance is going to be a frustrating ordeal.

Had to pull my HDHR3 back out. After the HDHomeRun Software finished updating the device it now has the same firmware version you are running.

As far as manually configuring, the HDHR devices in my experience have never needed any manual configuration, but I am not running inside a container. Plug it in and Plex finds the device on the network. When I plugged this one back in and went to the DVR Settings it was showing as a device available, just had to click on it. If you are running in a container that might change the device recognition. I have never used a container for running Plex so know nothing about it. How is the network configured? Is a separate network setup inside the container, if there is that could be a possible problem. I see that this thread is tagged with server-docker so maybe someone that is familiar with Docker and has DVR configured will comment.

It is a separate network which is why discovery doesn’t work. Entering the IP address directly should work though. It can reach out if I exec into the container and use curl.

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