CoZ

Yup, I tried just using 2457 but it wouldn't connect. So all the ports need to be forwarded. Thanks.

Thanks for that. Just got into this game a little while ago and was hoping there was a Docker for running it. Now I just need some friends that own the game as well. Quick question concerning the ports; you need all of those ports listed to be forwarded? The entire range of 2456-2458 or can you just pick ONE (eg: 2457) and forward it to the UnRaid docker?

I installed that docker briefly a while back. Had NO idea what it was doing or what it was supposed to do but everyone swears by it. I'll have to re-visit that at some other time. Right now, I'm just imply trying to get everything off of SmartThings and onto H.A. without breaking stuff lol The screenshots help though, I might be able to "translate" that into regular H.A. stuff. Thanks, again.

Yes Sir, that is correct. On a whim, I'd figure I'd try it and it worked. Multiple deleting / installing your docker, multiple revoking and enabling network debugging, multiple reboots of the Shield.... all produced those error messages in the Docker Log file but yet, ADB commands work. After getting the ADB commands to recognize, I went ahead and re-added the Shield I was sending ADB commands to back into Home Assistant and EUREKA it showed up with no errors. Weeks of this troubleshooting. It's kind of anti-climatic now at this point now that it's actually working as it should. Although I still can't power on/off the device from HA - I can "see" everything else the device is doing. Thanks for helping me troubleshoot the issue though!

I tried to break apart your post to answer them underneath the quote but I'm not Unraid Forum posting savvy yet apparently. I've removed and re-installed this Docker container a few times now trying to isolate the issue. Initially I had both of my Shield devices in the docker but then removed one just to concentrate on one device only. Apparently removing it form the config didn't actually remove it from the docker because it was still trying to connect to the other device I had removed - strange. It's the same exact error messages across the "board" looking at the Log files of the docker, regardless of which Shield device I'm trying to connect to. Just replace the error messages with the IP address of .104 or .103 I see the same exact error messages with only Networking debugging on that I saw with the USB+Network debugging on. It makes no difference. I know others have used it to connect to their "Smart TVs/Android" and Shield devices so that shouldn't make a difference. I'm also able to successfully connect to my Shield Devices using my Win10 computer and ADB from it. I can "Adb Devices" in the CMD Prompt of Win10 and it will return the Shield device. So something is going on that isn't 'normal'. My HA config looked exactly the same as your HA Config you posted. I've tried with the ADB Server (your docker) and without the ADB Server (and I never get a prompt to authenticate without - only using your ADB Docker did I get the prompt) Not sure where to look at this point. I've pretty much tried everything I could think of. EDIT: Just a further update. I'm able to go into your Docker's shell and issue every single ADB command I could think of. Adb Reboot reboots the shield for instance. Even though the docker's log file is full of these two lines over and over: adb I 02-03 23:22:34 8 127 transport.cpp:271] BlockingConnectionAdapter(): destructing adb I 02-03 23:22:34 8 127 transport.cpp:346] BlockingConnectionAdapter(): not started already connected to 192.168.1.104:5555

So with both USB and Network enabled: adb I 02-03 19:18:12 8 8 auth.cpp:437] adb_auth_init... adb I 02-03 19:18:12 8 8 auth.cpp:412] adb_auth_inotify_init... adb I 02-03 19:18:22 8 17 transport.cpp:283] 192.168.1.104:5555: read thread spawning adb I 02-03 19:18:22 8 18 transport.cpp:296] 192.168.1.104:5555: write thread spawning adb I 02-03 19:18:22 8 8 transport.cpp:1365] fetching keys for transport 192.168.1.104:5555 adb I 02-03 19:18:22 8 8 auth.cpp:489] Calling send_auth_response adb I 02-03 19:18:22 8 8 auth.cpp:456] Calling send_auth_publickey failed to authenticate to 192.168.1.104:5555 adb I 02-03 19:18:32 8 8 adb.cpp:114] 192.168.1.104:5555: offline adb I 02-03 19:18:52 8 23 transport.cpp:271] BlockingConnectionAdapter(): destructing adb I 02-03 19:18:52 8 23 transport.cpp:346] BlockingConnectionAdapter(): not started already connected to 192.168.1.104:5555 adb I 02-03 19:19:22 8 28 transport.cpp:271] BlockingConnectionAdapter(): destructing adb I 02-03 19:19:22 8 28 transport.cpp:346] BlockingConnectionAdapter(): not started already connected to 192.168.1.104:5555 With USB only: adb I 02-03 19:20:48 8 8 auth.cpp:437] adb_auth_init... adb I 02-03 19:20:48 8 8 auth.cpp:412] adb_auth_inotify_init... adb W 02-03 19:20:58 8 16 network.cpp:149] failed to connect to '192.168.1.104:5555': Connection refused failed to connect to '192.168.1.104:5555': Connection refused

