Pluto for Channels

Just a warning....I seem to remember that Plex would get upset if too many tokens were quickly requested by the same ip. Don't know if Pluto has anything similar, but probably deserves keeping an eye out.

2.0.2 pushed with copy fix.

2 Likes

totally!

But we should absolutely get a mainline version of Pluto for Channels. In the past, I just didn't have time to maintain it, especially when people were just forking and not even submitting pull requests.

But I not only have more time, I've got coding agents to help, lol. And this project is a perfectly fine use for them.

If you're familiar with what my version is missing that other versions have, please open some issues, with links to the projects that have the features. Let's get a defect project for everyone to use.

This goes for anyone else that wants to help too. Thanks!

1 Like

How do I get these regions: us_east,us_west,ca,uk. I tried -e PLUTO_CODE=us_east,us_west,ca,uk but it still pulls only the local Pluto channels.

Nice work @KineticMan! I'm streaming 3 Pluto channels right now using a single account, and a single CDVR Custom Channels source.

@bnhf Project One-Click to be updated soon? :wink:

Yes.

2 Likes

Now we can enjoy our Judge Judy, Price is Right, and Jersey Shore channels!

lol I actually do love Pluto -- some great movies on there and you can't beat the price.

works like a charm. many thanks!

I feel like I am missing something obvious here. When I add the second "tuner" (source) I now have 480 more channels in my guide in the 11000 range (original set is 10,000 set in the docker run command).

bnhf/olivetin:latest (aka bnhf/olivetin:2026.02.27) pushed a few minutes ago with an updated Pluto-for-Channels Action. This now uses the @KineticMan fork, which includes single-account, single-M3U support for the latest changes to Pluto. Pluto account required. Supports up to 10 streams:

screenshot-htpc6-2026-02-27-14-20-53

Use the Project One-Click Delete Action to remove any versions you currently have installed -- then run this Action.

1 Like

Totally agree.
I've been waiting for the dust to settle.
This topis (belonging to maddox) is all over the place with different projects.
Each developer should create their own topic for their project, like Bobby Vaughn did

Would also be nice if there was a maintained, locked topic listing all the project topics available.
I think if each project topic was tagged with some keyword, like project-topic a simple forum search would be able to list them all (like bnhf did for project-one-click)

You have to tell the Custom Channels source to use the channel numbers from the m3u. Otherwise, it gives them their own channel numbers.

Agreed, if the project is different. If it's a fork of this original project, then we should consolidate them into a single one.

1 Like

None of these forks are even actual forks. No wonder there hasn't been any contributions back. I guess they were just pushed up as their own fresh repo? :man_facepalming:

The @joagomez Pluto-for-Channels is written in Python, so was not a fork of your project. @Bobby_Vaughn forked that, and @KineticMan forked that fork. I don't believe there was ever another project thread though, and each was published separately.

On a related subject, do you see an advantage to the multiple M3U and CDVR source approach you're using? I've tested the @KineticMan man approach, and that allows multiple streams with a single account and single CDVR source (I tested 3 concurrently).

Imagine setting up 8 of them and how many extra same channels I had :wink:

1 Like

That's a lotta forking forks... :laughing:

You're not forking kidding! :rofl:

Ohhhhhhh. So weird it’s using the exact same name. Ok cool. I’ll check them out.