ESPN+ & FOX Sports with Custom Channels via EPlusTV

Playground Custom Channels
#2103

Just purchased Sunday Ticket for the remainder of the season ($89 through end of day today) and linked it through this wonderful app. Question however, it's too far out to see how the games will get populated in my 200 channel range. Will the games be grouped together, or will they be spread across randomly? And is there an opportunity to create "Linear" channels for Sunday Ticket vs them going into the array of channels?

Thanks.

Sunday Ticket + CDVR + TiviMate + Nvidia Shield equals MultiView Dream.....

2 Likes
#2104

It would get populated throughout the 200 channel range.
I mitigate this by running two instances of EPlusTV - one strictly for NFL set for 15 channels and one for everything else just to keep the NFL games grouped together (there are probably better ways to do this but I went for the quick solution)

#2105

Good suggestion. I'm showing my lack of docker knowledge, I tried to run a second version using the CLI install (prefer that over Portainer) and even though I setup a seperate port number, it treats it as the same as the default install (pulls in my certificates from the 8000 port install).

Here's what I got:

 sudo docker run -p 7999:7999 -v config_dir:/app/config m0ngr31/eplustv
Password:

> eplustv@4.1.0 start
> ts-node -r tsconfig-paths/register index.tsx

=== E+TV v4.1.0 starting ===
Refreshing device token (ESPN+)
Refreshing device refresh token (ESPN+)
Refreshing BAM access token (ESPN+)
Server started on port 8000
=== Getting events ===
Looking for ESPN+ events...
Looking for ESPN events
Looking for FOX Sports events...
Adding event:  The Facility
Looking for NFL events...
=== Done getting events ===
=== Building the schedule ===

====================================================================
===                                                              ===
===   Need to rebuild the schedule because the LINEAR_CHANNELS   ===
===            variable is no longer being used.                 ===
===                                                              ===
====================================================================
===  THIS WILL BREAK SCHEDULED RECORDINGS IN YOUR DVR SOFTWARE   ===
====================================================================

Scheduling 696 entries...
=== Done building the schedule ===

Assuming I am doing something wrong to setup a separate instance?

#2106

In your example, you'd only want to change the host side port. The container side is changed by a specific environment variable, but only in certain situations. Also, you'd want to map a different volume name to the container's data directory, or else you're going to be sharing data between the two containers.

I'd suggest something like this:

sudo docker run -p 7999:8000 -v config_dir2:/app/config m0ngr31/eplustv

EDIT: Though docker via the command line may be easier to copy-and-paste, I think you'd find Portainer is a simpler path to understanding how Docker actually works.

#2107

I have ESPN+ working fine. I can't seem to add BIG+ and see any guide data. I added my Big+ credentials, and it showed a token. I pulled the latest 4.1.3, but I do not have any thing in the stack or environments that mentions Big+. I only have 1 m3u added called espnplus, which i reloaded after adding Big+ to the web interface. Theres not much in this thread regarding Big+.

Does this need added as a separate m3u source and am I missing the stack info...

#2108

What do your logs look like?

#2109

I think I may need an updated yaml and environments for my stack. I saw in @bhnf thread using Bigplus entries. I have none of those - or any specific espn+ login ingo.

TypeError: Cannot read properties of undefined (reading 'refresh_token')
    at EspnHandler.<anonymous> (/app/services/espn-handler.ts:817:35)
    at Generator.next (<anonymous>)
    at /app/services/espn-handler.ts:8:71
    at new Promise (<anonymous>)
    at __awaiter (/app/services/espn-handler.ts:4:12)
    at EspnHandler.refreshAuth (/app/services/espn-handler.ts:814:50)
    at EspnHandler.<anonymous> (/app/services/espn-handler.ts:832:20)
    at Generator.next (<anonymous>)
    at /app/services/espn-handler.ts:8:71
    at new Promise (<anonymous>)
Could not get auth refresh token
Refreshing device token (ESPN+)
Refreshing device refresh token (ESPN+)
Refreshing BAM access token (ESPN+)
Could not get account grant
TypeError: Cannot read properties of undefined (reading 'id_token')
    at EspnHandler.<anonymous> (/app/services/espn-handler.ts:1124:35)
    at Generator.next (<anonymous>)
    at fulfilled (/app/services/espn-handler.ts:5:58)
Could not get BAM access token
TypeError: Cannot read properties of undefined (reading 'assertion')
    at EspnHandler.<anonymous> (/app/services/espn-handler.ts:1193:46)
    at Generator.next (<anonymous>)
    at fulfilled (/app/services/espn-handler.ts:5:58)
#2110

I have successfully added the Docker Container for ESPN+. It seems to work. Can anyone give me directions as how to add NFL using Amazon Prime and Peacock? I don't have a subscription for the NFL.

#2111

You don't have to have a subscription, but you do need to create a free NFL.com account

1 Like
#2112

Although this was for when you still had to do it command line and not the super easy user interface, this still applies:

Otherwise, it's all just checkboxes in the EPlusTV interface. Nothing to it!

image
image1487×685 59.9 KB

2 Likes
#2113

Figured out the issue, removing my novel of a post.

1 Like
#2114

FYI for everyone else:

2 Likes
#2116

So NFL Network as a linear channel via NFL+ was working for me earlier today at the linear-channels.m3u endpoint, but then it stopped around the start time of the second game.

EDITED to remove unrelated issue, subsequently fixed.

#2117

The only thing that I can think of that would cause the first issue would be a messed up JWT token that would break the check on the linear side... As far as the second issue, I have seen that happen randomly, and restarting the container usually fixes it. Some weird issue with the NFL API I think

1 Like
#2118

Thanks. I did wonder if my API requests were just getting denied, especially now that the container remains stuck on "Looking for NFL events..." after a complete rebuild, with entries.db and schedule.db empty (zero bytes). Is there any debug mode for the container? I guess I don't really need it for games after tonight anyway, so I can just nuke it for the offseason.

#2119

This happened to me, too, in addition to to the TNF replay on Friday at midnight. I had checked NFLN earlier in the day and it was working, but when I went to see the recordings they had failed. Restarting the container allowed the connection again, but it was too late for the Saturday games. Just seems like NFLN gives up after a while, but I'm not sure why and when. Didn't happen for weeks, then happened twice in three days (actually three in four days, but I thought I was having local issues, though maybe not).

#2120

If the linear feed fails again, before you do anything, can you send me a DM with all the NFL tokens?

#2121

Still not sure about the original linear feed failure, but I figured out why my subsequent container rebuild wasn't pulling any events: I had just cancelled my plan's renewal, although the plan still works at the web site up to the expiration date.

I just opened a pull request with a fix. Feel free to DM me if you need more info.

1 Like
#2122

Unfortunately the Disney+ feeds of the ESPN content is all using Playready DRM :frowning_face:

1 Like
#2123

I have version 4.1.0 installed, how can I update to the new version? I'm on Ubuntu 20.