I have a new HDHR-4-2US HD Homerun Connect with up-to-date firmware (20170930) that is not detected by the DVR setup in PLEX (Version 1.10.1.4602) running on a QNAP NAS (TS-251+; QTS 4.3.4). 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 never finding the HDHR; trying to manually add the HR using the i.p address results in “There was a problem adding the device: 192.168.1.121”. Logs attached. Thanks.
I see you have 2 different interfaces on the same network subnet it appears:
119894 Feb 19, 2018 19:46:28.590 [0x7f42be64e800] DEBUG - * 5 br0 (192.168.1.12) (loopback: 0)
119895 Feb 19, 2018 19:46:28.590 [0x7f42be64e800] DEBUG - * 6 br1 (192.168.1.11) (loopback: 0)
Also seeing network errors in your logs:
120157 Feb 19, 2018 19:46:32.061 [0x7f42afd11700] WARN - HTTP error requesting GET http://192.168.1.1:8200/rootDesc.xml (0, No error) (Failed connect to 192.168.1.1:8200; No route to host)
120162 Feb 19, 2018 19:46:32.063 [0x7f42b1bff700] WARN - HTTP error requesting GET http://192.168.1.121:80/dms/device.xml (0, No error) (Failed connect to 192.168.1.121:80; No route to host)
120177 Feb 19, 2018 19:46:33.165 [0x7f42ae511700] WARN - HTTP error requesting GET http://192.168.1.113:8060/ (0, No error) (Failed connect to 192.168.1.113:8060; No route to host)
I know very little about QNAP but I would suggest unplugging one of the two local interfaces and see if you are able to connect to the HDHR with just one local interface. I believe that QNAP is providing you with more than 1 interface so you can aggregate the link to effectively double your upload/download to the network. Typically in all instances I have seen where link aggregation is used the network device the links connect to must also support the link aggregation. Interesting article found: http://www.itpro.co.uk/nas/29490/two-ports-no-waiting-the-pros-and-cons-of-link-aggregation.
I agree with John above. If you want to use two Network connections you have to use LACP on your router to combine the ports. This presents the network with a single IP and not two.
Otherwise, just use one network connection. Using two network connections with two different IP’s with Plex doesn’t work well.
Thanks for the suggestions. The 2nd port on the QNAP was not being used (not connected). My Nighthawk R7000 does not provide LACP capabilities but the QNAP allows one to trunk the 2 ports into one - which I did. But still did not fix the problem of PLEX not detecting the HDHR. I couldn’t locate which of the files in the logs where you were seeing the errors - so not sure if those are gone or not. Other thoughts?
The errors were in the Plex Media Server log file. Did you try unplugging one of the network connections?
@rltarleton even though the QNAP allows you to link aggregate, you do need to have the links aggregated at the other end, otherwise the Router does not know how to handle the traffic coming down the connections.
Just try using a single cable with the link aggregation turned off in the QNAP.
As noted, the second port is not/was not ever connected - only one port connected to the router. The second port is defined (with an i.p. address) on the QNAP. But no cable connection from the second port to the router to begin with - yet still the errors. I will see if I can delete the second port (or delete the address designation) and see if that makes a difference. Thanks.
I deleted the second port - and that did the trick. Thanks for sending me in the right direction.
@rltarleton QNAP use an internal virtual Router system to direct traffic internally within the application layer in the unit. So even if the second NIC wasn’t connected externally, by defining the IP address and setting up link aggregation internally, to the PLEX app there appears to be two Network interfaces, which as you have found, doesn’t work.
Glad you resolved the problem.
