Plex Live TV Channels M3U?

There is not.

These URLs for EPG from one of our fearless leaders at the start of this thread are still active.
https://i.mjh.nz/Plex/

But I can't attest to their accuracy as I haven't found a currently active M3U to use it. If anyone has a working one that that would be fantastic. I will add tho eyeballing the US file contents to the Plex Live TV App Guide, series+episode numbers seems to lineup.

In case anyone else is having the same issue I am with @joagomez's Plex Docker:

Interesting @babsonnexus

Im not using a docker. Ive hard coded this plex epg link into a custom channel.

https://i.mjh.nz/Plex/

Been using for over a year.

As of yesterday Ive observed guide issues with that hard coded custom channel, but when i go to the url above that seems to still be alive.

Do you folks using the docker solution also indirectly call the link above, or do we just by coincidence have two separate problems with the plex guide?

No, the Docker builds its own guide using a similar, but different method. I tried to see if there was something going on in the i.mjh.nz, but nothing in particular stood out.

1 Like

As expected it was a coincidence.

I found my issue here..

Weird that the M3U affected the guide that way..

Resolved issue (hopefully) in the docker container.
Issue was there is a channel not returning any EPG data which was expected.
Updated how the data is read so that if the size is 0 (i.e. no EPG Data) it skips

4 Likes

Yay, it worked!

2024-11-07 20:19:23 Initialize XML File
2024-11-07 20:19:23 Run channels to load self.channel_list
2024-11-07 20:19:23 New token for local generated at 2024-11-08 01:19.23 +0000
2024-11-07 20:19:35 Day One Initialization of EPG data
2024-11-07 20:19:35 Retrieving local EPG data for 2024-11-08 through 2024-11-08
2024-11-07 20:20:48 Continuing to retrive local EPG data....Elapsed time: 73.57 seconds. 150 Channels parsed
2024-11-07 20:22:17 Continuing to retrive local EPG data....Elapsed time: 161.71 seconds. 300 Channels parsed. Please wait
2024-11-07 20:23:04 Continuing to retrive local EPG data....Elapsed time: 209.13 seconds. 450 Channels parsed
2024-11-07 20:23:56 Continuing to retrive local EPG data....Elapsed time: 261.17 seconds. 600 Channels parsed. Please wait
2024-11-07 20:23:59 Retrieving local EPG data complete. Elapsed time: 264.06 seconds. 607 Channels parsed.
2024-11-07 20:24:02 ⇨ http server started on [::]:7777

I looked at the code compare and you made it appear so simple. I was beating my head against the wall trying to figure out if there was missing parameter or something I could help point to. This is certainly much more elegant!

LOL! thanks but only because I knew what I was looking for....
Obviously something didn't have the "Medata" key so when I added more debugging some channel returned this

{'MediaContainer': {'offset': 0, 'totalSize': 0, 'identifier': 'tv.plex.provider.epg', 'size': 0}}

And this is not what I had ever seen - way too short - it's usually a lot longer so decided to key off of the 'size'

May add which channel gets skipped with no data in the logs later once I'm sure this continues to work

Trying to understand the guide update process for the Plex Docker and Pluto Docker setups - how often does the master M3u lists for each get updated? I installed what I think are the latest versions v1.13 and v1.18. All working, but my guide data does not go very far into the future - maybe this is normal? I have the source settings checking to pull the list from the container url every hour. Is there some setting or maintenace to be done on these docker instances?

1 Like

Yes, this is normal. That's all that's available, these scripts are only capable of indexing what the FAST sources themselves provide. Some go further into the future than others. Some are really short. One hour refresh is the best you can do.

Thanks! Does the "Last updated" date, in this case Nov 7th, indicate the update date of the container code, or the date of the epg data? If the latter, how often does this increment?

This :point_up:

I am sorry I am not following what is the fix? What do I need to do to get it working again?

I keep seeing this.

2024-12-01 16:07:30 New token for local generated at 2024-12-01 21:07.30 +0000
2024-12-01 16:07:30 Retrieving local EPG data for 2024-12-01 through 2024-12-01
2024-12-01 16:07:53 Continuing to retrive local EPG data....Elapsed time: 22.40 seconds. 150 Channels parsed
2024-12-01 16:08:23 Continuing to retrive local EPG data....Elapsed time: 52.83 seconds. 300 Channels parsed. Please wait
2024-12-01 16:08:46 Continuing to retrive local EPG data....Elapsed time: 75.31 seconds. 450 Channels parsed
2024-12-01 16:09:16 Continuing to retrive local EPG data....Elapsed time: 106.10 seconds. 600 Channels parsed. Please wait
2024-12-01 16:09:17 Retrieving local EPG data complete. Elapsed time: 106.94 seconds. 615 Channels parsed.
2024-12-01 16:39:20 Retrieving local EPG data for 2024-12-02 through 2024-12-02
2024-12-01 16:39:20 Scheduler crashed: 'Metadata'. Restarting...
2024-12-01 17:09:20 Retrieving local EPG data for 2024-12-02 through 2024-12-02
2024-12-01 17:09:20 Scheduler crashed: 'Metadata'. Restarting...
2024-12-01 17:39:20 Retrieving local EPG data for 2024-12-02 through 2024-12-02
2024-12-01 17:39:20 Scheduler crashed: 'Metadata'. Restarting...

can you try restarting the container?

1 Like

Thanks, seems to be working.
Stupid me should have tried that first.

1 Like

does give me something to look at as it should have recovered itself but isn't. at least the restart worked

Great Docker Container!! Seems to work pretty well just tried it today.