What's the latest on Xfinity Stream on the Fire 4K? I have it set up as I believe your most recent update shows but no success. I cannot get it to get past the three loading dots on any channel (with or without compatibility mode).
You need Compatibility mode no way around it. Are you sure that is the correct URL ?
1 Like
Yes, have copied a few urls including ubiquitous non-locals like QVC/CNN with the same result. Only changed the show title to the channel name in url.
Are you using it locally from the same place that has Comcast Internet ?
Different network, but same locale. All channels work when I manually tune.
It should work but one thing I do know is that you must use the Comcast ISP locally to access the main broadcast channels.
Yep
I got this
My opinion is just drop TV from Optimum and go with something like YTTV or Fubo (Fubo might have better offerings for SNY+MSG)
I don't think there is much info about using the Optimum stream device or linking the Apple TV Optimum app to an encoder. However, there is a ton of info about how to do it with YTTV. You'll save yourself a headache and some cash going with the most popular and talked about option.
If you are being incentivized into switching into their fiber offerings, then your coaxial network won't even be used for their TV service, becuase that will be delivered via fiber. You are basically switching TV providers despite being billed by the same company.
If you have to stick with optimum for TV service, maybe consider subscribing to their DVR service, it's not much more then paying for cable TV and this server subscription.
1 Like
Is there any chance you could show exactly how you set up ah4c for the NBC app? You mentioned writing your own scripts and modifying the existing scripts that came with the original HDMI for channels code. I currently have ADBTuner running through Docker on unbuntu server on a mini pc. The ah4c setup seems a bit confusing to me, but if someone is able to post a set of step-by-step instructions for an exact setup for the NBC app, I think I would be able to figure it out. Thank you for your time!
I'm also wondering how exactly you would set up this script in Home Assistant and have automation. I have Home Assistant set up and running as a docker container but I've never used Home Assistant before so I really don't know where to begin. But it seems like what one needs to do here is have a script that runs a set of commands from a remote control. Then, every time the NBC app launches, that script would automatically kick in?
My Chromecast with Google TV will no longer authorize ADB via ethernet does authorize over WFI ... I guess it seems like I finally hit the same problem with the ONN devices ... I tried everything I know but it just does not work anymore. Connected Via ethernet gets no popup to allow. USB Debugging is on which should allow ethernet.
2024-09-25 19:43:49.181 - uvicorn.access - 172.26.0.1:33952 - "GET /admin/tuner/metadata?_=1727293422174 HTTP/1.1" 200
2024-09-25 19:43:52.681 - lib.adb - ADB: Connecting to device (attempt 1).
2024-09-25 19:43:56.499 - lib.adb - [Errno 111] Connection refused
2024-09-25 19:43:56.499 - lib.adb - ADB: Connection failed.
2024-09-25 19:43:56.499 - lib.adb - ADB: 192.168.50.243 - settings list global
2024-09-25 19:43:56.499 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:43:56.500 - lib.adb - Failed to retrieve current configuration. Will not update Android device configuration.
2024-09-25 19:43:56.500 - lib.adb - ADB: 192.168.50.243 - dumpsys display
2024-09-25 19:43:56.500 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:43:56.500 - lib.adb - ADB: 192.168.50.243 - getprop ro.build.version.release
2024-09-25 19:43:56.500 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:43:56.659 - httpx - HTTP Request: GET http://192.168.50.242:8086/8.ts "HTTP/1.1 200 OK"
2024-09-25 19:43:56.720 - uvicorn.access - 172.26.0.1:33952 - "GET /admin/tuner/metadata?_=1727293422176 HTTP/1.1" 200
2024-09-25 19:43:57.660 - lib.adb - ADB: Connecting to device (attempt 1).
2024-09-25 19:44:01.052 - lib.adb - [Errno 111] Connection refused
2024-09-25 19:44:01.053 - lib.adb - ADB: Connection failed.
2024-09-25 19:44:01.053 - lib.adb - ADB: 192.168.50.243 - settings list global
2024-09-25 19:44:01.053 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:44:01.053 - lib.adb - Failed to retrieve current configuration. Will not update Android device configuration.
2024-09-25 19:44:01.054 - lib.adb - ADB: 192.168.50.243 - dumpsys display
2024-09-25 19:44:01.054 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:44:01.054 - lib.adb - ADB: 192.168.50.243 - getprop ro.build.version.release
2024-09-25 19:44:01.054 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:44:01.187 - httpx - HTTP Request: GET http://192.168.50.242:8086/8.ts "HTTP/1.1 200 OK"
2024-09-25 19:44:01.258 - uvicorn.access - 172.26.0.1:33952 - "GET /admin/tuner/metadata?_=1727293422179 HTTP/1.1" 200
2024-09-25 19:44:02.118 - lib.adb - ADB: Connecting to device (attempt 1).
2024-09-25 19:44:05.102 - lib.adb - [Errno 111] Connection refused
2024-09-25 19:44:05.102 - lib.adb - ADB: Connection failed.
2024-09-25 19:44:05.102 - lib.adb - ADB: 192.168.50.243 - settings list global
2024-09-25 19:44:05.102 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:44:05.103 - lib.adb - Failed to retrieve current configuration. Will not update Android device configuration.
2024-09-25 19:44:05.103 - lib.adb - ADB: 192.168.50.243 - dumpsys display
2024-09-25 19:44:05.103 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:44:05.103 - lib.adb - ADB: 192.168.50.243 - getprop ro.build.version.release
2024-09-25 19:44:05.103 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:44:05.248 - httpx - HTTP Request: GET http://192.168.50.242:8086/8.ts "HTTP/1.1 200 OK"
2024-09-25 19:44:05.292 - uvicorn.access - 172.26.0.1:33952 - "GET /admin/tuner/metadata?_=1727293422182 HTTP/1.1" 200
2024-09-25 19:44:27.328 - lib.adb - ADB: Connecting to device (attempt 1).
2024-09-25 19:44:30.530 - lib.adb - ADB: Connecting to device (attempt 1).
2024-09-25 19:44:32.334 - lib.adb - timed out
2024-09-25 19:44:32.335 - lib.adb - ADB: Connection error. Device may be waking up. Trying again.
2024-09-25 19:44:33.336 - lib.adb - ADB: 192.168.50.222 - settings list global
2024-09-25 19:44:33.337 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:44:33.337 - lib.adb - Failed to retrieve current configuration. Will not update Android device configuration.
2024-09-25 19:44:35.495 - lib.adb - ADB: Connecting to device (attempt 1).
2024-09-25 19:44:35.535 - lib.adb - timed out
2024-09-25 19:44:35.536 - lib.adb - ADB: Connection error. Device may be waking up. Trying again.
2024-09-25 19:44:36.537 - lib.adb - ADB: 192.168.50.222 - settings list global
2024-09-25 19:44:36.537 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:44:36.537 - lib.adb - Failed to retrieve current configuration. Will not update Android device configuration.
2024-09-25 19:44:37.150 - lib.adb - ADB: Connecting to device (attempt 1).
2024-09-25 19:44:40.498 - lib.adb - timed out
2024-09-25 19:44:40.498 - lib.adb - ADB: Connection error. Device may be waking up. Trying again.
2024-09-25 19:44:41.499 - lib.adb - ADB: 192.168.50.222 - settings list global
2024-09-25 19:44:41.499 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:44:41.499 - lib.adb - Failed to retrieve current configuration. Will not update Android device configuration.
2024-09-25 19:44:41.500 - uvicorn.access - 172.26.0.1:32982 - "POST /admin/tuner/1 HTTP/1.1" 303
2024-09-25 19:44:41.535 - uvicorn.access - 172.26.0.1:32982 - "GET / HTTP/1.1" 200
2024-09-25 19:44:41.612 - uvicorn.access - 172.26.0.1:33250 - "GET /js/main.js?t=1727293481 HTTP/1.1" 200
2024-09-25 19:44:41.612 - uvicorn.access - 172.26.0.1:32982 - "GET /css/style.css?t=1727293481 HTTP/1.1" 200
2024-09-25 19:44:41.662 - lib.adb - ADB: Connecting to device (attempt 1).
2024-09-25 19:44:41.667 - lib.adb - ADB: Connecting to device (attempt 1).
2024-09-25 19:44:42.156 - lib.adb - timed out
2024-09-25 19:44:42.157 - lib.adb - ADB: Connection error. Device may be waking up. Trying again.
2024-09-25 19:44:43.158 - lib.adb - ADB: 192.168.50.222 - settings list global
2024-09-25 19:44:43.158 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:44:43.158 - lib.adb - Failed to retrieve current configuration. Will not update Android device configuration.
2024-09-25 19:44:43.159 - lib.adb - ADB: 192.168.50.222 - dumpsys display
2024-09-25 19:44:43.159 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:44:43.159 - lib.adb - ADB: 192.168.50.222 - getprop ro.build.version.release
2024-09-25 19:44:43.159 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:44:43.311 - httpx - HTTP Request: GET http://192.168.50.242:8086/8.ts "HTTP/1.1 200 OK"
2024-09-25 19:44:46.666 - lib.adb - timed out
2024-09-25 19:44:46.667 - lib.adb - ADB: Connection error. Device may be waking up. Trying again.
2024-09-25 19:44:46.670 - lib.adb - timed out
2024-09-25 19:44:46.671 - lib.adb - ADB: Connection error. Device may be waking up. Trying again.
2024-09-25 19:44:47.667 - lib.adb - ADB: 192.168.50.222 - settings list global
2024-09-25 19:44:47.668 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:44:47.668 - lib.adb - Failed to retrieve current configuration. Will not update Android device configuration.
2024-09-25 19:44:47.668 - lib.adb - ADB: 192.168.50.222 - dumpsys display
2024-09-25 19:44:47.669 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:44:47.669 - lib.adb - ADB: 192.168.50.222 - getprop ro.build.version.release
2024-09-25 19:44:47.669 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:44:47.672 - lib.adb - ADB: 192.168.50.222 - settings list global
2024-09-25 19:44:47.672 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:44:47.672 - lib.adb - Failed to retrieve current configuration. Will not update Android device configuration.
2024-09-25 19:44:47.672 - lib.adb - ADB: 192.168.50.222 - pm list packages -3
2024-09-25 19:44:47.672 - lib.adb - ADB: Error while running command. Check for approval popup on device.
2024-09-25 19:44:47.673 - uvicorn.access - 172.26.0.1:33262 - "GET /admin/tuner/installed-packages?_=1727293483436 HTTP/1.1" 200
2024-09-25 19:44:47.807 - httpx - HTTP Request: GET http://192.168.50.242:8086/8.ts "HTTP/1.1 200 OK"
2024-09-25 19:44:48.228 - uvicorn.access - 172.26.0.1:33250 - "GET /admin/tuner/metadata?_=1727293483434 HTTP/1.1" 200
2024-09-25 19:45:02.430 - lib.adb - ADB: Connecting to device (attempt 1).
2024-09-25 19:45:02.908 - lib.adb - ADB: Connected.
2024-09-25 19:45:02.909 - lib.adb - ADB: 192.168.50.222 - settings list global
2024-09-25 19:45:02.997 - root - adb_allowed_connection_time=0, adb_enabled=1, adb_wifi_enabled=0, verifier_verify_adb_installs=0
2024-09-25 19:45:02.997 - lib.adb - ADB: 192.168.50.222 - dumpsys display
2024-09-25 19:45:03.194 - lib.adb - ADB: 192.168.50.222 - getprop ro.build.version.release
2024-09-25 19:45:03.250 - lib.adb - ADB: Android Version: 12.0.
2024-09-25 19:45:03.330 - httpx - HTTP Request: GET http://192.168.50.242:8086/8.ts "HTTP/1.1 200 OK"
2024-09-25 19:45:03.378 - uvicorn.access - 172.26.0.1:33062 - "GET /admin/tuner/metadata?_=1727293483438 HTTP/1.1" 200
Well comes to find out that I cannot really use this anyway with my HDHomerun Primes as Google broke DRM playing for premium Channels using HDHomerun app. Watching TV used to be so simple.
1 Like
yup, they have not found a way around that yet. I think Silicondust was looking into it.
The windows HDHR software still works with drm, so I put an old windows mini computer running the app, and made it run with ah4c. Works decently enough for now.
4-Way HDMI Video Encoder H.265/H.264 4K 30fps 1080P For IPTV Live Stream or NVR | eBay
I purchased the above device awhile back and it has worked great. And had no Issues.
I'm using 2 encoders with no issues with ADBTuner. It's all about end point links and your setup of the custom tuner in Channels that matters.
1 Like
This is a pretty simple setup by the way, for anybody interested in viewing/recording those DRM channels off of their HDHomerun Primes. @Gregg_K's python script runs on any old Windows device to control tuning via the Windows HDHR app, which is then captured via an encoder. ah4c handles the proxy duties to interface it with CDVR.
Both the Python script, and the ah4c scripts are short and sweet. I haven't formally added this to ah4c, but anybody interested should post in the ah4c thread.
Am I overlooking how to do an update? I don't see it documented on the ADBTuner Github page. I don't even know what version it is - just shows the container was created 2024-08-05. Still absolutely loathe docker and portainer.
Use Watchtower in RUN_ONCE mode, with the Docker Compose and env vars shown here under "Watchtower". This will update any running containers, if there's an update available:
1 Like
Not all of us are sysadmins and that's my gripe. I don't know what to do with the drop downs in your link. Do I copy/paste it in Terminal or is there something I'm supposed to do with it in Docker? Great that all of those are there, but not everyone understands what to do with it. Ok, at least I don't know what to do with it. I get frustrated and things like the Portainer nag saying it had updates, but no way to update irritate me to the point that I just delete it. Only way I could get Docker to update was to shut it down and install the new version on top of it - the update on it doesn't work (downloads, shuts down and never updates or restarts).
They're intended to be used with Portainer-Stacks, which is the WebUI for Docker. Get Portainer running, and I believe things will make more sense to you (your screenshot is of Docker Desktop, not Portainer). Portainer is available as an extension in Docker Desktop, but it's not the full version -- which is what you want.
What OS are you running Docker Desktop on? With that info, we should be able to give you the basic steps to getting the full version of Portainer going. Once you can interact with your containers, via a browser from anywhere on your LAN (or Tailnet), things will likely start to seem more accessible and begin to fall into place.
1 Like
MacOS. 2018 Mac mini i5 6-core, 64GB RAM. Do I need the 3-node or SE version of Portainer?