Plex not working with HDHomeRun Dual?

Greetings!

I’ve been on here a bit reading about other peoples experiences with Silicon Dusts HDHomeRun and trying to get it into Plex. Thus far, the concensus seems to be that Legacy devices are troublesome.

I reached out to HDHomeRun themselves and according to them, the legacy devices should still work.

Server Version#: 1.22.2.4282
Tuner Make/Model: HDHR-US

I’m unable to get it to show up in the Live TV & DVR settings on clients or the media server itself. I have setup my network to manually assign the mac address associated to the Dual with a static IP, as I read that you cannot specify a static device within the device, you can only have DHCP do it for you.

Attempting to manually input the Duals IP doesn’t work either. Any ideas?

More info:
What OS and version?
How did you install Plex?
Is your network one segment and RFC1918 compliant?
Did you ensure that the firmware is latest for the Legacy Model (20200225)

Debug(Not Verbose) logs from the Webapp: Settings > Manage > Troubleshooting > Download Logs.

I’m running the media server on Centos 8, 8.3.2011.
I installed Plex via the CentOs 8 installer (I loaded UI on, it’s not pure command line).
Firmware on the Legacy Model is in fact 20200225.

Can you elaborate on my network being one segment? Does this mean that the HDHomeRun and the Plex Media Server should be on the same switch, or? What is RFC1918 compliant?

I’m not doing anything strange, only thing I could think of in the network that is causing issues is the fact that there’s about 5 switches on it in a top down configuration (there are a lot of devices).

Logs:
Plex Media Server Logs_2021-04-20_07-23-13.zip (6.7 MB)

Thanks!

On the same subnet.
With PMS being on 192.168.1.220 then the HD Homerun Dual needs to have an IP Address in range 192.168.1.xxx

Is SSDP enabled ? It is used for discovery

If the HD Homerun Dual is on a 192.168.1.xxx IP address, could you see if it is responding to

http://192.168.1.xxx:80/discover.json
(replace the xxx with the actual ip address octet)

Sorry about the account flips. I have the media server on an administrator one and forgot to flip off it… lol.

My Dual is running on 192.168.1.90, so it is on the same subnet. It is responding to discover.json.

Where would SSDP need to be enabled, on the router or somewhere else?

Temporarily stop the firewall sudo systemctl stop firewalld to see of Plex can then see the tuner. You have a double NAT situation going on with a router at 192.168.0.184 that is confusing Plex as to the proper gateway.

On the router - enabling uPnP should result in SSDP being enabled

I am not sure if there are any specifics with Centos and if SSDP needs to be enabled there

At the moment - the Plex Tuner Service logs do not show any HD Homerun discovered - there should be entries like this in the Plex Tuner Service.log files

Apr 20, 2021 14:09:31.495 [32968] INFO - [I] dvb_device_factory_t::get_device_list. Id dvb#hdhr#0#304162995, Name HDHomeRun 122128B3 (192.168.0.107) - 0, Standards 3
Apr 20, 2021 14:09:31.495 [32968] INFO - [I] dvb_device_factory_t::get_device_list. Id dvb#hdhr#1#304162995, Name HDHomeRun 122128B3 (192.168.0.107) - 1, Standards 3
Apr 20, 2021 14:09:31.504 [50920] INFO - [I] DeviceGetListEx_impl: Filter [Silicondust HDHomeRun Tuner 122128B3-0]

I don’t know if there are any specific requirenents on Centos to allow Plex Tuner Service to use the network

Stopping the firewall fixed the whole thing. Any ideas why that might be and how I can fix the double NAT in a more permanent way?

Furthermore, I am able to access to HDHomeRun Dual as of right now and it pulled in all the channels I can see in the HDHomeRun setup. The problem is it will not do playback. It consistently pulls up an error.

Any thoughts, or should I send log files again?

The stopping the firewall didn’t fix the Double NAT, that will take more work.
Centos has a firewall on by default. The Plex Tuner Service needs port 32600 open in addition to several others (What network ports do I need to allow through my firewall? | Plex Support)

Yes a new set of logs with a playback attempt would answer why it is failing. If you can manage, restart the server, attemp playback and wait a couple of minutes after it fails before you download the logs. Post the logs with what you attempted to playback and I’ll take a look.

Plex Media Server Logs_2021-04-20_13-22-18.zip (5.5 MB)

Here is the latest logs following those steps.

Plex can’t talk to itself over localhost, getting a 404 error.
First try sudo setsebool httpd_can_network_connect on -P and if that doesn’t work then sudo setenforce 0

If you didn’t already repeat sudo systemctl stop firewalld, to make that survive reboots do sudo systemctl disable firewalld

I repeated all that. Same issue. I took a look at the logs and noticed there was a timeout in trying to find duration? Seems this has been a reoccurring issue over the years.

Can you access the tuner using the HDHomerun software? For the Legacy tuners it helps to run the setup program and scan/save the channel list to the device.

Way ahead of you. I already scanned the channels and such on the HDHomerun software. I rescanned them and nothing changed.

Some progress has been made! I did some further digging on the forums, and found the Plex has no control for which tuner it pulls in from. I ended up splitting the antenna and plugging in both tuners to the same source (from said splitter). I am now getting Error code s4032 (Manifest).

Didn’t even think to ask if you had both connectors populated with an antenna.

s4032 is a browser error, browsers being the worst client for live/recorded tv will always cause the video to be transcoded.

Do you have a Windows machine or phone that you can load the Plex client on?

Got it resolved and all working now. (Just need to test recording later today).

One of the things I read is that s4032 requires VLC or some other things. I ran it on Chrome on Windows 10, and it worked just fine. Also worked perfectly on the Samsung TV’s, which is the main place Plex will be used anyway.

Thanks for all the help!

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