Non-Docker source for PlutoTV m3u playlists and EPG

Ah...well crap.
Hopefully, they are just on vacation or busy and will maintain it.

Was just about to dump Philo, as pretty much just stick with the channels provided by the dockers/nocords for Pluto, Plex, Samsung, as those are the ones i most watch....
Quite convenient that soon as i am about to do that....things go to hell and nothing is reliable anymore.
:unamused:

be the change you want to see in the world

1 Like

I meant for those users that make a new project to address this...or, maybe a time to retire this thread and make a new master thread for working Pluto integration solutions, as the OP (from 2021) has way outdated info and the user who posted that has nothing to due with things that do work, as it seems.

What region would be the same to what nocords provided, ALL? Or is ALL included every region option, which may exceeded what Channels accepts for number of channels.

I am not sure what Local, US East, US West is compared to what nocords uses, far as i know, was just US for the jgomez docker i used.

EDIT: Looks like ALL has 750 channels. LOCAL has 405 Channels. (The nocords had 411)
And Channels did NOT save or match up to the same channel numbers or favs when i changed the URL. So, have to redo all of that.
(I am using the Windows.exe)

I really don't know what nocords had. Mine is a fork of jgomaz docker, but that was like 5 or 6 months ago and I can not remember what all I changed in it. I do know I added the German feed. I will look at it tomorrow and try to provide some answers to this.

Awesome! Thanks Jon. I was not expecting it so quickly. Enjoy your evening.

1 Like

Works great here, Thanks! Didn't wanna fiddle with a container, your Windows app filled the nocords void perfectly for me.

The 750 is the limit that Channels will import. The all has a lot more but would have to be broken up by a playlist manager.

Thanks for the update. I will be working on it the next few days to find and fix any bugs that pop up.

Yea. Figured out I want to use LOCAL to get the equivalent to what nocords was giving me i guess.

I am trying the Window exe you made. Seems to work so far. Thank You so much for that!
Will it auto start with Windows, or do you need to add that option into it?

I had to re-do my Favs and Channels collections as the numbers did not match up, but i gather that is due to me using custom set channel numbering.

Would be cool to also have a Widows based app for Plex and Samsung.

1 Like

Many thanks, it works perfectly :+1: For now don’t need login for France, but as all other, old links didn’t work anymore because old links use the V1 Pluto API, as your software use V2 Pluto API links now it’s ok again, and don’t need any login.

Perhaps @maddox and @HankLloydRight can use the V2 API links?

For France as it doesn’t require Login, if JM2P server can return to V2 Pluto api link for all channels and not only DAZN channels, it will work, same for all countries without account required.

1 Like

@Bobby_Vaughn I am getting alot of "The connection to the tuner was lost" when i try to play any channel for more than a couple minutes. 10 secs active channels stream then it fails.

The logs in Channels show for example
[TNR] Error during live stream for ch2142 Top Gear: Playlist had no segments: https ://cfd-v4-service-channel-stitcher-use1-1.prd.pluto.tv/v2......super long url.

I have two servers using the generated playlist from the windows program.
Is that the issue? Does this only support one device now?
I was able to use multiple devices with past methods fine.

EDIT:
Looks like the Windows.exe solution only supports one device/one stream at a time.
I get Connection to tuner lost if it try to tune another channel on same server or use it on another server.
Can't record one channel/watch another etc.

@maddox Same issue with your Docker. I can only have one channel playing globally, if i try to open another one, on another client for example, it says tuner lost connection on the active stream. Even using the "multiple feeds" playlist options.

Ok. I do not see any posts on this. (as of yet)

You can only have ONE active stream globally.

Per account/ per source you use.
Meaning only ONE client can be playing any Pluto channel at a time.
If you are recording a channel, tuning a new channel live will cause the recording stream to stop.
The newest client to tune a channel gets priority.

The only thing i have been able to accomplish, with my setup of 2 separate servers, one for me to use, one for my mother...

Is to use two different sources and different Pluto accounts (emails).
I use the Windows.exe for mothers account, the Maddox Docker for mine.

This results in each server being able to stream one Pluto channel each, without canceling each other out.

However, again, each server can only have ONE active Pluto TV channel in use at any time.

I hazard a guess that this is a new limitation by the new Pluto API / this new requirement of Account login?

1 Like

Hi. Just got the Windows.exe going. I'm looking to a similar setup and run the Maddox Docker as well. Other than the simple copy paste method I used previously, I have little/no detailed experience running Docker. Very much still learning. I'm trying to run the Maddox startup code

docker run -d --restart unless-stopped --name pluto-for-channels -p 8080:80 \
 -e PLUTO_USERNAME='[email protected]' \
 -e PLUTO_PASSWORD='yourpassword' \
 jonmaddox/pluto-for-channels

but keep getting -e PLUTO_USERNAME & -e PLUTO_PASSWORD error messages. Do I remove or keep the single quotation marks around my username & password?

Also, before I paste the code, I get a warning about running multiple commands - is it ok to run the entire code at once?

@MisterMustang Try running it like this if you are using the Windows Terminal or Powershell:

docker run -d --restart unless-stopped --name pluto-for-channels -p 8080:80 -e PLUTO_USERNAME="[email protected]" -e PLUTO_PASSWORD="yourpassword" jonmaddox/pluto-for-channels

Once the stitcher builds the proper url and hands it to Channels, it is handled by Pluto from that point on. I will look into it during testing but I have not seen that behavior during use.

Pluto could be limiting it by device ID. I will test a work around today and see if we can fix this.

I'll give that a go & let you know how it goes. My thanks for the assist. It's appreciated