08-27-2025 01:20 PM
I think this is well known by now, but a recent patch push broke the ADB integration to GTV devices from Home Assistant - now the ADB pairing is complex and only works from a wireless connection and does not survive a boot. The only workaround is to go to drop the wired connection, go to Wi-Fi and use ADB to connect and change the port back to default (5555) on wireless.
Two fixes requested:
1) Allow ADB to work over a wired connection. I can't see any reason why wired is not allowed. Oversight?
2) Allow the ADB debugging connection parameters to survive a restart.
My use case is controlling the room lighting based upon Play/Pause/Resume/Stop, as well as by which app is being used. I also use a software remote in Home Assistant to control the TV.
08-31-2025 02:09 PM
Hi wmichael3,
Thanks for posting in the community.
I understand you're experiencing an issue with the ADB connection on your Chromecast with Google TV over a wired connection, and that this connection doesn't survive a reboot. I appreciate you for the detailed report for bringing this to our attention, along with your clear workaround and proposed fixes.
Because this issue is related to the core software functionality of the device, the best way to ensure your feedback is seen by the development team is to submit your report through this feedback form. Your input will help us prioritize features and ensure that we're meeting the needs of our diverse user base.
Feel free to keep us posted if you have more questions.
Best regards,
Virna
09-05-2025 10:15 AM
I am getting below error after Chromecast OS version updated last week
"adb connect <IP address>
"cannot connect to <IP address>:5555: No connection could be made because the target machine actively refused it. (10061)"
developer option and wireless debugging is ON, ip address is correct
Under Wireless Debugging menue i saw Port number is 39697, tried with new port number as well, didn't work
09-05-2025 09:31 PM
You need to pair using:
adb pair <ip_address>:<port>