Are you suggesting enabling both USB & Network debugging or just USB debugging and leave Network off? At this point, I'll try anything. Too much time of my life has been spent on this lol BTW: Still running your SUI Start Page!

Yes sir. I've tried both the Nvidia Shield Pro and my Nvidia Shield TV with and without the ADB Server info. Without the ADB Server info, I never get the prompt on the device asking to allow the connection and no device/entity shows up in HomeAssistant with the names I gave the devices. With the ADB Server, I get the prompt for the connection but then.... nothing happens after that. Hitting "Yes" and "always trust" does nothing past that. The devices never show up in H.A. and the errors about it not being able to connect using the ADB server or, the device is not connected show up in the HA Logs. I've revoked the keys, rebooted both devices, enabled and disabled network debugging. Same result over and over. "Offline" / "Already Connected" over and over again to both devices in your Docker log.

Yes sir, it does indeed say that I also have this bit of confusing information: adb I 02-02 22:27:49 8 17 transport.cpp:283] 192.168.1.103:5555: read thread spawning adb I 02-02 22:27:49 8 18 transport.cpp:296] 192.168.1.103:5555: write thread spawning adb I 02-02 22:27:49 8 8 transport.cpp:1365] fetching keys for transport 192.168.1.103:5555 adb I 02-02 22:27:49 8 8 auth.cpp:489] Calling send_auth_response adb I 02-02 22:27:49 8 8 adb.cpp:114] 192.168.1.103:5555: offline connected to 192.168.1.103:5555 It says "offline" and then right after it it says it's connected. Not sure which line to believe.

So I've been struggling for a few days now connecting my Nvidia Shield PRO (and also my Nvidia ShieldTV) to HA. Most people I run across just say "I just simply put in my IP address into the Config.yaml file and it connects, I never even need to acknowledge the prompt to allow it to connect" Unfortunately, I am not one of those people. I've installed this ADB Docker container. Verified in the shell with adb devices and it returns my Shield TV that's connected. I even got the "Allow this computer to connect" notification on the Shield initially. So, I went ahead and added the rest of the lines to the config.yaml file to point to my unraid ADB docker: media_player: # Use the Python ADB implementation - platform: androidtv name: Living Room Shield host: 191.168.1.103 adb_server_ip: 192.168.1.102 adb_server_port: 5037 My Unraid IP is correct. The docker port is correct. Yet my HA install has all these errors in the log: Logger: androidtv.adb_manager.adb_manager_async Source: /usr/local/lib/python3.8/site-packages/androidtv/adb_manager/adb_manager_async.py:400 First occurred: 5:39:13 PM (1 occurrences) Last logged: 5:39:13 PM Couldn't connect to 191.168.1.103:5555 via ADB server 192.168.1.102:5037 because the server is not connected to the device Logger: homeassistant.components.androidtv.media_player Source: components/androidtv/media_player.py:227 Integration: androidtv (documentation, issues) First occurred: 5:39:13 PM (1 occurrences) Last logged: 5:39:13 PM Could not connect to Living Room Shield at 191.168.1.103:5555 using ADB server at 192.168.1.102:5037 So one of these programs is lying to me ... either HomeAssistant or the Docker lol Any suggestions? Because I am at my Wit's end here with this.

@bashNinja - just an update; I'm running unRaid 6.8.3 and I finally figured it out. There still has to be a PS3ISO folder in the share on the array. I was just dumping everything into the share which is incorrect. Anyway, I'm not having any issue using your docker. It finally scanned the ISO and loaded it without any issue. Well besides the incredibly slow WiFi speeds which caused this particular ISO that had Full Motion Video cut scenes to be unplayable. I will try another ISO without so much F.M.V. and see what happens. But for whatever reason, I'm not having an issue with your Docker.

