DVR Setup: There was a problem adding the device

General Discussions Plex Features
1

When I try to add a DVR (HDHomeRun) on the Network, it just hangs trying to find it, but if I manually specify the IP address I get the error:

There was a problem adding the device

Relevant part of the logs:

Jun 02, 2018 01:29:18.265 [0x7f39223fd700] DEBUG - DVR:Grabber: Checking device URI http://10.0.1.16
Jun 02, 2018 01:29:18.266 [0x7f39223fd700] DEBUG - HTTP requesting GET http://10.0.1.16/discover.json
Jun 02, 2018 01:29:18.271 [0x7f39223fd700] DEBUG - HTTP 200 response from GET http://10.0.1.16/discover.json
Jun 02, 2018 01:29:18.272 [0x7f39223fd700] DEBUG - HTTP requesting GET http://10.0.1.16/capability
Jun 02, 2018 01:29:18.276 [0x7f39223fd700] DEBUG - HTTP 404 response from GET http://10.0.1.16/capability
Jun 02, 2018 01:29:18.277 [0x7f39223fd700] ERROR - DVR:Grabber: No tuner key exists for device, couldn't obtain device status.

It looks like the request to /discover.json is working just fine (and I can verify this in my browser), but whatever /capability it 404s on the HDHomeRun (also verified in my browser). Why is Plex making this request?

I’m using version 1.13.0.5023, which, at the time of this writing, Plex claims is the latest version.

(oops, this discussion is in the wrong category, but it wont let me move it or delete it)

2

I’m assuming this is some sort of issue with the ports being blocked by the firewall. But if that is the case, I have no idea what ports need to be opened up. :frowning:

3

So if I open up all of the ports on the Plex Server’s firewall, it works perfectly, so is there a way to figure out what port(s) I need to open up?

4

This appears to be an issue with the way Docker networking works (I think). I can’t get it to work on the bridge networking (firewall? IP address being different?).

But it works with the host networking. Not ideal, but it works. Is there any way to get the DVR to work with bridge networking?

5

I upgraded to the latest version and that solved my problem. Had the same issue with it not being able to find the capability url.