Server Version#: 1.20.1.3252
Player Version#: 4.41.1
Tuner Make/Model: Hauppauge 1800, two Clearstream tuners also
Guide/Lineup name: OTA
Using XMLTV?:
Channel number/Name:
Hello,
I have been a plex pass member since 2013. this is my first time posting in the forum. I have two clearstream tuners that are giving me just a little trouble. I had chocked it up to they were not very good then realized after reading that they are just difficult to setup. I have one running fine and when i add the second one it freaks out and i can’t get either of them to work. I read a post in the forum that plex mixes them up in older versions of the server and figure that it is still doing the same thing in the post i read they user had worked around this by editting the xml file that identifies them. they were using windows and i am using linux. i am not very adept in editting the database so i backed it up and started just looking. could someone point me in the direction of where the tuners are located.
If it helps here is the post they wrote about it. I am sorry for bugging about this i usually read and try to figure it out without asking stupid questions
[Quoted]
Server Version# : 1.16.1.1291 (Linux, Arch, Docker) / 1.16.1.1246 (Windows, Server 2012 R2)
Player Version# : 3.71.1 (Linux, Arch)
Tuner : 2 Clearstream TVs
When using multiple Clearstream TVs with Plex, Plex gets confused about device IDs and uses the wrong ID when communicating with the second device.
Symptoms :
- When trying to tune a channel Plex gives you an error similar to: “Could not tune channel. Please check your tuner or antenna.”
- A XML parser error (I apologize for the crop):
Troubleshooting :
I was using Wireshark to figure what was going on when the second device was added (and another issue with the Clearstream, but unrelated to Plex).
Looking at the device ID that Plex requested from the Clearstream, you can see it starts mixing them up after the initial setup:
x.123has the ID of9499x.125has the ID of94a8
Notice the 400 Bad Request response near the end of the capture.
The reason why Plex freaks out is because the Clearstream returns the path requested as the body when it can’t understand the request, but Plex is expecting XML as the response.
Workaround :
Working around this bug requires messing with a Plex database, DO NOT mess with it unless you know what you’re doing AND you have backups ! Otherwise just wait for it to be fixed. I messed up once and learned the value of nightly backups. I’m not taking responsibility if you mess up your install.
In com.plexapp.plugins.library.db there is a column 'identifier' varchar(255) . If you look at the contents you’ll notice that both devices have the same identifier. In my case they were both com.geniatech.www . I simply UPDATE 'd the pair of rows (there seems to be 2 rows per device) for one Clearstream to com.geniatech.www2 and everything started working.
(I’m pretty sure the bug is still present in the most recent/Plex Pass version, because that was the version I was running when I encountered the bug. I downgraded somewhere in the troubleshooting process and I have yet to upgrade back to the version I was running. Which is why the version I’m listing is a bit behind.)
(If you’re wondering why I was trying so hard to get 2 Clearstreams working instead of another tuner, I bought them because they were on clearance for $25. I figured it would be a cheap way to get TV on Plex for multiple people in my house considering we have a hard time getting channels except in a few weird spots.)
