correct
So sad… Why Plex wants to play with multiple versions is a mystery.
Cool beans:
1 Like
Many of the channels once missing for me in the UK are now available via the new EPG provider, however, I now have different channels with no data 
I can’t win!
PMS on Nvidia Shield
Ok, seems from recent research that PMS on Nvidia Shield has issues, hence lagging behind on updates. Just got notification of update yesterday to 1.16.0.1126. Today I see this email regarding the EPG and PMS version 1.16.1, so I check for newer version; none.
When will an update be available?
Is your update channel set to “beta”?
Yes, Server update Channel is set to Beta
The update for the Shield has already been been submitted to the Google Play appstore. So it should be landing on your device within the next hours.
Thanks for heads up
Hi @OttoKerner, I am not sure if the team is awared of this issue but as soon as I upgraded the guide data based on your zip code get miss configured. I currently have a HDHR prime tuner device which uses cable cards, and after upgrading to the latest beta, the guide started refreshing using Comcast and I have Verizon Fios. I do not think there is a way to modify the location and cable company lineup after you have added the tuners. All my scheduled recordings were gone because of the channel number mismatch between comcast and verizon. I ended having to delete all my tuners and re-add/re-configured them again. The issue is now fixed for me and it pulling the right guide data, but I also think it is affecting people using OTAs.
Yes, this can happen.
I had the same issue, because the cable operator was listed with a different name in the new EPG. I had to erase the DVR and recreate it.
This is such a stupid process by Plex. I received the email, saw a notification about new version, installed it, thinking ‘job done’. Then looked at file I had downloaded prior to deleting it only to see it’s 1.16.0, not 1.16.1. Why would you send an email out requiring an update before you’d actually pushed the update? Or at least not mention it? I don’t buy the PlexPass forum version answer at all as most customers won’t even be aware of that.
1 Like
ok that is what happened to me then… probably Verizon Fios was named differently with the old provider
Has it been announced when the non-beta v1.16.1 is expected to be released? Like others I expected to see an update yet one is not available.
1 Like
So who’s the new EPG provider? Does it say down bottom of guide where Gracenote used to appear?
I’m also curious who the new EPG provider is. I switched to Zap2XML a while back after multiple gracenote outages but am open to switching back if the new provider is an improvement.
Was wondering the same thing and hoping that it would support a EPG per tuner which it doesn’t so back to XMLTV for me. Prefer not to have to compile my own EPG but have to with Plex.
Installed the update when I got home. Had Zap2XML XMLTV set up and wasn’t expecting to be switched to the new Plex EPG provider. However it seemed like I was switched since there were missing channels and the scheduled programs weren’t right. Had to reconfigure XMLTV which seemed like an unnecessary inconvenience but wasn’t all that hard. First I tried setting it back up with Plex’s new provider, to see if I could use it. While some of the missing channels seemed available, others showed as “coming soon”. So seems that I’m better off with XMLTV for now. Have to see how it develops…
- Update - the “coming soon” I saw actually came from the label of a local OTA channel. I didn’t realize that had changed. So that wasn’t an issue with the new plex EPG ras I’d thought. I’ll try it again at some point but just got my XMLTV set back up and don’t want to mess with it right now.
I’m confused by the email. Do we have to manually update to version 1.16.1 or will it automatically update like it normally does with the settings I use?
If your update channel is set to ‘beta’, it will update automatically.
If it’s set to ‘public’, it won’t.
