Why do I get 'all tuners in use' failures?

My HDHomeRun devices are exclusively used by Plex, yet I see requests rejected because all tuners are in use. I see this even when one complete device (2 tuners) is idle, and available with the same channel lineup. I have noticed the DVR Settings page can be wrong about which devices are in use; in this case below it showed one tuner in use on each of two devices, whereas the device logs themselves showed one whole device idle, and the second device rejecting a request.

20170601-19:00:00 Tuner: tuner0 tuning 10 ITV3 (t8qam64:506MHz-16048)
20170601-19:00:00 Tuner: tuner1 tuning 105 Channel 5 HD (tt8qam256:546MHz-17728)
20170601-19:00:01 Tuner: tuner0 streaming http to 192.168.122.183:54246
20170601-19:00:01 Tuner: tuner1 streaming http to 192.168.122.183:54249
20170601-20:00:01 HTTP: rejecting request from 192.168.122.183 - all tuners in use
20170601-20:40:00 Tuner: tuner1 tuning 19 Yesterday (t8qam64:530MHz-25792)

This seems to have started with the recent changes, around the time of the .ts -> .mkv shift

What it feels like to me, is that Plex is not keeping track of its tuners and addresses properly.

I have tried removing whole devices, deleting and recreating the DVR, changing nothing. The device that is used is the second device added in the latest recreation, with the higher IP address.

Version 1.7.2.3878 on MacOS, 2 x HDHomeRun CONNECT (HDHR4-2DT firmware 20161117)

We need full logs to debug this. Plex Media Server and Plex Tuner Service as well.

Will turn on verbose logging and wait for it to happen again; thanks.

Captured one error at 2100 (BST) local, 2 tuners available on one device, none on second device, but second device was selected. Logs and HDHomeRun system logs and screenshots attached.

I particularly liked this one:

Hey everyone, I just bought a second ‘extend’ HDHomeRun tuner and am trying to record four shows at once to try it out.

I am having like issues where I can record two shows on the first ‘extend’ and then it says that my third recording conflicts with the previous two shows when I obviously have two tuners remaining. Basically, it won’t carry to the second ‘extend’ device.

Does this seem like the same issue?

I’m getting this issue, or one much like it: Plex says my Connect (the only tuner device I have associated with Plex) has two tuners, three of which are in use. Additionally, a recording has been visible in the schedule as if it is currently recording, even though it finished more than two hours ago. I haven’t restarted the Plex server since then, but I have pulled the power and network connections from the Connect at least twice since then (I only got my Connect today, so I’m still working out where best to put it).

Edit: now showing “2 tuners - 2 recording now” when the Connect itself shows neither tuner in operation. Additionally, only one of the two simultaneous recordings I just told it to make was actually completed: the other shows a warning symbol with no explanation of why or when it failed.

There are several folks having similar issues. We have a PlexNinja looking at it. http://forums.plex.tv/discussion/282378/multiple-hd-homerun-primes/p3

This thread is very disappointing. I was having so many issues with a USB tuner in the nVidia Shield that I bought the HDHomeRun Connect because it seemed more reliable. I hope when I hook everything up tomorrow I get two tuners and two recordings!

@“thalfmanamiga@gmail.com” You should be fine if you only have the one Connect device. I get 2 recordings currently. Plex just fails to record 3 or more recordings at the same time because it will not utilize my 2nd Connect device. What I am actually seeing when Plex records is that it “thinks” my first Connect device “10.0.1.22” is being used for recordings, it has actually used the 2nd Connect “10.0.1.28” when it started the recordings. So when it tries to started a 3rd or 4th recording it tries to use my second Connect “10.0.1.28” but all of it’s tuners are already in use so the recording fails. I can record 2 shows at the same time all day long with no issues. Hopefully Plex will have this resolved soon since the problem has been replicated by Plex.