SiliconDust HDHomerun tuners

@chrisallen

thanks… looks like it found my tuner/s and it scanned channels and downloaded the over the air guide… only issue I am having is that I am getting write permissions issues during a capture test

I am running plex in a ubuntu VM on esxi

the metadata are stored locally on the plex VM virtual disk
the movie/series/music etc are on SMB shares that are connected at boot by webmin.

plex has been running fine in this config… but I suspect that plex is trying to write out to the series SMB share and that permissions are not right?

I believe the way this VM appliance is set up… most everyting runs as openflixr but plex was installed to run with a plex user… I think that the shares are connected with the openflixr user…

any help here>? anyone… hehe… permissions in ubuntu console are not my strong suit!!

@dragonmel your correct, Plex will try to write to the share to store the recorded files.

You will need to figure out a way to mount the share so that the plex user has the permissions to write to it. Unfortunately openflixr is not an officially supported product you will need to ask the creators how to change the SMB share permissions.

@chrisallen is the shares are mounted with openflixr:openflixr would adding user plex to the openflixr group give uid plex the necessary access

@dragonmel that might work, as long as the group openflixr has read/write access.

thanks… I will give that a shot first I guess…

@chrisallen no joy… I dont see any options in plex mediaserver settings for the acutual path that its trying to use…

where is it exactly trying to write to? is it trying to write to the cifs mount that is set up for the tv shows or is it trying to write to a local directory where metadata is stored?

When you set up the recording you select the library you want to record to. It will create a /path/to/library/.grab folder for temporary storage, then move the contents to /path/to/library/title/season once done.

For what it’s worth, I created a new set of libraries, /mnt/dvr_tv and /mnt/dvr_movies, so I could keep the rest of my library as read-only to the plex user.

@chrisallen

still having an issue

/mnt/series is where tv is located and I can write to it as the plex user. I added plex pid to the openflixr group and the group has rwx on the directory

getting these log entries

Mar 19, 2017 19:41:03.079 ERROR Failed to calculate available disk space for path ‘/mnt/series/.grab’: 1 (Operation not permitted)
Mar 19, 2017 19:41:03.079 ERROR IsDirectory failed boost::filesystem::status: Permission denied: “/mnt/series/.grab/52c173997db2348a120616917483f14907c0ce50”
Mar 19, 2017 19:41:03.079 ERROR Media Grabber: No write permission.
Mar 19, 2017 19:40:27.984 ERROR downloadContainer: expected MediaContainer element, found html
Mar 19, 2017 19:40:27.984 WARN MediaSub: No container available for /tv.plex.providers.epg.onconnect:2/metadata/com%2Egracenote%2Eonconnect%3A%2F%2Fepisode%2FEP003250610024

I seem to be having an odd issue that I have not seen in the forums yet:

When I manually add my HDHR3 it fails immediately with the error “There was a problem adding the device: 192.168.1.19”. When I checked the plex logs I see:

Mar 19, 2017 20:30:26.981 [0x7f88eafff700] DEBUG - MediaGrabber: Checking device URI http://192.168.1.19
Mar 19, 2017 20:30:26.981 [0x7f88eafff700] DEBUG - HTTP requesting GET http://192.168.1.19/discover.json
Mar 19, 2017 20:30:26.985 [0x7f88eafff700] DEBUG - HTTP 200 response from GET http://192.168.1.19/discover.json
Mar 19, 2017 20:30:26.986 [0x7f88eafff700] DEBUG - HTTP requesting GET http://192.168.1.19/capability
Mar 19, 2017 20:30:26.988 [0x7f88eafff700] DEBUG - HTTP 404 response from GET http://192.168.1.19/capability

I am not sure if bold items above are related but just something I quickly saw in the logs.

Model: HDHR3-US
Device ID: 103640AA
Firmware: 20161117

Plex Version 1.5.0.3501

@dragonmel Please open a new discussion for your permission issues. It is good that the HDHR tuner is working, but PMS cannot record due to not having write permissions to your SMB share. Thanks

@cereal3825 Ahh, currently the ability to add a device manually is limited to newer HDHomeRun devices.

are you not seeing your HDHR3-US show up as a device in the setup modal?

If not, please provide logs via the Download Logs option under server settings in Plex Web.

@cereal3825 said:
I seem to be having an odd issue that I have not seen in the forums yet:

When I manually add my HDHR3 it fails immediately with the error “There was a problem adding the device: 192.168.1.19”. When I checked the plex logs I see:

Mar 19, 2017 20:30:26.981 [0x7f88eafff700] DEBUG - MediaGrabber: Checking device URI http://192.168.1.19
Mar 19, 2017 20:30:26.981 [0x7f88eafff700] DEBUG - HTTP requesting GET http://192.168.1.19/discover.json
Mar 19, 2017 20:30:26.985 [0x7f88eafff700] DEBUG - HTTP 200 response from GET http://192.168.1.19/discover.json
Mar 19, 2017 20:30:26.986 [0x7f88eafff700] DEBUG - HTTP requesting GET http://192.168.1.19/capability
Mar 19, 2017 20:30:26.988 [0x7f88eafff700] DEBUG - HTTP 404 response from GET http://192.168.1.19/capability

I am not sure if bold items above are related but just something I quickly saw in the logs.

Model: HDHR3-US
Device ID: 103640AA
Firmware: 20161117

Plex Version 1.5.0.3501

You may want to run hdhomerun_confg discover on the server to see if your devices are discovered.

