Thank You
I have referred this to Gracenote asking to look into availability of the WKAQ 2.11 / 2.12 / 2.21 / 2.22 channels in the lineup and also adding 4.3 WTIN3 to the lineup. The lineup already has 4.1 and 4.2 WTIN channels
They were looking into this to establish if the stations were full power
The channels being 47.7 to 47.9
(rabbitears.info view)
I have asked Gracenote for status
I have referred the lack of logo to Gracenote
Which should correspond to: K30MM-D GILA RIVER INDIAN CO, AZ
The EPG data seems to be pretty far off current reality for a bunch of the smaller channels in the Phoenix/Prescott area. The major channels look mostly correct though. My zipcode is 85383.
1 Like
I have been getting the “To be announced” message on the London Freeview guide for a while now, loads of missed recordings due to it.
Is this going to be fixed? Or is there a solution that I am not aware of?
Thank you.
How do I find out?
I had configured literally hundreds of recordings for TV shows and if several TV stations air a show, I may have set up “limit to channel”. There’s no way for me to check without clicking through each an every one of it individually.
The recording pre-set is a mess. I wrote an article years ago of how to change the way that recording pre-configuration survives all kind of internal changes like the one in this topic or metadata provider changes or whatever.
Since almost nothing of this has been done, I can only do Plex DVR as a backup service. Lately, Plex discontinued my Buffalo Windows 2012 server NAS OS, so I cannot do any further updates. Now, you discontinue some of my own pre-configs for recordings.
This is what I call a mess. And I will not buy new hardware and re-configure everthing every few months just to let Plex put TV show recordings on those hard drives of mine.
I have another “production” Plex server but I will not switch on DVR function on that server. Simply too much work and too much hassle.
@sa2000 you are an excellent supporter, so please don’t take this as personal. But the whole idea of having a DVR like this is to setup-and-forget. I am not recording two or three TV shows. Your way of doing it even prevents that I can setup all of the hundreds of TV show recording configurations (since most of them are not aired in the short period of time that you provide metadata for) on another Plex server.
Rendered unsusable. No key-word-based recording → I am out of Plex DVR.
1 Like
It’s been 5 days since this was escalated. I’d imagine as a high priority as having a DVR with missing EPG goes against the whole point. However the problem still exists. Can you please provide a detailed update on the response to your escalation and a time frame that this will be sorted by. @sa2000
I don’t have any information on that. I have escalated the problem to get it looked into
I just wanted to add in and say I’m getting this in the UK also! My examples revolve around Emmerdale on channel 3/103.
It’s certain shows, on certain days that are marked as “To Be Announced”. And it’s not one show that doesn’t show up, Emmerdale (TV show) is pretty much on Mon to Fri, and it’s just certain eps that get missed! So it’s not a time/show issue, as in it’s not repeating like that. I do see in the EPG that other other “To Be Announced” info appears all over the EPG.
No matter how many updates I do to the EPG it won’t fix and removing and re-adding does nothing. It’s defiantly a PMS and/or EPG provider issue; in that, PMS is messing up interpreting the EPG data, or the EPG data is just wrong.
I know there’s nothing generally wrong with UK EPG as I have Jellyfin setup, with custom XML OTA EPG and it has no issues at all. I’ve had to resort to using Jellyfin as a secondary DVR, to a separate folder, that’s then added as a new media library in Plex, just so that we don’t miss recording!
Same issue for me in the UK - lots of ‘to be announced’ peppered throughout the guide, plus BBC HD has lost it’s icon and no amount of refreshing is fixing either.
1 Like
We found an EPG gracenote data ingestion failure that would lead to the TBAs not being replaced by actual program data. The fix was deployed yesterday but also need to re-ingest some EPG data.
We expect the TBAs to get replaced over the next few days - leaving only that ones that are normally there towards the end of the Guide covered timeframe.
So please make sure EPG refreshes are completed daily over the next few days. This runs normally during daily Plex Media Server scheduled housekeeping tasks.
Please let me know if the problem persists next week giving me details of times/channels/lineup/zip code.
4 Likes
One would need to check the individual scheduled recording to see if Limit to Channel is used. I have already raised a request to our development to see if those can be switched correctly to the new lineup.
I do not believe you are using any of the lineups that are affected - I may be wrong
I am bringing that into discussions internally
The problem seems to be fixed for me, just done a quick browse through the next week and all looked good, thank you.
1 Like
Mine seem to have clean-up for the coming week, but the following week still has a lot of TBA for certain channels. That said, I’ll try and keep an eye on it next week and see what happens 
Well, in my case it looks much better now…
The rest are only a few stupid TV stations or Radio broadcasts
Our next version 1.23.4 will have a fix for this. I sent you by PM link to download the alpha build for this release - please could you try it and confirm that that it fixes the problem. Please do a test recording into a new temporary test library to see that the original available date gets preserved
You can see check for your normal recordings. If you continue to have the problem, please give me details again or channels/show/episode/airings with debug server logs and also send me by PM zip of the database - taken after recording completes and then again later when you see it is changed
The fix in version 1.23.4.7126 and later should ensure we preserve the EPG metadata - this may not apply if the show was previously matched
We have a fix coming out in PMS 1.32.4. I sent alpha build to try to @goellnjh who is having the same issue. I see that you are running the server using docker - unfortunately I do not have a way I can make a development build or alpha build available for docker and will need to wait until release 1.32.4.7126 (or later) become beta
Update: version typo corrected ! sorry. dyslexic fingers
I’m seeing Unknown Airing for several channels starting at 5 PM on Wednesday 5/31 and lasting for 24 hours. These are Local Broadcast Listings for the 94087 zip code.
Channels include: 2.3, 4.2, 9.1, 14.4, 22.2, 65.2, 68.1, 68.2, and 68.4.
@sa2000 unless I am misunderstanding the version numbers the current upgrade screen shows my server is running 1.32.2.7002 and an upgrade is available to 1.32.3.7089.
Based on the version you have listed (1.23.4.7126) I should already have the fix since it’s earlier than the one I’m currently running. Please advise.
Given the build number (7126) I think that is a typo on @sa2000’s part and it should have read 1.32.4.7126.
1 Like
