HD Homerun Connect not recognized by PLEX DVR setup

I have a new HDHR-4-2US HD Homerun Connect with up-to-date firmware (20170707beta2) that is not detected by the DVR setup in PLEX (Version 1.5.3.3580) running on a QNAP NAS. I’ve confirmed that the HR is on the same subnet; it is seen and functions when accessed by WIN10 machine on the same network. Auto DVR setup in PLEX cycles continuously; trying to manually add the HR using the i.p address results in “There was a problem adding the device: 192.168.1.146”.

I saw one other comment on possible problems with cloud sync - so I removed that from PLEX - no change.

Suggestions?

Update your Plex Media Server. 1.5.3 is quite old and has no support for HDHomeRun Connect.

Use the latest PlexPass build, which is 1.8.0.

Thanks, yes, I updated to 1.8.0.4109, still not detecting.

Other thoughts? Other ways to get HD Homerun recognized?

My HDHomerun Prime does not auto-detect. But if I manually enter the IP address of the HDHomerun Prime, then it recognizes it and fully supports it.

@rltarleton said:
Other thoughts? Other ways to get HD Homerun recognized?

What does hdhomerun_config --discover output?

When run from WIN10 computer on the same network: “hdhomerun device 104ACE5E found at 192.168.1.146” - as expected.
Running hdhomerun_config on the QNAP might be beyond my capabilities without some hand-holding

After the “Looking for compatible devices” … fails.

Then you click on “Don’t see your device ? Enter its network address manually”

Finally enter “192.168.1.146” as the Device Address, and click the “Connect” button.

What happens ? Does it still fail to find the device ?

Yes, fails. Stated this in the original post - "trying to manually add the HR using the i.p address results in “There was a problem adding the device: 192.168.1.146”.

Any chance that a firewall could be blocking the port ?

Not sure if it will help but found this on SiliconDust website:

1 Like

I have a similar problem where the HDHomerun is not discovered when I manually enter its IP address. It is not on the same subnet as Plex and there is a pfSense firewall in between. Plex is at 192.168.5.5 and the Homerun is at 192.168.4.98. After looking at the logs I can see that Plex is sending UDP broadcasts to 192.168.5.255:65001 and trying to contact 192.168.4.98:80. I’ve opened all of those ports but discovery still not working. UDP is a routable protocol; it seems like there is some arbitrary Plex software limit that Homerun needs to be on the same subnet? Feature enhancement? Suggestions welcome…

Nevermind, I figured it out. Entering the Homerun IP in the Plex DVR setup screen and clicking connect doesn’t work, but simply ignoring that and clicking continue finds the device once the ports are open. Just a confusing Plex UI. Hopefully this helps someone else in the future who also doesn’t accept that the devices need to be on the same subnet… :wink:

I was having a very similar issue after the recent upgrade to the latest version, my steps to resolve include. 1 - Downloading the channel fixer,Channel Fixer, and pointing it to the location of the db it populates 2 -Then using the button at the bottom I was able to remove all Tuner dvr data. 3 - Closing PMS from the task bar, i relaunched PMS and was greeted to a popup stating it has found an HDhomerun device and, would i like to setup DVR? You seemed to have it cleared up by the clean reinstall, but wanted to leave my fix for others.