Server Version#: 1.19.2.2673
Player Version#: N/A
Tuner Make/Model: HDHR5-2US FW 20200225
Guide/Lineup name: Antenna
Today I received a brand new HDHR5-2US. When attempting to set it up it disappears from view when the channel line-up page shows up.
I’m able to see it auto-detected. I click continue. The channel lineup briefly shows then the screen drops back to not showing the device. Manually trying to add the device later doesn’t work. I have to restart plex before it will show up again.
Did you find a solution to this? I’ve been in the same predicament. After trying the many troubleshooting steps / methods others have had success with, I pulled out the sledge hammer and I tried recreating my Plex database – nothing has fixed it for me.
I can restart the Plex server, and the HDHomeRun briefly shows up. I try to add it, and it disappears again.
Nope service crashes every time and needs a restart to fix. What firmware version are you running?
If all devices are on a flat (no vlan) network then Plex should find them via the SSDP protocol.
Set your Server logs to Debug on, Verbose off.
Restart the Server, give it 3 minutes and then download from the troubleshooter and upload here.
I found my problem. After checking debug logs and finding a “died” message on discovery, I did some wiresharking. Ultimately, I traced it back to a security feature on my router. Specifically, Orbi’s integrated “Armor” functionality was leading to dropped packets. So discovery initially worked, but was then dropped on the mesh backplane. I disabled that, and things are working as expected.
I didn’t get a notification that you updated this thread so I apologize for late response.
Your database is confused over the state of DVR and has some leftover entries from before the EPG provider switch. Before resorting to a Database repair, try restarting and deleting the DVR. Wait a few minutes, restart and try adding the DVR back in. There are also so old scheduled recordings that may have to be removed.
Subscription: Failed to resolve subscription for episode 'grandparentGuid: com.gracenote.onconnect://show/16236892 grandparentThumb: https://tmsimg.plex.tv/tvbanners/generic/generic_tvbanners_v8.png grandparentTitle: Christmas Devotional 2018 grandparentYear: 2018 guid: com.gracenote.onconnect://episode/16236892/2018-12-02 originallyAvailableAt: 2018-12-02 parentIndex: 2018 summary: The First Presidency of the Church of Jesus Christ of Latter-day Saints shares a Christmas message. type: 4 year: 2018' to library item
Subscription: Failed to resolve subscription for episode 'grandparentGuid: com.gracenote.onconnect://show/922694 grandparentThumb: https://tmsimg.plex.tv/assets/p922694_b_v8_aa.jpg grandparentTitle: Studio 5 with Brooke Walker grandparentYear: 2006 guid: com.gracenote.onconnect://episode/922694/2019-05-10 originallyAvailableAt: 2019-05-10 parentIndex: 2019 summary: Ideas to help improve relationships, homes, and communities. title: type: 4 year: 2019' to library item
Subscription: Failed to resolve subscription for episode 'grandparentTitle: KSL 5 News at Noon grandparentYear: 1999 guid: plex://show/5cffa6e2ff28af001e7f18f4 originallyAvailableAt: 2019-05-10 parentIndex: 2019 title: type: 4 year: 2019' to library item
Subscription: Failed to resolve subscription for episode 'grandparentGuid: com.gracenote.onconnect://show/16822533 grandparentThumb: https://tmsimg.plex.tv/tvbanners/generic/generic_tvbanners_v8.png grandparentTitle: Golden Spikes - As One grandparentYear: 2019 guid: com.gracenote.onconnect://episode/16822533/2019-05-10 originallyAvailableAt: 2019-05-10 parentIndex: 2019 summary: A KSL News special. title: type: 4 year: 2019' to library item
Subscription: Failed to resolve subscription for episode 'grandparentGuid: com.gracenote.onconnect://show/191278 grandparentThumb: https://tmsimg.plex.tv/assets/p191278_b_v5_ak.jpg grandparentTitle: NHL Hockey grandparentYear: 2008 guid: com.gracenote.onconnect://episode/EP029977171480 originallyAvailableAt: 2019-05-11 parentIndex: 2019 tagline: This Event title: St. Louis Blues at San Jose Sharks type: 4 year: 2019' to library item
In the Plex server network settings turn off the IPV6, I don’t know if that is giving you problems or the Plex in Docker on OMV host is.
I’ll try it. Plex is running on bare hardware not in a Docker container.
when it is disappearing, could you try out these requests in a browser and see what you get - copying out the responses into text files.
http://192.168.3.14/lineup.json
http://192.168.3.14:80/discover.json
http://192.168.3.14:80/lineup_status.json
I presume this is the DVR - device on 192.168.3.14
it is identified as 106745F1
The log shows it got marked as dead - not sure why
May be some similar issue to New HDHomeRun disappears when setting up
Jun 02, 2020 21:02:45.171 [0x7f415effd700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/106745F1 at http://192.168.3.14
Jun 02, 2020 21:02:45.171 [0x7f415effd700] DEBUG - DVR:Device: Device device://tv.plex.grabbers.hdhomerun/106745F1 was already known, refreshing database info
Jun 02, 2020 21:02:45.171 [0x7f415effd700] DEBUG - HTTP requesting GET http://192.168.3.14/discover.json
Jun 02, 2020 21:02:45.173 [0x7f415effd700] DEBUG - HTTP 200 response from GET http://192.168.3.14/discover.json
Jun 02, 2020 21:02:45.173 [0x7f415effd700] DEBUG - HTTP requesting GET http://192.168.3.14/lineup_status.json
Jun 02, 2020 21:02:45.185 [0x7f415effd700] DEBUG - HTTP 200 response from GET http://192.168.3.14/lineup_status.json
Jun 02, 2020 21:02:45.204 [0x7f415effd700] DEBUG - DVR:Device: Device was alive, refreshed device://tv.plex.grabbers.hdhomerun/106745F1.
Jun 02, 2020 21:02:51.220 [0x7f410effd700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/106745F1 at http://192.168.3.14
Jun 02, 2020 21:02:51.220 [0x7f410effd700] DEBUG - DVR:Device: Device device://tv.plex.grabbers.hdhomerun/106745F1 was already known, refreshing database info
Jun 02, 2020 21:02:51.220 [0x7f410effd700] DEBUG - DVR:Device: Device device://tv.plex.grabbers.hdhomerun/106745F1 died
Jun 02, 2020 21:02:51.955 [0x7f410e7fc700] DEBUG - HTTP requesting GET http://192.168.3.14/lineup.json
Jun 02, 2020 21:02:51.969 [0x7f410e7fc700] DEBUG - HTTP 200 response from GET http://192.168.3.14/lineup.json
Might need to get network packet capture to see what we are getting back at the time and what we respond to Plex Web from the server
I’ll check it out and get a capture. This is a device with the latest 2020 firmware on it. Its possible something changed.
if you get a packet capture please zip the pcap file and send to me by private message
I will also need the corresponding server logs with debug logging not disabled
Thanks for the logs and packet capture.
I am not seeing any ssdp packets from the device in the packet capture. We do appear to rely on ssdp packets and discovery that way and if we do not see these - we mark as dead.
I do see udp packets but not ssdp from the device.
can you check if ssdp discovery is enabled in your linux environment
There is also a Plex Media Server setting
Settings / Server / Network / Enable local network discovery (GDM)
I’ll check that. It initially auto discovers fine. Then disappears. It doesn’t come back for quite a while or or Plex restart.
@karrots I have sent you a development build with a potential fix - it covers cases where the DVR is on a different subnet from the server and added manually or just DVRs not sending out SSDP responses to Plex Media Server SSDP searches
Let me know how it goes and would like to see logs with also packet capture regardless of the outcome
Thanks
@karrots when you do the network packet capture, i would also like to see ssdp packets so please do not just filter the DVR IP address - if possible filter for IP being either the DVR or Plex Media Server and to be either for source and destination
I filtered by the MAC address of the SiliconDust device for the last packet capture. I’ll try to adjust and see if I can get anything better. This device was not added manually Plex discovers it then about 30 seconds later it goes away.
I will have a look - i wanted to see also what the server sends out for SSDP searches and when relative to what we see back from the device - so filtering would need to be both server and dvr and to pick all traffic for both
I hope this isn’t deemed as a “Hijack” of the thread…
I have the HDHomeRun Quatro and last week it started playing up in that every channel watched would stutter and become blocky.
Or the audio sync would be way out, I read about going back 10secs when this happened and it did work but only for a minute or two until the next stutter.
This has been working all okay since December when I got the aerial fitted, details as below:
Plex Version 1.19.4.2935
OS: Ubuntu 18.04.4
Tuner: HDHR5-4DT with fw 20200521
Tuner and Plex server are on different subnets with a firewall rule in place to allow traffic in both directions, had no issues with this until this month.
Now when I setup the tuner all works until I view the guide and then the status of the tuner is:
“Device not found. Ensure your device is powered on and connected to your network.”
When adding the tuner I always input the address manually and the wizard works as expected.
Both Nvidia Shields and Android devices cannot use the Live TV but interestingly if you access Plex via a browser you can select the guide and play/watch TV even with the above error.
Lastly the HDHomeRun app on the shields works as expected.
If I can help in anyway please let me know as I currently have time on my hands.
Nick
