Unable to add HDHomerun on local VLAN after previously working

Live TV & DVR
1

Server Version#: 1.19.4.2902
Player Version#:
Tuner Make/Model: HDHomeRun Connect Quatro HDVR-4US-1TB
Guide/Lineup name:
Using XMLTV?:
Channel number/Name:

Issue:
I had the liveTV setup and working for more than 4 months. I tried to record an OTA show recently and it said the server was unavailable so I tried to go to the liveTV on the android app as well as the full web version and the LiveTV does not show up as a viewing option. When I go to check the status of the tuner from Plex it has the setup as if it isn’t setup anymore. When I try to add the tuner it does not find it and when I try to add it manually it does nothing. Looking at the logs it shows this:

device://tv.plex.grabbers.hdhomerun/152045DE at http://192.168.1.69:80
Jun 09, 2020 08:20:21.978 [2052] Debug — HTTP requesting GET http://192.168.1.69:80/discover.json
Jun 09, 2020 08:20:21.984 [2052] Debug — HTTP 200 response from GET http://192.168.1.69:80/discover.json
Jun 09, 2020 08:20:21.984 [2052] Debug — HTTP requesting GET http://192.168.1.69:80/lineup_status.json
Jun 09, 2020 08:20:21.996 [2052] Debug — HTTP 200 response from GET http://192.168.1.69:80/lineup_status.json
Jun 09, 2020 08:20:33.509 [0424] Debug — Request: [192.168.1.105:64569 (Subnet)] POST /media/grabbers/tv.plex.grabbers.hdhomerun/devices?uri=192.168.1.69 (11 live) TLS GZIP Signed-in Token (#####)
Jun 09, 2020 08:20:33.509 [0424] Debug — Grabber: Checking device URI http://192.168.1.69
Jun 09, 2020 08:20:33.509 [0424] Debug — HTTP requesting GET http://192.168.1.69/discover.json
Jun 09, 2020 08:20:33.514 [0424] Debug — HTTP 200 response from GET http://192.168.1.69/discover.json
Jun 09, 2020 08:20:33.514 [0424] Debug — HTTP requesting GET http://192.168.1.69/lineup_status.json
Jun 09, 2020 08:20:33.526 [0424] Debug — HTTP 200 response from GET http://192.168.1.69/lineup_status.json
Jun 09, 2020 08:20:33.557 [0424] Debug — Grabber: tv.plex.grabbers.hdhomerun called the probe of http://192.168.1.69 a success.
Jun 09, 2020 08:20:33.557 [0424] Debug — HTTP requesting GET http://192.168.1.69/discover.json
Jun 09, 2020 08:20:33.564 [0424] Debug — HTTP 200 response from GET http://192.168.1.69/discover.json
Jun 09, 2020 08:20:33.564 [0424] Debug — HTTP requesting GET http://192.168.1.69/lineup_status.json
Jun 09, 2020 08:20:33.576 [0424] Debug — HTTP 200 response from GET http://192.168.1.69/lineup_status.json
Jun 09, 2020 08:20:33.604 [0424] Info — Grabber: The device was already discovered at http://192.168.1.69, updating URI
Jun 09, 2020 08:20:33.606 [4204] Debug — Completed: [192.168.1.105:64569] 200 POST /media/grabbers/tv.plex.grabbers.hdhomerun/devices?uri=192.168.1.69 (11 live) TLS GZIP 96ms 940 bytes (pipelined: 31)

I can supply more logs if needed. As you can see it says that it is already discovered but does not add tuner. Can confirm it is not recording from Plex and I can get to the tuner via http.

2

I just had an issue where Plex wouldn’t tune to any channels. I went in and checked on the HDHR status page (like the one for the HDHR, not in Plex) and it appeared that it had auto-updated and was waiting from me to click a Reboot button at the bottom of the page. After I did that, everything was working again.

Just something to try.

3

That’s not exactly what I am experiencing. My server looks as though it isn’t setup for DVR (which it has been for sometime until an update) but when trying to setup the DVR it will not find the tuner or even find it when I manually put in the IP address. I rebooted the tuner, the server, and the switch in the middle but still no luck. I can ping the tuner from the server and its on the same VLAN.

4

Darn, that was my only idea. Sorry I couldn’t help.

I would, try to add the tuner again and then download the logs and post them here. Hopefully that will tell us why Plex can’t / won’t connect

5

In addition to logs (full logs zip) it would be useful to also include what you get back from the DVR at the time of the issue by sending these requests in a browser and copying the responses out

Look for all the HTTP requesting GET [http://192.168.1.69 log lines and fire off these requests in a browser

eg

http://192.168.1.69:80/discover.json
http://192.168.1.69:80/lineup_status.json

as two examples from your log extracts - there may be one or two more

6

Its making it to the tuner but not recognizing it at all. I did a packet capture on the meraki switch and a wireshark packet capture from the server and everything indicates it is working but nothing on the server is saying it recognizes the tuner. I am tempted to spin up a new plex server with the current software and see if i get the same results.

7

We do have a change that will be in a forthcoming version of Plex Media Server that has better handling where there are no SSDP packets or on different subnet

Logs captured after restart of Plex Media Server and allowing it to run for 5-10 minutes would indicate if it is a similar issue

Anyway, if you need help, please provide the full logs and responses for the specific requests i outlined

Thanks

8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.