Hello, I’m hoping to get some pointer as to why my AndroidTv integration is NOT fully functional.
I just bought a 43 inch, TCL series 4, AndroidTv . I was able to setup the “developer options” on the TV to enable USB debug and ADB services. I then integrated it to HA as follows:
```
media_player:
- platform: androidtv
host: 10.0.0.199
name: TCL 43s434 Android TV
## device_class: androidtv ## using this attribute did not change behavior.
```
Using the developer tools, I can control the TV by calling a service “androidtv: ADB command” and supply various ADB commands. for example, I can select items on the screen (netflix or YouTube), and I can change volume, and exit a playing tv program to select another…
However, If I send the “POWER” command then the TV will turn off as expected. But now I can NOT turn it back on. the way I attempted to turn the TV back on, is by sending the ADB command “POWER” again (which I was hoping would toggle the power back on). However, that did not work !!
I also tried the command “WAKEUP” but that did NOT do anything.
the only way I can turn the TV back on is by using the actual remote control that came with the TV…
I’m looking for guidance, as to what I’m doing wrong in here…I’m assuming that the ADB POWER command is used to “toggle the power” is this correct ? or do I need to use a different ADB command.?
Observation: The TV is behaving as if I turn-off the TV (via ADB POWER command) it some how disables the ADB bridge all together and won’t respond to any further ADB commands. Could this be the issue ? …
Thank you in advance for any pointers…Your help is much appreciated,
thank you Vadimbz for your suggestion.
I will look into the IR blaster HW solution you suggested.
though I was hoping for a native HA solution for such a popular TV device. since I’m new to home automation I thought I can learn more about the SW to control this ADB bridge that I read about…However, it seems that the ADB bridge can’t turn on the device (if the bridge lives on the same device that was turned off a bit earlier)…well anyway, I guess you can’t win them all.
Again thanks for the suggestion.
This is a bit of deadposting, but those ir blasters are pretty cool and 100% reliable, you can’t go wrong with it really, mine controls dumb fan and AC as fully functional climate entities in addition to TV, and if you set up your TV with this
Be carefull hawanam.
Your AndroidTV may have a bluetooth remote, so if you get an IR blaster you may fail connecting it.
I have the same problem as you, but my case with Xiaomi MIBOX S. I got a Broadlink RM4Pro for it (can only IR and RF), but ended up not using it due to bluetooth remote.
If you find a solution to turn back on the AndroidTV Integration, I’d appreciate you let me know.
Regards.
I had both IR and BT - as in 2 separate remotes. Also, my TCL has ability to wake up when cast is initiated (it’s in network settings), you may be able to use it.
I have a TCL 43P715 Android TV. I can power it on most of the time using Wake On Lan. It does appear that the network completely powers down after a while and I can not use WOL anymore, but I am trying to work through at the moment.
Hi, new to HA, could you please tell me where to place this “wake on lan service” as said by @aheath ? Like in configuration.yaml (I have HAOS) ? Also, I have to call this service inside the media player somehow right?