From the article:
Tubi’s stream will be available in 4K
They are supposed to provide 4K streams but I have not seen a 4K stream in Tubi to date (nor have I really looked) so not sure if the docker will provide 4K streams. Something that will have to seen as the date comes closer and if they have other 4k streams to test with
You need to create a Tubi account to watch it.
Sounds like you'll need to sign in to that account.
Correction, January 15th: A previous version of the article stated that you will not need an account to stream Super Bowl LIX on Tubi. You do not need an account to watch Tubi, but Tubi spokesperson Seana Sullivan told The Verge after publication that an account will be required to stream the Super Bowl. This article also previously implied that Super Bowl LVII was only available to stream on paid streaming services; Fox also made it available for free on the Fox Sports app.
Added the option to use email credentials for Tubi into the docker for the SB
That's a good question. I haven't seen any mention of the sound quality, only that it will be in 4K.
I think it would be reasonable to expect the sound to be 5.1 if they bother to go through the trouble of providing a good quality 4K picture.
No idea. 
Hi, I just noticed that my Tubi source M3U lost all of it's channels today. Does anyone know if there is a problem with the current docker container? FWIW, the Tubi app and website appear to be working.
v2.01 working here
I was about to say I'm not having this issue, but I checked, and it turns out I am (using v2.01). It looks like things were okay this morning...
2025-01-23 09:53:18 [INFO] Updating channel id list
2025-01-23 09:53:19 [INFO] Close the Signin API session
2025-01-23 09:53:19 [INFO] Number of streams available: 173
2025-01-23 09:53:19 [INFO] Retriving EPG Data
2025-01-23 09:53:19 [INFO] EPG API Call
2025-01-23 09:53:22 [INFO] EPG API Call
2025-01-23 09:53:24 [INFO] Channels: Available EPG data: 173
But not so much now (forced a restart to be sure)...
2025-01-23 16:50:15 [INFO] ⇨ http server started on [::]:7777
2025-01-23 16:50:31 [INFO] Updating channel id list
2025-01-23 16:50:31 [INFO] Close the Signin API session
2025-01-23 16:50:31 [INFO] Number of streams available: 0
2025-01-23 16:50:31 [INFO] Retriving EPG Data
2025-01-23 16:50:31 [INFO] Initialize channel_list
2025-01-23 16:50:31 [INFO] Close the Signin API session
2025-01-23 16:50:31 [INFO] Number of streams available: 0
2025-01-23 16:50:31 [INFO] Channels: Available EPG data: 0
Open the m3u or xml files and you'll see they are empty, save the base stuff.
Might be a temporary hiccup from Tubi or a change in their API call, will have to wait on @joagomez for the answer.
For me, it seems that it pooped out within the last hour or so. I tried restarting the container, too. Still, nuthin'.
Yep, both the m3u and xml are empty.
Not sure if this is normal for the container log
2025-01-23T17:49:03.956171557Z [INFO] Updating channel id list
2025-01-23T17:49:03.957101007Z [INFO] Update Token via API Call
2025-01-23T17:49:03.957287461Z [INFO] Update token_sessionAt
2025-01-23T17:49:04.701548105Z [INFO] Close the Signin API session
2025-01-23T17:49:04.702800031Z HTTP: 400: {"code":"INVALID_PARAMS","message":"Request params is invalid"}
2025-01-23T17:49:05.210131635Z [INFO] Close the Signin API session
2025-01-23T17:49:05.669226294Z [INFO] Number of streams available: 176
2025-01-23T17:49:05.680355425Z [INFO] Retriving EPG Data
2025-01-23T17:49:05.681198249Z [INFO] EPG API Call
2025-01-23T17:49:09.303884774Z [INFO] EPG API Call
2025-01-23T17:49:10.459290651Z [INFO] Channels: Available EPG data: 176
2025-01-23T17:49:10.782899453Z [INFO] Updating channel id list
2025-01-23T17:49:10.783135661Z [INFO] Update Token via API Call
2025-01-23T17:49:10.783258384Z [INFO] Update token_sessionAt
2025-01-23T17:49:11.018768427Z [INFO] Close the Signin API session
2025-01-23T17:49:11.019302093Z HTTP: 400: {"code":"INVALID_PARAMS","message":"Request params is invalid"}
2025-01-23T17:49:11.504839226Z [INFO] Close the Signin API session
2025-01-23T17:49:11.937896709Z [INFO] Number of streams available: 176
2025-01-23T17:49:11.940306319Z [INFO] Retriving EPG Data
2025-01-23T17:49:11.941087652Z [INFO] EPG API Call
2025-01-23T17:49:15.250792829Z [INFO] EPG API Call
2025-01-23T17:49:16.401198936Z [INFO] Channels: Available EPG data: 176
2025-01-23T17:49:16.553873710Z [INFO] Running EPG
2025-01-23T17:49:20.201964234Z [INFO] Write XML
2025-01-23T17:49:20.998163696Z [INFO] End EPG
Now I'm seeing 0 streams available in the container log
2025-01-23T22:10:13.737093514Z [INFO] Updating channel id list
2025-01-23T22:10:13.750182985Z [INFO] Update Token via API Call
2025-01-23T22:10:13.750404656Z [INFO] Update token_sessionAt
2025-01-23T22:10:14.707535323Z [INFO] Close the Signin API session
2025-01-23T22:10:14.708451566Z HTTP: 400: {"code":"INVALID_PARAMS","message":"Request params is invalid"}
2025-01-23T22:10:14.829407538Z [INFO] Close the Signin API session
2025-01-23T22:10:14.946690740Z [INFO] Number of streams available: 0
2025-01-23T22:10:14.948888772Z [INFO] Retriving EPG Data
2025-01-23T22:10:14.949122081Z [INFO] Initialize channel_list
2025-01-23T22:10:14.949237379Z [INFO] Update Token via API Call
2025-01-23T22:10:14.949344718Z [INFO] Update token_sessionAt
2025-01-23T22:10:15.126371324Z [INFO] Close the Signin API session
2025-01-23T22:10:15.126698473Z HTTP: 400: {"code":"INVALID_PARAMS","message":"Request params is invalid"}
2025-01-23T22:10:15.263893093Z [INFO] Close the Signin API session
2025-01-23T22:10:15.279909702Z [INFO] Number of streams available: 0
2025-01-23T22:10:15.377287101Z [INFO] Channels: Available EPG data: 0
2025-01-23T22:10:31.993689177Z [INFO] Updating channel id list
2025-01-23T22:10:31.994645240Z [INFO] Update Token via API Call
2025-01-23T22:10:31.994880091Z [INFO] Update token_sessionAt
2025-01-23T22:10:32.239553609Z [INFO] Close the Signin API session
2025-01-23T22:10:32.239766209Z HTTP: 400: {"code":"INVALID_PARAMS","message":"Request params is invalid"}
2025-01-23T22:10:32.365716579Z [INFO] Close the Signin API session
2025-01-23T22:10:32.381364592Z [INFO] Number of streams available: 0
2025-01-23T22:10:32.383400365Z [INFO] Retriving EPG Data
2025-01-23T22:10:32.383612058Z [INFO] Initialize channel_list
2025-01-23T22:10:32.383890829Z [INFO] Update Token via API Call
2025-01-23T22:10:32.384014833Z [INFO] Update token_sessionAt
2025-01-23T22:10:32.613693070Z [INFO] Close the Signin API session
2025-01-23T22:10:32.614043948Z HTTP: 400: {"code":"INVALID_PARAMS","message":"Request params is invalid"}
2025-01-23T22:10:32.729091778Z [INFO] Close the Signin API session
2025-01-23T22:10:32.746412157Z [INFO] Number of streams available: 0
2025-01-23T22:10:32.748405635Z [INFO] Channels: Available EPG data: 0
2025-01-23T22:11:48.698039732Z [INFO] Running EPG
2025-01-23T22:11:48.698965127Z [INFO] Retriving EPG Data
2025-01-23T22:11:48.699143242Z [INFO] Initialize channel_list
2025-01-23T22:11:48.699242548Z [INFO] Update Token via API Call
2025-01-23T22:11:48.699348895Z [INFO] Update token_sessionAt
2025-01-23T22:11:48.922028323Z [INFO] Close the Signin API session
2025-01-23T22:11:48.922303643Z HTTP: 400: {"code":"INVALID_PARAMS","message":"Request params is invalid"}
2025-01-23T22:11:49.064950195Z [INFO] Close the Signin API session
2025-01-23T22:11:49.081012622Z [INFO] Number of streams available: 0
2025-01-23T22:11:49.082965774Z [INFO] End Read EPG
2025-01-23T22:11:49.161928841Z [INFO] Write XML
2025-01-23T22:11:49.202191589Z [INFO] End EPG
My guide is also, but check the m3u, xml and container log.
Yeah was doing that as you posted ... no good
2025/01/23 14:45:17.804746 [ERR] Failed to start stream for ch3008: M3U: Could not fetch playlist from 192.168.50.83:7778: GET: http://192.168.50.83:7778/tubi/watch/400000099: 500 INTERNAL SERVER ERROR
2025/01/23 14:45:17.825656 [HLS] Couldn't generate stream playlist for ch3008-dANY-ip192.168.50.186: M3U: Could not fetch playlist from 192.168.50.83:7778: GET: http://192.168.50.83:7778/tubi/watch/400000099: 500 INTERNAL SERVER ERROR
2025/01/23 14:45:17.825953 [HLS] Stopping transcoder session ch3008-dANY-ip192.168.50.186 (out=0s finished=false first_seq=0 last_seq=-1)
[INFO] Updating channel id list
[INFO] Close the Signin API session
[INFO] Number of streams available: 0
[INFO] Retriving EPG Data
[INFO] Initialize channel_list
[INFO] Close the Signin API session
[INFO] Number of streams available: 0
[INFO] Channels: Available EPG data: 0
[INFO] Updating channel id list
[INFO] Close the Signin API session
[INFO] Number of streams available: 0
[INFO] Retriving EPG Data
[INFO] Initialize channel_list
[INFO] Close the Signin API session
[INFO] Number of streams available: 0
[INFO] Channels: Available EPG data: 0
Just tried to install from One Click and got the error message
"{"error":"invalid source url: no channels found in m3u"}"
That makes sense. Channels DVR won't accept a source with an empty m3u. When/if we all get the docker container generating the channel list properly again, the "One Click" installation should work.
It appears something has changed in the last couple of hours will need to investigate
Receiving the following in one of their API calls
"alert": "Tubi is experiencing technical issues. You're on a degraded experience now.",
will need to wait for this to clear to see if the APIs have changed or if this is a temporary issue