Pluto and Samsung TV Plus work just fine for me on TiviMate.
1 Like
If you're running the jgomez docker version, check the environment variable PLUTO_CODE= which defines what countries will be available. Channels DVR will only grab the first 750 channels.
https://github.com/jgomez177/pluto-for-channels?tab=readme-ov-file#environement-variables
Okay I do have that enabled, it just started doing this, I have added and removed the source. I installed it from OliveTin. Still no luck.
According to your Custom M3U Channel setting
The Pluto TV (UK) channels will start at 7673 in your guide
Not 7625
If you have multiple custom m3u sources and you use a start channel number in the settings, I find it best to separate them by 1000 to prevent overlap (limit 750 per source).
i.e.
Source 1 1-1000
Source 2 1001-2000
Source 3 2001-3000
...
3 posts were merged into an existing topic: [RELEASE] Playlist Manager for Channels [Streaming Library Manager Extension]
Anyone having issues with Pluto not working today? It was working fine overnight but when I went to stream something I just get the "Connection Lost" message no matter which channel I try. I have restarted everything and the standalone PlutoTV app on my Andriod TV boxes all connect and stream without any issues.
Is there someplace to see any errors that are generated to help in troubleshooting the issue? When I look in Docker at the log for instance it just shows Success at the end of loading and no errors.
Not working for me. Have been using nocords.xyz forever...
Edit: Pluto app on Android is not working for me either. "We're having trouble playing this title" error...
Edit: Works now.
I got that the 1st time I tried the app but then it started working (and is still working currently).
Edit: Spoke too soon, after exiting the app it no longer connects so it looks to be a Pluto issue.
Back to working again!
Looks like Pluto is now requiring account log in on some live channels. Hoping for a docker update to allow us to log in.
2 Likes
Some more recent detail to add to what I posted a couple of months ago about this and others started talking about going back six months now...
From the article:
Paramount has emphasized that this is not a full lockdown; unregistered users retain broad access to the catalog, and the restrictions vary by region and device as part of an A/B test. Early feedback... highlights frustration, with many describing the prompts as intrusive pop-ups that interrupt channel surfing. Some report the limitation appearing inconsistently, affecting Roku devices more frequently than mobile apps, leading to speculation about phased rollouts.
Thus, it sounds like it's all still in flux and different depending on who and where you are, which might make it difficult to implement a universal solution. Still, it'll require a way to login through the API, which I'll turn to @joagomez to confirm if its a possibility right now.
1 Like
I'm working on a fork that I still need to finish testing. I added username and password support as well as support for German Pluto feeds.
2 Likes
If anyone tries to run it and it breaks, don't be too surprised. I'm pushing untested code on some of the updates for the next day or two. I already had python indentation errors twice 
.
2 Likes
Thank so much for taking on the update.
I will be watching how things proceed.
Sorry to keep posting in this thread, but it seems to be working as expected. You can verify your credentials are returning a valid token by navigating to the container with the port you are using like this:
http://<your_server_ip>:<port>/<country_code>/token
e.g. http://127.0.0.1:7777/us_east/token
If a very long token is returned, it works. If Error is returned, you have an issue with your username or password.
I have the container online and it appears to be working. The password on my account had to be changed becuase it was too long or had stuff the docker didn't like.
Let's see how it plays.
If the username and password is wrapped in single quotes, e.g. 'password', they will be interpreted as literal characters and should avoid issues with characters that have special meanings.
Edit: Thanks for the feedback @rpaulmerrell I'll make sure to mention the single quotes in the readme file. I am also working on some improvements that will hopefully speed up the the script and lower the resource usage when it loads the guide data. I will test those before I push the update. I would hate to create a bunch of new issues that weren't there before.
Thanks for the great help.
the verification of my valid token worked out great so i know it is logging into Pluto.
I will test and see what happens.
1 Like
I have a test version that could use some testers. I made a lot of changes that should improve its performance, but could also cause issues on some setups. Some of the changes include instead of pulling the Pluto guide data one chunk at a time, it now pulls it 10 chunks simultaneously. It no longer holds the entire multi-megabyte EPG in memory while it's building, now it processes the guide data and writes it directly to the .xml file piece by piece. It also builds all the data guides at the beginning, before the server starts to avoid a potential race condition. This test version uses the :test tag rcvaughn2/pluto-for-channels:test