use this within a homeasistant automation

[sojab0on]

Is it posible to use this for google tv devices with in the automation part of the device in home hasistant

I ask it because I want to setup 2 chrome casts with google tv to be triggered at specific times to power up and start a app ( amazon prime video) witch can't be started with a basic command so might be better via a adb command

[netrene]

I have exactly the same question. Would be great to have the possibility to send commands via automation. Or do I miss something? I understand that currently the only way to do things is the WebUI?

[sojab0on]

the automations you normally build in the web ui and they run on the trigger ls you set

[netrene]

Can you explain morde detailed? I use now Android/TV Debug Bridge and use this Addon here as Server. Then I can send commands via AndroidTV Debug Bridge via ADB Server. That works, but I´m also struggling with Autoconnect devices at startup.

[sojab0on]

auto connect is not working any more the newer os versions wont expose the default port but rather expose a random port on every restart or sleep wake cycle. so auto connect is broken due to that

with older devices port 5555 was exposed but as said in newer devices with Google tv in stead it does a random one every time the adb debug is started on devices start

[netrene]

Well, I was able to solve the issue you mentioned by changing TCPIP to port 5555 after i connected the device via random port.

Since that I can always do the connect using port 5555. That works since yesterday and even after a restart of the ABD Server without pairing code.

So the command is: adb tcpip 5555

That opens a second port on the android device that is forever reachable through port 5555.

But the reconnect devices is stilkl not working. Looks to me like it´s not properly implemented.

However I´m now exploring ways to do the reconnect automatically maybe from the Android/TV Bridge.

[sojab0on]

after a reboot it wil revert to random port

[netrene]

after a reboot it wil revert to random port

Maybe after a reboot of the Tablet, but not HA. As I understood it will keep the port 5555 open forever. I will test tonight.

[sojab0on]

its not a tablet iny case and the case of where this wont work, its the Chromecast with Google tv as os on it.

that will revert to random on every reboot as far as i could find that due to making it more secure and the addons for ha cant work with random ports for auto connect

[Amateur-God]

@netrene recconect devices does not work the entire configuation tab is currently deprecated with no plans to reimplement it due to too many issues/bugs with it in the past

[netrene]

@Amateur-God
Well that makes the addon kind of useless or is there any other way to trigger a reconnect from HA automation or maybe via ssh or via Android TV Debug bridge, when setup to use your addon as adb Server. Or maybe via hassio.addon_stdin?

I‘m at 99% but the missing reconnect is messing everything up.

Regards Rene

[Amateur-God]

It makes it useless for your use case yes, but doesnt make it useless in general, there is still lots of uses for an ADB server addon.

ATM the feature is deprecated because it was extremely buggy and not reliable with the version of ADB in Debian package manager however, the next release will be a version that builds ADB from source so once the next release is out it may be reimplemented in future but it's not something I can guarantee.

I don't know of any other ways for you to try and do it.

[netrene]

@Amateur-God
Sorry if I was a little bit harsh but let me explain.

I see Homeassistant as a platform to control devices. I use your addon as adb Server and use Android TV Debug Bridge to open an app on an android tablet and press a button.

I was even able to always connect with port 5555 without pairing again.
That works fine.

But after any restart of HA I have to do the reconnect manually.

I don’t see any use case with just a console to manually enter commands.

I can live with that for a while and keep fingers crossed that you find some time to implement it. Trigger connect via HA automation would be the best solution for all users imo. That would be in the real spirit of Home Assistant.

Regards Rene

[sojab0on]

the issue isnt ha on its own , it the way the adb debug bridge is implemented by Google into Android it self.

my question wasnt for tablets but the Chromecast and other Google tv based devices.
the default port isnt exposed by default in some cases Google completely removed it in newer versions. might be part of getting rid of sideloading witch Google is actively dooing atm.

other question why would you reboot ha, normally you just reload the config files. i hardly ever reboot it because it also tracks solar panels and power use from the grid.

i most cases the reconect failed due to the Google tv device rebooted and responses a port randomly.

i gave up on dooing a automated start trigger and app launch because of the Google tv device constantly reasigning port on reboot
and the app i want to to start having a custom command set that wont let it start up correctly