dvr - (2) hdhomerun tuners cannot record 3 shows at the same time

General Discussions Plex Features
1

Bug:
I have (2) hdhomerun EXTEND tuners and have scheduled multiple concurrent recordings. When it is time for the recordings to start, two of the three recordings start.
Further signs of trouble … Plex DVR shows the status of the two tuners with one tuner active on each of the two hdhomerun devices, while investigating the status of the hdhomerun tuners directly shows both recordings on the same hdhomerun (not one on each).

Note: I am certain that 3 recordings are possible, so long as they do not start within a short time of each other. I have 3 recordings going on presently because two started 30 minutes ahead of the 3rd. In other words, 2 recordings seem to start at the same time without much trouble, but 3 is definitely a consistent/reproducible problem.

Platform / Version:
Ubuntu Linux 64 / 1.9.0.4252

The following log info is suspicious:
Sep 18, 2017 19:04:11.642 [0x7f1838bfb700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (40f7cd31-0d41-4907-9ea9-2d51cb8894e5, expected af26c694-4c0f-4bac-86fc-20d6f3a3e961)
Sep 18, 2017 19:04:12.242 [0x7f1838bfb700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (82c57ddb-1e0a-4c86-b4c7-d860570da5bd, expected 88bbd2dd-6d74-4243-b23e-2fe0fded6c6e)
Sep 18, 2017 19:04:12.242 [0x7f1838bfb700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (cc140f3e-f89b-4869-b8c3-d51256429a1e, expected 88bbd2dd-6d74-4243-b23e-2fe0fded6c6e)
Sep 18, 2017 19:04:12.242 [0x7f1838bfb700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (6c9eb83b-a931-42e1-8b53-82e4850176fb, expected 88bbd2dd-6d74-4243-b23e-2fe0fded6c6e)
Sep 18, 2017 19:04:12.459 [0x7f1838bfb700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (af26c694-4c0f-4bac-86fc-20d6f3a3e961, expected 88bbd2dd-6d74-4243-b23e-2fe0fded6c6e)
Sep 18, 2017 19:04:52.187 [0x7f1838bfb700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (1fa1962c-2065-4ac1-9041-cce5898cc8cf, expected ddda5fbb-d5a7-424a-ac77-794ddbf32d98)

2

@DaveBinM - would you like to say it? :slight_smile:

and how forthcoming is forthcoming?

3

@EABenton I’m still a few days behind (working my way through post by post), but sure!

@larson9000 This should be fixed in a forthcoming release. Exactly when, I’m not sure, but hopefully not too far away :slight_smile:

4

@DaveBinM Thanks!! x 2 :slight_smile:

5

Thanks! (Something tells me that my search of the forums was “weak”. I’ll go now and see if I can find evidence of the answer out there.