I was going to test the Directv app with the Deeplinks but I got busy adding some new functions to the app. I wanted to make a free 5 day Directv to test but I know I can't make my one-track mind stop working on an idea until I get it done. The uuid should be the content_id for Roku, what I'm finding out is this is not as universal as I had hoped. The first two providers I tested, YTTV and Philo, worked great with this format. Others do not.
1 Like
@Bobby_Vaughn ! I just completed my free trial with DirecTV. I have spent the past several days struggling to get ADBTuner to work properly with the DTV app. Unfortunately, the app has some quirks which are making success elusive so far. I have the great minds of @turtletank , @spammedeeper , and @bnhf helping me. We are temporarily hampered by a deep sleep mode which triggers after a while of activity dormancy.
So, today, for a change of pace, I decided to give your Roku Bridge a try. I can say that I now have successfully added and played 46 different deeplinked DirecTV channels with your program! WOO HOO! 
In answer to my own question, the deeplink content id to enter for a channel is simply the uuid portion of the full ADBTuner links I use to set that program up.
I will try setting up a few recordings this evening to do some additional testing. I only have one Roku stick right now. I think that I might have to pick up another.
With the LinkPi ENC5-V2 and a USB HDMI capture device, I have six total Encoder streams. I am thinking that rather than having an array of all the same tuner devices, what may be the best solution for long-term flexibility is to have a wide variety of devices and related programs and apps to use.
I expect that we may get the ADBTuner setup working with DTV, and/or I'm considering giving the ah4c program a try. 
Awesome to hear. Thank you for testing the DirecTV app. It seems more and more apps are trying to make Deeplinking difficult. I am in the middle of trying to add a plugin system with navigation logic for individual apps to better handle required keystrokes for tuning and a more robust key sequence with loops and structured waits. So far, it's been a few successes and a lot of failures. Thanks again.
Our thanks to you, @Bobby_Vaughn , and all of the creative minds and helpful souls here on the Channels Community. The ever changing streaming landscape is hard to keep up with. Channels DVR, and this supportive community, make me happy that we can utilize a variety of devices, apps, and providers and consolidate them all into a single viewing interface. 
My wife and the dogs get to hear me grumble a bit while I'm constantly tinker with stuff. But, when we all hit the couch for the evening, everything we want to watch is right there. 
1 Like
A new bnhf/olivetin:latest (aka bnhf/olivetin:2025.09.03) was pushed this morning with Project One-Click support for this Roku-Channels-Bridge:
As always, this project can be added or completely removed using Actions in Project One-Click. A sample Docker Compose and set of sample env vars can also be found in OliveTin, if you'd like to add the project yourself in Portainer.
If you're not an OliveTin-for-Channels user, and are looking for a recommended Docker Compose, it's available here too:
4 Likes
New Test Branch Available for Roku Channels Bridge
Hi everyone,
I'm excited to announce a new test version of the Roku Channels Bridge with some powerful new features. This version is available on the test branch for those who want to try it out before it is ready for stable release. There will be more channel plugins added soon.
The main branch is still the stable version. This new build is for testing, as the branch implies.
How to Get the Test Version
You can pull the new test image from Docker Hub by adding the :test tag to the image name.
For Docker Run:
docker pull rcvaughn2/roku-ecp-tuner:test
Make sure to stop and remove your existing container before running a new one with the :test image tag.
For Docker Compose:
Simply change the image line in your docker-compose.yml file:
services:
roku-bridge:
image: rcvaughn2/roku-ecp-tuner:test
Then run docker compose up -d to pull the new image and recreate the container.
What's New?
This test version introduces two major features designed to handle difficult apps and create a more seamless viewing experience.
1. Extensible Plugin System
For apps that don't support deep-linking and require complex navigation (like the Fox One app), you can now use simple Python plugins.
-
How it works: The bridge will now automatically load any
_plugin.pyfiles you place in yourconfig/pluginsdirectory, a file upload feature will be available soon. When you add or edit a channel, a new "Plugin Script" dropdown will appear, allowing you to select a plugin to handle the tuning to the guide. You will use the Plugin List Position to reach your desired channel. -
Example: I've included a sample
fox_one_plugin.pyto show how you can navigate to a specific channel based on its position in a list e.g. Big10 is the 5th channel in the guide so 5 would be the number entered in the Plugin List Position field.
2. Blanking Duration (Hide the Tuning Process!)
You can now visually hide the entire tuning process (app loading, keypresses, etc.).
-
How it works: When adding or editing a channel, you'll see a new "Blanking Duration (sec)" field. If you set this to a value (e.g.,
10), the bridge will show a black screen for that number of seconds while it tunes the Roku in the background. - Usage Tip: Since "Blanking Duration" can be set for each channel individually, you can tailor it to each one's specific loading time. For the best experience on a given channel, set its "Blanking Duration" to be slightly longer than that specific channel's total tuning time (including its "Tune Delay" and any key sequence waits).
I've also added helpful tooltips in the UI to explain what the Tune Delay and Blanking Duration settings do.
Please feel free to test this new version out, especially with apps that have been difficult to automate in the past. Let me know how it works for you!
1 Like
Hi everyone! I have been testing the Roku Tuner Bridge with the DirecTV app on Roku Streaming Sticks. The tuning for live viewing and recording has been very reliable.
I do have a problem in that the DirecTV app has a four hour "are you still watching?" pop up, which will close the app if no response is received.
I pad recordings by 30 seconds front and back, to allow for tuning and overruns. So, I often have continuous same channel recordings for several hours. I have had some back to back movies abort at the 4 hour mark.
Is there a way to prevent the pop-up by periodically sending a command to let the app know that we're still there?
Or, is there a way to force a switch to a different tuner between recordings?
That has been the issue with the DTV App on all devices. The only device that allows you to turn that setting off is on the Osprey boxes.
Unfortunately, that seems to be the only answer. I have been trying to avoid purchasing more hardware. (retired and on fixed income)
I will add an option to have a random 3 hour key press to see if that will keep it from asking. Are you using the main or test version?
Cool! I'll be happy to give that a try! I'm on the test version. 
I donât use Roku but can give you suggestions based on testing that I tried on Firesticks.
Key pad down then select.
Brings to Home Screen and back to show. Not ideal as youâll see the results.
Key pad up then the U-turn button
Brings up the recent channels then clears.
I could keep the Firestick DTV app open for over 4 hrs without seeing the 'R U Watching' screen but was never able to duplicate thru Adb tuning. The posts and discussion with bnhf are in the ah4c thread. Of course, it could have been my poor coding skills that caused my failure. (Starting at post 648)
I was wondering if using volume down and/or up could work? Especially if you don't have a TV attached to it. You may not even see any response on the screen or actual volume change...
Nope, you have to interact with the app. Volume interacts with your tv
Maybe a very quick pause/play?
Pause/play may work but I donât remember testing that. I spent hours running to an isolated TV every couple of hours to perform a key series to keep it awake. Those are the key series that I was able to keep it awake. Was never able to replicate with Adb.
I'm gonna try 2 quick selects. One to pause and one to play. It should keep it going or a quick left arrow to rewind a second.
If that doesnât work, I would try the keypad down then select. That is effectively reselecting the channel in the app. You donât lose audio but the picture shrinks while this is occurring. When I was doing my non-automated testing, I avoided that dreaded screen for over 6 hrs during that test. I believe I was doing it every 2-3 hrs.
Good luck!!
I've got several episodes of Gunsmoke recording on TVLand today. It's coming up on the end of the third hour soon. When the commercial break comes on between episodes, I'm going to manually do two quick selects, and also try a down/select combo on the remote. That'll give me an idea what each will look like on the recording. By the end of the fourth episode, I'll know if the still watching prompt comes up, or if the actions stalled it off for a while...
@Bobby_Vaughn , both the double select and down/select were very noticeable on screen. Maybe try a single select. It doesn't actually pause. But it briefly brings up a timeline menu at the screen bottom. If you do double select, you may need a third select. One brings up the bottom menu, the second pauses the show, the third resumes playback.