My “Plex Tuner Service.log” shows the same as @RonRN18. I believe the jail running PMS defaults to a running on the same network as FreeNAS and the HDHRs. Unless I’m missing something (which may totally be the case). Here is the output of ifconfig from within the jail:
To test if the jail could discover, I installed hdhomerun_config and ran the discover command: root@plexmediaserver_1:/ # hdhomerun_config discover hdhomerun device 1031A5CB found at 192.168.2.138 hdhomerun device 10389775 found at 192.168.2.127
What does PMS use to discover the HDHRs? Should something like mDNSResponder be installed along side of PMS in an installation like this.
Like @sudorouss , I installed hdhomerun_config and when I ran it I got: root@plexmediaserver_2:/$ hdhomerun_config discover hdhomerun device 103584B6 found at 172.18.1.30 hdhomerun device 104054B7 found at 172.18.1.31 hdhomerun device 10527CA4 found at 172.18.1.32 hdhomerun device 105317A0 found at 172.18.1.33
This was expected. The first is my DUAL, the second is CONNECT and the last two are EXTENDs.
Here is my ifconfig: root@plexmediaserver_2:/$ ifconfig lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> epair8b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=8<VLAN_MTU> ether fe:92:79:d4:33:3a inet 172.18.11.110 netmask 0xfffff000 broadcast 172.18.15.255 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>) status: active
Just a note, a netmask of 0xfffff000 is the same things as 255.255.240.0
Just a further note, my PMS’s IP address, as you can see from my last post, is 172.18.11.110. For a whim, I set my DUAL to have an address of 172.18.11.30 instead of 172.18.1.30; it made no difference. hdhomerun_config discover still recognizes it but PMS still can’t see it.
In case anyone is curious, I set up my router to use the strange network design to group similar devices by the third octet. For example, servers have a third octet of “0” (172.18.0.x), headless appliances (i.e. sprinkler controller, surveillance camera system, HD HomeRuns, ADSB receiver etc…) have a third octet of “1”. I have wired desktops/laptops with a “3” and wireless laptops often share the 4th octet of their wired number but have a 3rd octet of “4.” The third octet of “11” is for virtual machines or jails on my FreeNAS server, which is why my PMS has a third octet of “11.” I know it may be confusing to some, but it works for me.
Add me to the list of folks not getting old DUALs to work on FreeBSD based PMS –
I have an old dual. I hooked it up with a digital antenna, updated the firmware (20161117), configured it via a windows PC and have 75 channels found.
Here is the output of the discover.json from my HDHR:
{“FriendlyName”:“HDHomeRun DUAL”,“ModelNumber”:“HDHR-US”,“Legacy”:1,“FirmwareName”:“hdhomerun_atsc”,“FirmwareVersion”:“20161117”,“DeviceID”:“1016E13F”,“DeviceAuth”:“R5scYM9HQsYs1w/oFlCdgNKY”,“TunerCount”:2,“BaseURL”:“http://192.168.1.39:80”,“LineupURL”:“http://my.hdhomerun.com/api/lineup?DeviceAuth=R5scYM9HQsYs1w%2FoFlCdgNKY”}
Running PMS 1.5.0 on FreeBSD (not in a jail). My PMS server is at 192.1.68.1.3, same subnet.
I can view channels using the HDHomeRun app on my mac and windows PC.
@adamchri your issue of the INI file is fixed in PMS 1.5.1
@RonRN18 There is one outstanding known issue that I am investigating, and that is the detection of the older HDHomeRun tuners on FreeBSD platforms. We are working on testing a potential fix, which if successful, should be included in the next Plex Pass release of PMS.
@adamchri said:
It finds my old HDHomeRun DUAL tuner - great, but I have no providers for Cable included. If I select Antenna I get a list of providers, but when I select Cable (and any country it seems) I just get an odd reference to an ini file.
When I try to add a DVR it sits there forever and never finds anything. When I manually enter the IP address I get “There was a problem adding the device”. The logs show:
Jun 07, 2017 12:22:19.530 [0x7fe2223ff700] DEBUG - DVR:Grabber: Checking device URI http://172.24.0.201
Jun 07, 2017 12:22:19.530 [0x7fe2223ff700] DEBUG - HTTP requesting GET http://172.24.0.201/discover.json
Jun 07, 2017 12:22:19.533 [0x7fe2223ff700] DEBUG - HTTP 200 response from GET http://172.24.0.201/discover.json
Jun 07, 2017 12:22:19.534 [0x7fe2223ff700] DEBUG - HTTP requesting GET http://172.24.0.201/capability
Jun 07, 2017 12:22:19.537 [0x7fe2223ff700] DEBUG - HTTP 404 response from GET http://172.24.0.201/capability
Jun 07, 2017 12:22:19.537 [0x7fe2223ff700] DEBUG - HTTP requesting GET http://127.0.0.1:32600/devices/
Jun 07, 2017 12:22:19.539 [0x7fe2223ff700] DEBUG - HTTP 404 response from GET http://127.0.0.1:32600/devices/
Jun 07, 2017 12:22:19.539 [0x7fe2223ff700] ERROR - Error parsing content.
Jun 07, 2017 12:22:19.539 [0x7fe2223ff700] ERROR - Error parsing XML.
Jun 07, 2017 12:22:19.539 [0x7fe2223ff700] ERROR - DVR:Grabber: Error obtaining device status.
I can watch the HDHR with other software including VLC without issue.
Plex version 1.7.2.3878, running in a Docker container (but with --net=host)
