You actually can use the Ospreys in the same ADBT instance. One of the recent dev builds allows you to have an M3U per app.
You'd also need to change the container name to adbtuner2, which I haven't allowed for in Project One-Click. Do you feel comfortable spinning up a stack in Portainer? You could copy and paste from the existing stack or use the sample Docker Compose for ADBTuner in Projerct One-Click.
EDIT: Or, do what @spammedeeper is suggesting. 
EDIT2: If you decide to spin-up a second container, I believe these are the changes you'd need to make to the Docker Compose:
services:
adbtuner:
image: turtletank99/adbtuner:${TAG}
container_name: adbtuner2
dns_search: ${DOMAIN} # Change to the name of your LAN's domain, which is usually local or localdomain
init: true
ports:
- ${HOST_PORT}:5592 # Use the same port number the container is using, or optionally change it if the port is already in use on your host
volumes:
- adbtuner2:/app/.config
restart: unless-stopped
volumes:
adbtuner2:
name: ${HOST_VOLUME}
And then, you were on the right track with the env var changes you were proposing...
I must have missed that post. Thanks
In my main docker I have a mix of Ospreys and Onn boxes. I use the unique package/App M3U to add individual sources to Channels. This is great as it lets me set priority for certain apps, all while using one docker.
In practice this has allowed me to have separated DirecTV Onn source and DirecTV Osprey Source. As the Osprey is faster to tune, I set the Osprey as primary source on my Apple TV for faster channel flips (and recently multi view tuning). To keep the ospreys available for live TV watching, I set the sever to use Onns for recording. Don’t care if the tuning is slower for recoding as I don’t see it.
This setup has worked really well last few weeks.
My Mac-Mini-M2 updated the OS to the latest version Tahoe 26.0 yesterday.
Docker Desktop also had a waiting update to version 4.46.0 (204649) that I installed. After that I noticed that the ADBTuner tuners were displaying the Endpoint/Android Connection Failed error on all three of my Osprey tuners. After messing with it for several hours I decided to delete everything except Docker Desktop and start over. I reinstalled OliveTin and from there I deployed Portainer, Watchtower and ADBTuner. I set up my three Osprey devices and also one of the Onn 4k Pros I had available. All four devices are showing the Connection Failed error for Endpoint and Android. I can ping all of the devices and I can open a stream in VLC using the Endpoint URL for all devices. I stopped and started the adbtuner container and I see this in Portainer - adbtuner log:
INFO: Application startup complete.
INFO: Uvicorn running on http://0.0.0.0:5593 (Press CTRL+C to quit)
2025-09-16 20:59:09.639 - lib.adb - [Errno 111] Connection refused
2025-09-16 20:59:09.639 - lib.adb - ADB: Connection failed.
2025-09-16 20:59:09.639 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2025-09-16 20:59:09.639 - lib.adb - Failed to retrieve current configuration. Will not update Android device configuration.
2025-09-16 20:59:09.639 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2025-09-16 20:59:09.639 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2025-09-16 20:59:09.667 - lib.adb - [Errno 111] Connection refused
2025-09-16 20:59:09.667 - lib.adb - ADB: Connection failed.
2025-09-16 20:59:09.667 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2025-09-16 20:59:09.667 - lib.adb - Failed to retrieve current configuration. Will not update Android device configuration.
2025-09-16 20:59:09.667 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2025-09-16 20:59:09.667 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2025-09-16 20:59:09.689 - lib.adb - [Errno 111] Connection refused
2025-09-16 20:59:09.689 - lib.adb - ADB: Connection failed.
2025-09-16 20:59:09.689 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2025-09-16 20:59:09.689 - lib.adb - Failed to retrieve current configuration. Will not update Android device configuration.
2025-09-16 20:59:09.689 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2025-09-16 20:59:09.689 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2025-09-16 20:59:09.707 - lib.adb - [Errno 111] Connection refused
2025-09-16 20:59:09.707 - lib.adb - ADB: Connection failed.
2025-09-16 20:59:09.707 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2025-09-16 20:59:09.707 - lib.adb - Failed to retrieve current configuration. Will not update Android device configuration.
2025-09-16 20:59:09.707 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2025-09-16 20:59:09.707 - lib.adb - ADB: Error while running command. Check for approval popup on device.
None of the devices are displaying an ADB approval popup. I then went into a couple of the Osprey's Settings and revoked ADB permissions. I still don't get an ADB approval popup when I do a Refresh Status from ADBTuner.
What should I try next?
Maybe MacOS network permissions? These apparently get reset now on every update:
Thanks for the link. I found in Settings-> Privacy & Security-> Local Network an entry for Docker that was turned off. I enabled Docker and then restarted Mac OS just to make sure it took effect and ADBTuner can once again access my streaming devices. Many thanks and I hope this will save someone a little troubleshooting if they encounter the same issue.
3 Likes
Dood to hear you found the issue and got it all working on new macos. I've got too much going on right now to be the brave one to test this out.
When I try to play any channel on the nbc app through adb tuner using my firestick on my hdmi encoder the channels stream with the lights dimmed, there was previously a post that had a solution which was to download version 9.9.1 of the nbc app and it would work, but that version no longer works because it wont let you login with your provider much less stream anything, is there any way to fix this? THANK YOU!
You will need a development build of ADBTuner and a custom config, but this should help.
thank you so much for yout post on installing NBC App Channels, working around the Dim Video Challenge, I currently am trying to do the same but beczuse I am new at this I only know how to install adbtuner by first installignn portainer and docker desktop and then running the following command on cmd prompt:"docker run -d --init -p 5592:5592 --name adbtuner -v adbtuner_config:/app/.config turtletank99/adbtuner" I have never installed it the way you said, is there any guide that you can give me or send me to that will show me how to do so? THANK YOU!
Just want to report that Iptv simple addon for Kodi and adbtuner now works great after i enter "mime type" video/mp2t in iptv Simple settings and enable ffmpeg reconnect and inputstream.adaptive
video/mp2t
Channel start is 3-4s and channel change with up/down 5s.
Without mime type setting channel change takes along time as Kodi uses MIME types to understand the format of files and streams to correctly display or play them.
You have to find the apk, open it with apktool, and look inside the AndroidManifest.xml to see which links are supported.
I see:
<activity android:configChanges="keyboardHidden|screenSize" android:exported="false" android:launchMode="singleTask" android:name="com.nesn.nesnplayer.ui.main.MainActivity" android:screenOrientation="behind" android:theme="@style/AppTheme.NoActionBar">
<intent-filter>
<action android:name="android.intent.action.SEND"/>
<category android:name="android.intent.category.DEFAULT"/>
<data android:mimeType="text/plain"/>
</intent-filter>
<intent-filter>
<action android:name="android.intent.action.VIEW"/>
<category android:name="android.intent.category.DEFAULT"/>
<category android:name="android.intent.category.BROWSABLE"/>
<data android:scheme="com.nesn.nesnplayer"/>
</intent-filter>
</activity>
which means com.nesn.nesnplayer:// would launch com.nesn.nesnplayer.ui.main.MainActivity.
But its not clear what more you use to go directly to a live channel. It requires experimentation and luck. Sometimes the same link from the webbrowser will work if the app is configured for it.
There is another section that does seem to support urls that start with nesn.com/watch:
<activity android:configChanges="orientation|screenSize" android:exported="true" android:name="com.nesn.nesnplayer.ui.splash.SplashActivity" android:screenOrientation="behind" android:theme="@style/AppTheme.NoActionBar">
<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
<intent-filter android:autoVerify="true">
<action android:name="android.intent.action.VIEW"/>
<category android:name="android.intent.category.DEFAULT"/>
<category android:name="android.intent.category.BROWSABLE"/>
<data android:scheme="http"/>
<data android:scheme="https"/>
<data android:host="nesn.com"/>
<data android:host="*.nesn.com"/>
<data android:pathPrefix="/watch"/>
</intent-filter>
1 Like
I can give you some advice to get started, but you will need to experiment.
1. You can pull the experimental development builds by using this for repository.
turtletank99/adbtuner:development
This will pull an experimental, developer version.
2. After you load the dev build, go to your adbtuner web interface, with /configurations
http://[your IP address]:5592/configurations
3. Create a new Config (button at top), leave the top section by giving it a name and leaving your UUID, then copy in and replace just the info I provided in last post.
4. Go back to your channel with NBC, change the config to use the custom one you built. You may need to refresh docker or webpage to see it.
From there you will just need to play with settings. Every config is different, but what I provided will get you started.
One last thing, I'm happy to assist where I can, but there is no reason to ping me so many times for the same topic. If you need simple tuning, use standard channels tuning for YouTube TV.
Thank you so much, I'm sorry about the pinging so many times, its just that I had some spelling and punctuation errors in the previous messages I sent you, but I completely understand, once again thank you!
I was able to install it and I pasted the configurations like you told me and everything seemed to be going well but when I try to run the channel the app just doesnt launch at all, as a matter of fact nothing happens, I guess I may be doing something wrong but I have tried to do it with different devices (both an Onn and a Firestick) and I have uninstalled and reinstalled it several times but its still the same way. And as soon as I revert back to the default configurations the app opens successfully but of course with the dim lights, maybe you may know of a fix or if you have any suggestions it would be much appreciated. THANK YOU!
I have been using this for a while, and overall it is working great, but I have a feature request. Not sure if it has been asked before.
Would it be possible to add a button on each 'Tuner' to send an ADB reboot command for the google devices (or FireTV)? My devices sometimes just get stuck, and they are remote (across town in my office). If I could reboot them from the web interface, it would save me a trip!
That would be good for most situations, however powering your devices with a managed PoE switch is really the ultimate, as it provides a power-cycle reboot if ever needed. I'm an ocean away from my devices a fair bit, and this gives me a lot of confidence that I can deal with whatever. My encoders are powered the same way.
2 Likes
That's a great idea! Another possibility is to plug your tuners into smart switches, a smart power strip, or a basic power strip connected to a smart switch.
These are wireless devices (Chromecast and FireTV). I know of no way to use PoE to power them.
I could use a smart plug I suppose.