PMS can't find hdhomerun

Plex Media Server
1

PMS is running on a headless Ubuntu server (with all updates docker :latest). I can successfully 'curl $HDHR3_IP_ADDRESS. So i don’t believe its a firewall issue. Trying to manually add the device in the PMS DVR yields the error ‘There was a problem adding the device: $HDHR3_IP_ADDRESS’

i’ve rebooted both my HDHomeRun DUAL (Model HDHR3-US, Firmware: 20200225) and my PMS (Version 1.21.1.3842).

This tuner work a fews months ago. With the holidays I haven’t been using it much. I don’t know what PMS version it last worked on however.

My HDHomeRun CONNECT (Model: HDHR4-2US, Firmware: 20200907) seems to work fine.

Edit: I upgraded to PMS Version 1.21.1.3876 last night. Problem persists.

2

bump.

3

The Plex documentation shows support for SiliconDust HDHomeRun (all models)
Is this no longer true and the website is out of date?

4

suggest you ensure debug logging is enabled on the server. Update to the current version 1.21.1.3876-3c3adfcb4 and reproduce the problem after a fresh launch of Plex Media Server and then gather server logs and screenshot

see

The HD Homerun Dual is an old model and is managed by the Plex Tuner Service

5

Attached log excerpt and screen shot.

DVR error
DVR error791×552 26.6 KB
Plex Media Server [cut].log (7.7 KB)

6

Bump.

7

I need the full logs zip which would also include the Plex Tuner Service logs and need the startup sequence in the server log after the launch

Can you tell me what DVRs are on each of these IP addresses
192.168.43.100
192.168.43.101

Can you tell me if you have multiple local subnets ?
192.168.42.xx
192.168.43.xx

and can you save the response you get from these browser requests and include with the logs

http://192.168.43.101/discover.json
http://192.168.43.100/discover.json

and responses from these requests

http://192.168.43.101/lineup_status.json
http://192.168.43.100/lineup_status.json

Please copy each response to a text file and label them as 101 and 100

I can see an error relating to 192.168.43.101

Jan 12, 2021 12:56:40.958 [0x7fc7037fe700] ERROR - Grabber: No tuner key exists for device, couldn't obtain device status.

And when using the HD Homerun Setup app when DVRs are discovered and what are the displayed ID’s ?

Thanks

PS: I only work on Tuesdays on Plex so if you can get that info today, I will have a look - otherwise it will be next week

8

Yes I have multiple subnets. 43 is where PMS and the tuners live.
42 is treated as external clients.

192.168.43.100 - HDHomeRun CONNECT (Model: HDHR4-2US, Firmware: 20200907)
discover.json

FriendlyName	"HDHomeRun CONNECT"
ModelNumber	"HDHR4-2US"
FirmwareName	"hdhomerun4_atsc"
FirmwareVersion	"20200907"
DeviceID	"10483526"
DeviceAuth	"REDACTED"
BaseURL	"http://192.168.43.100:80"
LineupURL	"http://192.168.43.100:80/lineup.json"
TunerCount	2

lineup_status.json

ScanInProgress	0
ScanPossible	1
Source	"Antenna"
SourceList	
0	"Antenna"
1	"Cable"

192.168.43.101 - HDHomeRun DUAL (Model HDHR3-US, Firmware: 20200225)
discover.json

FriendlyName	"HDHomeRun DUAL"
ModelNumber	"HDHR3-US"
Legacy	1
FirmwareName	"hdhomerun3_atsc"
FirmwareVersion	"20200225"
DeviceID	"103C4A17"
DeviceAuth	"REDACTED"
TunerCount	2
BaseURL	"http://192.168.43.101:80"
LineupURL	"REDACTED"

linup_status.json

404 Error
Page Not Found

.

9

Plex Tuner Service.log (21.4 KB)

10

I appreciate you looking into this. I’ll be a bit more patient knowing that you only work Tuesdays. :smiley:
I’d rather not post my entire log set for security reasons, but I sent a DM with the complete set.

11

Had a similar issue a few months back when I was experimenting with multiple tuners. I had to remove the existing DVRs/EPGs from the Plex Database.

The forums have examples of how to do this, some in the command line others using GUI software.

12

Tried that. Same issue.

13

Thanks

The Plex Tuner Server.log does not show successful discovery of the DVR on 192.168.43.101 with an error being returned when the device status is requested - i am guessing at the moment that dvb#hdhr#0'272386583 is actuall DVR with device if 103C4A17

Jan 12, 2021 12:58:25.333 [0x7f57c77fe700] INFO - [I] v4l::DeviceGetList_impl. getting v4l device list
Jan 12, 2021 12:58:25.338 [0x7f57c77fe700] INFO - [I] onetv_factory::DeviceGetListEx >>
Jan 12, 2021 12:58:25.338 [0x7f57c77fe700] WARN - [W] onetv_factory::DeviceGetListEx. libusb_init returned an error -99

Jan 12, 2021 12:58:25.339 [0x7f57cca00700] INFO - [I] web_service_t::process_device_status
Jan 12, 2021 12:58:25.758 [0x7f57cca00700] WARN - [E] web_service_t::get_device_status. get_device_info returned error for device dvb#hdhr#0#272386583

A previous report of similar issue was reported back as was being a firewall issue - see HDHomerun not found

Could you look into the firewall rules

Also try the LineupURL for that DVR - the one you redacted. Try it in a browser and see what you get back

14

As best i can tell there is no firewall blocking com between PMS and the HDHR. I’m using a docker container PMS and I’m fairly new to docker but IPTABLES on the host is not blocking this.

As for the line up: http://ipv4-api.hdhomerun.com/api/lineup?DeviceAuth={redacted]

	
0	
GuideNumber	"2.1"
GuideName	"WDTN HD"
URL	"hdhomerun://103C4A17/ch689000000-4"
1	
GuideNumber	"2.2"
GuideName	"ESCAPE"
URL	"hdhomerun://103C4A17/ch689000000-6"
[...]
39
GuideNumber	"64.4"
GuideName	"TBD"
URL	"hdhomerun://103C4A17/ch587000000-6"
15

I don’t use docker but another forum post for DVR discovery issue on docker had this post:

I’d moved Plex to use host networking so that the tuner discovery wasn’t an issue

Could you check if you are using the host networking method - if you are please send me by Private Message the docker config / setup file

16

I am using bridge networking.

I can’t switch to host networking, but I did temporally start PMS on a host directly (without docker). I confirmed that I am able to detect the DUAL. NOTE that I stopped the docker container for this test and both instances of PMS point to the same location in my NAS for configuration, database and content.

That implies the issue is with bridge networking and/or docker. but begs the question, why does the CONNECT work but not the DUAL?

Again, I don’t believe there are any firewalls blocking the traffic, but maybe the bridge set up, as i’ve only specified port 32400 for NAT. PMS-Docker
I.e. only ‘-p 32400:32400/tcp’

When setting up my container i referenced This article

I don’t believe I’m using any of the referenced ports so didn’t include them. (e.g. Bonjour/Avahi, G’Day, DLNA, or Plex Companion)

17

Interesting. May be it is to do with the lineup url having a domain name on the HDHomerun Dual - I will discuss with the our development team

18

I would be surprised if the domain name had anything to do with it. But hey i always enjoy the

:smiley:

19

Initial development team feedback:

  • do not use bridge networking

I will see if there is a way round it

20

haha That’s helpful… :stuck_out_tongue_winking_eye:

Obviously let me know if there is a way round it and I’d like to know what the root issue is, once they figure it out.