@chrisallen said:
@cereal3825 Ahh, currently the ability to add a device manually is limited to newer HDHomeRun devices.

are you not seeing your HDHR3-US show up as a device in the setup modal?

If not, please provide logs via the Download Logs option under server settings in Plex Web.

I am running plex in a container and was using bridge mode for networking. I have changed this to host mode and everything is now working.

Thank you @chrisallen and @“Dean Junk” !

@chrisallen

tried your suggestion of a new mount just for dvd_tv and dvd_movies… made the user:group plex:plex and added 2 new libraries DVR TV and DVR Movies that use those folders in the new mounted volume.,

seems to be working now with the orginal HDHR-US dual… nice…!!

some questions thought…

when I turn on on the fly transcode… the finished recording is showing up as a 1080p progressive .h264 … and with my ipad on the same network and set to play native - i.e. full stream no transcode…why is plex re transcoding it when playing to the iPad? 4.0 main is what I use on all my blu rays and they stream direct play to the ipad no problem?

so I guess i will just let it store the mt stream and transcode on play… or start searching for a good transcode/comskip script for postprocessing on ubuntu…

feature request… can we have a recently added DVR on the main page instead of burryign new recordingd into recently added TV and recently added movies?

anywho… been with plex since the beginning and a plexpass user… and this is a really nice push so far with 1.5!!!

keep up the good work…

@chrisallen said:
@“livøvænget”

If it’s easy you can simply use the Download Logs option under server settings.

Please upload the ZIP file here and I can hopefully figure out what the issue is.


I only get the Media Server log, not Tuner Service log

@chrisallen

any plans to control recording schedule from the plex apps like iOS/android or will it stay web interface only?

I too have issues with adding my DUAL. Like someone else mentioned, I too am running this as a jail on FreeNAS… running this newest version of PMS.

(


(

When I try to add a new device, I see it trying for a while. I know my IP address is 172.18.1.30 for the DUAL, so I entered that manually and get an error.
(

I didn’t see anything standing out in the “Plex Tuner Service.log” but in “Plex Media Server.log” I see:

Mar 20, 2017 16:43:44.869 [0x809815400] VERBOSE - * uri => 172.18.1.30 Mar 20, 2017 16:43:44.869 [0x809815400] DEBUG - MediaGrabber: Checking device URI http://172.18.1.30 Mar 20, 2017 16:43:44.869 [0x809815400] DEBUG - HTTP requesting GET http://172.18.1.30/discover.json Mar 20, 2017 16:43:44.973 [0x809815400] DEBUG - HTTP 200 response from GET http://172.18.1.30/discover.json Mar 20, 2017 16:43:44.973 [0x809815400] DEBUG - HTTP requesting GET http://172.18.1.30/capability Mar 20, 2017 16:43:45.076 [0x809815400] DEBUG - HTTP 404 response from GET http://172.18.1.30/capability Mar 20, 2017 16:43:45.076 [0x809815400] DEBUG - HTTP requesting GET http://127.0.0.1:32600/devices/ Mar 20, 2017 16:43:45.077 [0x809815400] DEBUG - HTTP 404 response from GET http://127.0.0.1:32600/devices/ Mar 20, 2017 16:43:45.077 [0x809815400] ERROR - Error parsing content. Mar 20, 2017 16:43:45.077 [0x809815400] ERROR - Error parsing XML. Mar 20, 2017 16:43:45.077 [0x809815400] ERROR - MediaGrabber: Error obtaining device status. Mar 20, 2017 16:43:45.077 [0x80980e400] DEBUG - Completed: [172.18.3.10:32085] 404 POST /media/grabbers/tv.plex.grabbers.hdhomerun/devices?uri=172.18.1.30 (5 live) TLS GZIP 208ms 452 bytes (pipelined: 3)

This made me a little curious, seeing the URL of http://172.18.1.30/discover.json, so I looked it up:
{"FriendlyName":"HDHomeRun DUAL","ModelNumber":"HDHR3-US","Legacy":1,"FirmwareName":"hdhomerun3_atsc","FirmwareVersion":"20161117","DeviceID":"103584B6","DeviceAuth":"D93LgdQJFpYqBR1azvrumrrD","TunerCount":2,"BaseURL":"http://172.18.1.30:80","LineupURL":"http://my.hdhomerun.com/api/lineup?DeviceAuth=D93LgdQJFpYqBR1azvrumrrD"}

I’m hoping someone can figure out what the issue is.

@RonRN18 Your PMS needs to be in the same network (bridge network) with the HDHR Dual since discovery is done in a similar way to MDNS. Currently the ability to add a device manually is limited to newer HDHomeRun devices.

@johnny15 said:
Wow, fairly big news. In case people missed it…

(DVR) Support all SiliconDust HDHomerun tuners, including older generations

https://forums.plex.tv/discussion/comment/1399343/#Comment_1399343

Great job, Plex!!

just saw this post and updated my Plex Server. Im up and running on my old HDHomeRun Dual. Thanks.

I just bought the Connect yesterday though… to bad i didn’t see this post earlier.

@chrisallen said:
@RonRN18 Your PMS needs to be in the same network (bridge network) with the HDHR Dual since discovery is done in a similar way to MDNS. Currently the ability to add a device manually is limited to newer HDHomeRun devices.

It is on the same network; my private network is 172.18.0.0/20 (netmask of 255.255.240.0) so everything between 172.18.0.0 through 172.18.15.255 is within my private network. It also had no problems finding my other three devices which are 172.18.1.31-172.18.1.33 while my PMS is 172.18.11.110.