ESPN+ & FOX Sports with Custom Channels via EPlusTV

I don't remember this, and I checked my PRs and I don't see anything from you:


Sorry if I missed something? I don't have a photographic memory of every comment in this thread

I have never pretended that there aren't any flaws. Like I said I do this in my very limited free time.

I added Mountain West that @doug8796 suggested because it literally took me 5 minutes. Sorry my priority list and yours don't line up.

Besides I didn't say that I wouldn't add any providers - just that I wouldn't/couldn't do every.

Fixed now. You'll have to clear your entries and schedule files and start the container again though

2 Likes

Oh, I added support for NESN (with 4K home games) yesterday for those that have access to that

7 Likes

It is because of this that I'll be deleting my shared info. I want to focus on chrome capture and not offer help in the grey areas. Mongr31l code is very impressive. We should be grateful for what he wants to implement. I assume it would work for tsn as well in Canada, but we can't access without VPN. Ok so fox 4k broke, he says it himself this code will work until it breaks it again . It's cat and mouse and we all know what we are up against

CBS Sunday ticket breaks TOS and could be troublesome

2 Likes

Don't listen to the negativity @m0ngr31. This is by far my favorite product with Channels. Appreciate you're always taking feedback, questions and adding more to it!

3 Likes

This is really rich. @m0ngr31 's workflow is only a degree different from what Channels does for TVE, and it's stood the test of time. It's an invaluable addition to the ecosystem. @m0ngr31 's contribution should be lauded for keeping the "DVR" more viable in channels, when the devs seem to have moved more towards media collection. It's likely to keep my subscription going for longer, and i doubt I'm alone there.

8 Likes

I appreciate the kind words everyone.

I have a prior engagement this morning so I'll miss the start of Red Zone so if it's still not working it'll be a bit before I'm back on to fix it but hopefully I'll get it figured out

4 Likes

RedZone seems to be working good for me?

2 Likes

Not for me. NFL Network works fine, but not Red Zone.

Also FWIW my linear channels guide isn't working either. The URLs in the setup are fine (used OliveTin One Click to set everything up). Regular non-linear ESPN+ stuff works fine too.

Do you mind DM'ing me your login so I can figure it out?

Curious about this -- so I can adjust in OliveTin if needed. If you look at the URL for the linear channels, does it include station IDs? If not, I believe you'd want to map those channels to specific stations in CDVR Sources.

This is what the M3U looks like:

#EXTM3U
#EXTINF:0 tvg-id="331.eplustv" channel-id="NFL RedZone" channel-number="331" tvg-chno="331" tvg-name="NFLNRZD" tvc-guide-stationid="65025" group-title="EPlusTV", NFL RedZone
http://localhost:8000/channels/331.m3u8

Those logs from Channels look like it's not mapping to the right number or something? Since it's 404ing.

Are you importing the /linear-xmltv.xml as well? Either way though Channels should be able to map what's there from the M3U I think. Unless I set it up wrong

The M3U that my source points to is below. 20430 (NFLN) and 20440 (MLB Big Inning) both work. Just 20431 is the 404.

#EXTM3U
#EXTINF:0 tvg-id="20430.eplustv" channel-id="NFL Network" channel-number="20430" tvg-chno="20430" tvg-name="NFLHD" tvc-guide-stationid="45399" group-title="EPlusTV", NFL Network
http://192.168.1.4:8185/channels/20430.m3u8

#EXTINF:0 tvg-id="20431.eplustv" channel-id="NFL RedZone" channel-number="20431" tvg-chno="20431" tvg-name="NFLNRZD" tvc-guide-stationid="65025" group-title="EPlusTV", NFL RedZone
http://192.168.1.4:8185/channels/20431.m3u8

#EXTINF:0 tvg-id="20440.eplustv" channel-id="MLB Big Inning" channel-number="20440" tvg-chno="20440" tvg-name="MLBTVBI" tvc-guide-stationid="119153" group-title="EPlusTV", MLB Big Inning
http://192.168.1.4:8185/channels/20440.m3u8

Also I am importing the linear-xmltv.xml
image

OK just for fun I created a new volume in portainer and edited my stack to use that (so I needed to log in to everything again but could theoretically go back to before).

Anyway, now Red Zone is working. But the guide data is still not populating (which is less of a big deal. I know when red zone is on :slight_smile: )

Thanks

1 Like

Ok, so I am not quite understanding, Disney killed its apps but they still work on channels but ESPN the ocho can only be recovered from chrome capture?

1 Like

Give it some time. Disney will eventually stop the streams.
If the apps are gone, there is really no reason to keep paying for streams. A few channels users aren't going to make a huge difference.
enjoy the streams while they work and if it continuesk, great if it doesn't, i guess time to move to other alternatives.

1 Like

…because the Ocho isn’t a real linear channel.

1 Like

Actually, I doubt this very much. Disney is just consolidating their platforms.

