Version 3.00 Released
Total rework of the container to hopefully fix many of the issues of late with improved API calls, error handling and thread handling. Plus improved logging
Version 3.00 Released
Total rework of the container to hopefully fix many of the issues of late with improved API calls, error handling and thread handling. Plus improved logging
Thank you, Thank you, Thank you!
Thanks. Plus more guide data (almost 2 days) now
If the docker only provides up to 2 days of EPG, how is it possible that the Super Bowl is already scheduled for you to record on the Tubi channel?
The non-Gracenote guide data channels only have 2 days EPG.
According to @joagomez, Tubi has mapped the wrong guide data (Gracenote Station ID) to the Dog the Bounty Hunter channel, which is one of the channels with Gracenote guide data. It's mapped to a Fox streaming channel.
I'm using two sources for Tubi, like FrndlyTV
Thank you for the explanation. It was mapped to a FOX linear channel, which has normal EPG.
Makes sense.
Yep, for me it's mapped to
{
"type": "Streaming",
"name": "FNP Chico, CA",
"callSign": "FNPCHIC",
"stationId": "105981",
"bcastLangs": [
"en"
],
"preferredImage": {
"uri": "https://tmsimg.fancybits.co/assets/s103482_ll_h15_aa.png?w=360&h=270",
"height": "270",
"width": "360",
"primary": "true",
"category": "Logo",
"text": "",
"tier": ""
},
"videoQuality": {
"signalType": "Digital",
"videoType": "HDTV",
"truResolution": "HD 720p"
}
}
May be different depending on your location (I'm not in Chico, CA).
The Tubi-for-Channels Project One-Click Action now automatically creates two CDVR Custom Channels sources for you. One containing those channels with Gracenote guide data available, and the other for the channels that need XML data.
More details here:
this should be corrected the next time the channel list gets updated with a manual change I've included.
Will see the following in the log
[INFO] Updating Dog the Bounty Hunter with 150981 from 105981
So obviously a typo in tubi DB
Thanks, no more Super Bowl on Dog the Bounty Hunter channel.
[DVR] Deleting job no longer in the guide: 'Super Bowl LIX' EP054074760001 @ Sun Feb 9 3:30:00PM on ch=[21039] (1739143800-226)
And to answer my own question
Looks like it fetches 26 hours of EPG every 6-7 hours?
New issue with authorization when attempting to sign in without credentials has been identified.
Realease 3.00a has been pushed until issue can be resolved.
As in when you haven't provide a Tubi username and password for the container?
I got this before I filled them in
HTTP: 400: {"code":"INVALID_PARAMS","message":"Request params is invalid"}
No errors w/v3.00 now that I provided them in the compose yaml
Updated and my docker container was restarting constantly.
2025-01-31 23:38:27 [ERROR] Anonymous Credentials Not Functioning. Please use username/password credentials
Edit: Found the variables to send creds at Github. Working now.
https://github.com/jgomez177/tubi-for-channels/pkgs/container/tubi-for-channels
New release 3.00b to revert code when using anonymous credentials.
Using username/password still utilizing updated code.
This error started appearing in the Channels DVR log recently.
[ERR] Failed to fetch station 16964: Invalid station ID: 16964
Appears it comes from the Tubi channel tubi-715945
"Welcome Home" being assigned gracenote station 16964. Not sure if one of these are the correct station, but they're all I could find.
"type": "Streaming","name": "Welcome Home [Sling]","callSign": "WBTV11S","stationId": "169645","uri": "https://tmsimg.fancybits.co/assets/s169645_ll_h15_aa.png?w=360&h=270"
"type": "Streaming","name": "WB TV - Welcome Home","callSign": "WBTV11","stationId": "138037","uri": "https://tmsimg.fancybits.co/assets/s138037_ll_h15_aa.png?w=360&h=270"
Maybe it should be 169645
Looks llike I inadvertently stripped a character from the end of the csv file in my rush to upload 3.00b.
Corrected now
I'm getting zero channels in the m3u as of today - did something change
Same with me. Zero channels today.
I added a username and password per the directions on the container - that fixed the issue
Perhaps its not accepting no username and password anymore
Did you update to the latest release and create a Tubi account ?