A few people have asked for a Windows Tubi Bridge for Channels DVR. It's nothing special, but it does work. It defaults to using mostly Gracenotes for guide data with an option to use only the scraper and provided epg for guide data. If you are on the latest Pre-release of Channels DVR, you can use the provided M3U and EPG files for guide data. If you are on the current stable release of Channels DVR, do not add the epg file to the Custom Channel as it will cause issues with the included Gracenotes ID's in the M3U file.
Will it continue to work once there's a new stable release in the future? I also assume you can run it alongside the Pluto one as a separate instance?
This is a completely separate application from the Pluto one. It's working on the pre-release which allows for mixed gracenotes and epg data.
Ok, I've installed the Tubi bridge now on port 7778 (Pluto is on 7777), and we'll see how it works. I noticed some channels have very short epg though. But, it appears to be working fine.
If my server reboots, will it restart the Tubi bridge automatically?
Thanks Bobby. -- am on vacation from my server for two weeks. Will try it out when I get back. Any TUBI integration is good integration to CHANNELS.
Yes, it will restart and run as a service, you should not have to touch it. The GitHub Readme explains this as well as commands to manually stop and start the service:
Managing the Service
- The bridge starts automatically with Windows under the service name
TubiBridge. - To start or stop the service manually, open Command Prompt (Run as Administrator) and run:
- Stop:
sc stop TubiBridge - Start:
sc start TubiBridge
- Stop:
- To uninstall, use Windows Settings > Apps > Installed apps and select Tubi Bridge to remove the service, files, and firewall rules cleanly.
If you find a need to restart it without doing a stop and start, just use Powershell
Restart-Service -Name TubiBridge
Hope it works well for you. It is basic and serves the main purpose of watching Tubi.
My Windows 11 based server rebooted last night due to yet another Microsoft update, and the Tubi bridge restarted like it should BUT, there's no longer anything in the playlist. The .m3u generated is completely blank.
Did Tubi change something at the same time?
I'll look into it
It is still working for me. Let's see if a restart fixes it for you. Open Windows Command Prompt as Admin and we will do a stop and start of the Tubi app. Once you get the Command Prompt opened as admin, run
sc stop TubiBridge
and then run
sc start TubiBridge
Give it a minute to load and see if that fixes it.
Ok, the above commands didn't seem to work for me, even starting under admin. So, I killed the instance in Task Manager, then restarted it by double-clicking tubi-bridge.exe in its install folder. It restarted on a different higher port, but it is working now. Until possibly another server reboot happens again anyway.
Now, it actually started and was actually running after the server reboot (at least the admin screen came up properly in the browser) but, it just was empty of channels
I am getting the following error trying to setup the Tubi Bridge:
Failed to load M3U:No Channels found in M3U
I am running W11 with most recent updates installed
Is this the first time running it?
I will look into a possible race condition that might be causing the issue.
It looks like Tubi is requiring user credentials. I will work on an update this evening.
For me, it a first time install.
The message is when I am trying to setup a custom channel and it won't let me.
I'm going to update the script and add a Tubi log in to it. I should have it done by tomorrow.
That's awesome Bobby! I certainly appreciate all you do on these projects, and I know there could be glitches now and again. That's just the way it is.
v1.0.1 released to address Tubi changes that now requires authenticating with a Tubi user account. You will need a Username and Password for Tubi. To upgrade, just run the installer and enter your Tubi Username(Email) and Password and click Save/Refresh on the Dashboard. Give it a minute to load the channels and guide data .
That went just as easy as you said. It swapped versions, kept the port I was using, and I entered my credentials and did the save & refresh. Waited a few minutes, and tried a channel and it worked fine.
Thanks!