In there eyes those apps became redundent next to Hulu and Disney+. The latter of which has been rumored to be getting linear channels in the near future.

Their press release expressly sent users to the site to continue to enjoy the feeds and content if you had access.

This is different than Paramount closing their apps and feeds. They were trying to cut costs to make a deal to be purchased happen.

They also do not own a tv provider like Hulu Live to consolidate the linear channels into. Yes they had Paramount+, but they would have had to retool it to support both standalone and tv provider logins, which would have taken too long given the pending sale negotiations.

This is different, until Disney sells the ABC and ESPN family of networks.

2 Likes

It's real if you believe it m0ng31 we believe , or could at least teach us how you scrape your guide data?

image

It would just be funny to have it work :smiley:

Been trying to get started with ESPN+ using eplustv and I have a docker container running but getting refresh token errors when starting - here's the first few lines of the log:

2024-09-24 14:25:34 
2024-09-24 14:25:34 > [email protected] start
2024-09-24 14:25:34 > ts-node index.ts
2024-09-24 14:25:34 
2024-09-24 14:25:36 === E+TV v3.2.1 starting ===
2024-09-24 14:25:37 === ESPN+ Auth ===
2024-09-24 14:25:37 Please open a browser window and go to: https://www.espn.com/watch/activate
2024-09-24 14:25:37 Enter code:  xxxxxx
2024-09-24 14:26:31 Refreshing device token (ESPN+)
2024-09-24 14:26:31 Could not get device token exchange
2024-09-24 14:26:31 Refreshing device refresh token (ESPN+)
2024-09-24 14:26:31 AxiosError: Request failed with status code 400
2024-09-24 14:26:31     at settle (/app/node_modules/axios/lib/core/settle.js:19:12)
2024-09-24 14:26:31     at IncomingMessage.handleStreamEnd (/app/node_modules/axios/lib/adapters/http.js:512:11)
2024-09-24 14:26:31     at IncomingMessage.emit (node:events:529:35)
2024-09-24 14:26:31     at IncomingMessage.emit (node:domain:489:12)
2024-09-24 14:26:31     at endReadableNT (node:internal/streams/readable:1400:12)
2024-09-24 14:26:31     at processTicksAndRejections (node:internal/process/task_queues:82:21) {
2024-09-24 14:26:31   code: 'ERR_BAD_REQUEST',
2024-09-24 14:26:31   config: {
2024-09-24 14:26:31     transitional: {
2024-09-24 14:26:31       silentJSONParsing: true,
2024-09-24 14:26:31       forcedJSONParsing: true,
2024-09-24 14:26:31       clarifyTimeoutError: false
2024-09-24 14:26:31     },
2024-09-24 14:26:31     adapter: [ 'xhr', 'http' ],
2024-09-24 14:26:31     transformRequest: [ [Function: transformRequest] ],
2024-09-24 14:26:31     transformResponse: [ [Function: transformResponse] ],
2024-09-24 14:26:31     timeout: 0,
2024-09-24 14:26:31     xsrfCookieName: 'XSRF-TOKEN',
2024-09-24 14:26:31     xsrfHeaderName: 'X-XSRF-TOKEN',
2024-09-24 14:26:31     maxContentLength: -1,
2024-09-24 14:26:31     maxBodyLength: -1,
2024-09-24 14:26:31     env: { FormData: [Function], Blob: [class Blob] },
2024-09-24 14:26:31     validateStatus: [Function: validateStatus],
2024-09-24 14:26:31     headers: AxiosHeaders {
2024-09-24 14:26:31       Accept: 'application/json',
2024-09-24 14:26:31       'Content-Type': 'application/x-www-form-urlencoded',
2024-09-24 14:26:31       Authorization: 'Bearer xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx',
2024-09-24 14:26:31       'User-Agent': 'axios/1.2.2',
2024-09-24 14:26:31       'Content-Length': '617',
2024-09-24 14:26:31       'Accept-Encoding': 'gzip, compress, deflate, br'
2024-09-24 14:26:31     },

I am able to get a channels.m3u and xmltv.xml files and I'm able to kinda use them - the stream won't play and I get errors in the log like:

2024-09-24 16:51:42 Channel #1 has an active event (The Pat McAfee Show). Going to start the stream.
2024-09-24 16:51:42 Could not get device token exchange
2024-09-24 16:51:42 Could not get device token exchange
2024-09-24 16:51:42 Could not get account grant
2024-09-24 16:51:42 Could not get BAM access token
2024-09-24 16:51:42 Event status:  OVER
2024-09-24 16:51:42 Could not get stream data. Event might be upcoming, ended, or in blackout...
2024-09-24 16:51:42 Failed to parse the stream
2024-09-24 16:51:42 Could not get a playlist for channel #1. Please make sure there is an event scheduled and you have access to it.

Looking at the schedule it's not over and I think this error is happening only because of the token issues above, any suggestions / help?

1 Like