Thanks for taking the time out to reply. I can understand your frustration on this. I don't have any corrupted data message. Unless I'm doing something entirely wrong with this (which could be a possibility as I've just started my venture down this whole PS3 CFW escapade). webMAN will scan my PS3 directory just fine. I can "See" the files in the webMAN file manager. However when I initiate a scan/refresh from the XMB, it never actually recognizes the games. They just simply don't 'show up' in the PS3 Game folder on the GUI. I'm not sure if I can just slap the ISO in my PS3 share or if the need to be in separate folders or if they need to be inside a PS3ISO folder on the share.. etc...etc.. There isn't real documentation out there on the webMAN plug-in or, I'm just not looking in the right place for the info.

Well that explains why I can "see" the files on my Ps3 but absolutely nothing happens when I initiate a scan. Just bought the kid a PS3 and messing around with CFW and such and stumbled on this. Thought it would be much easier to do this than copying ISOs over to the USB and plugging / unplugging etc..etc.. Damn sorry to hear your request was ignored. This would have made life so much easier.

I tried to pass through my Nvidia 1050ti and it blew up my entire unraid system. I am still trying to get everything back up and running correctly. Why it just wouldn't fail to start the VM with an error, instead of taking out all my VMs and causing a hard reboot is beyond me.

How does one stop it from running through piHole? If the piHole docker is on the server and the DNS settings on the WAN part of the router point to the piHole's docker IP address, how can you stop unRaid from running through it?

So this was working for me without issue previously (after not working for whatever reason). I just upgraded my Cache drive from 240GB to a 1TB different manufacturer. I tried to run the scrutiny command again in the docker's console and, once again was greeted by this lovely message that no one seems to have an answer for: INFO[0000] Sending detected devices to API, for filtering & validation type=metrics 2020/12/09 22:07:35 ERROR: Post http://localhost:8080/api/devices/register: dial tcp 192.168.1.123:8080: connect: no route to host

I've got /data pointed to the host path of /mnt/user/Downloads/Qbittorent/ That's the directory I created for QB downloads. Or am I just missing this whole thing entirely and too stupid to figure this out? Knowing myself, I'm going to go with option B. lol

Thanks for the reply but that doesn't help me at all. Either I just don't understand it at all or it's not applicable because Q2 is talking about Volume Mappings I've tried to go into settings of Qbittorent to change the default save path but it also won't let me move it out of /mnt/user/appdata/binhex-qbittorrentvpn/qBittorent/downloads

Ok, I'm back with one question I can't figure out: /container path data is mapped to where I want my downloads stored on my array? Be default it's just mapped to "data". So I created a folder on my SSD and changed it from "data" to the folder I created. However, all my downloads are being saved in /mnt/user/appdata/binhex-qbittorrentvpn/qBittorent/downloads

So I followed the instructions on this post since 8080 was already in use. I've tried 8081/8082 etc..etc... Everytime I try to launch the WebGUI, Binhex-SabNZB opens instead of Binhex-Qbittorent. It's kind of amusing and frustrating all at the same time. Anyone have any ideas? Edit: Figured it out myself. Even though I changed the WebUI port along with the container port, the 'right click on the icon to launch the WebGUI was still launching unraid IP:8080 I had to enter into advanced view and change the icon url port in there to the new port as well. Now it's working.

Settings - disable audio encoding That will keep whatever audio is on the file intact.

I've been using romancin/tinymediamanager - and it works fine. I've been getting updates pushed to it so it is in active development. Just don't update to V4. I did and it breaks the docker. I read somewhere that there are no plans for him to upgrade compatibility to V4 of TMM because it's a paid program now. Otherwise, there is nothing wrong with Romancin version

@Josh.5 you've been pushing a ton of updates lately! Almost daily I get an update container notification on my unRaid server for your docker.

Well this is DAMN strange. I've changed nothing but noticed a update to the docker container a few days ago. I updated the container and left it alone. I started it today to come back and try and figure out how to get past the error message I was getting... started the WebGUI and all my HDD data was there. I hate and love when stuff like this happens lol

Yup, I didn't touch the api endpoint. I only changed the webgui port.