You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Android TV for Media Player is almost perfect but a lot of features for TV sets based on Android TV have a lot of missing features.
Additional context
Last week I did my first steps with the core-api and it seems that the remote has 2GB RAM and 4GB FLASH so there is quite some space.
With adb my Philips TV can directly switch the different inputs and also the different sound outputs like ARC, BlueTooth or internal speaker. adb only needs USB debug enabled, the IP (which the integration already has), port 5555 and a string. The string could be made configurable as a source input like the http-get integration does it.
The text was updated successfully, but these errors were encountered:
I am not asking for me. I have it already running but not with HAss instead with IP Symcon. I am asking for people which have not the skills and/or equipment to have a home automation running.
I do not know if HAss also can switch audio output? If not here is a tip:
"adb -s " . $ip . ":5555 shell settings put global hdmi_system_audio_control_enabled 1";
will enable ARC on my Philips TV.
btw. thank you kennymc.c for the Swiss army knife HTTP-Post integration.
BlueTooth seems to be on the way. For FireTV I think there will be either no or only a limited amount of commands to directly start an App. Here adb would be a great help. So instead of integrating it into AndroidTV it makes more sense to have a separate adb integration imho.
Description
Android TV for Media Player is almost perfect but a lot of features for TV sets based on Android TV have a lot of missing features.
Additional context
Last week I did my first steps with the core-api and it seems that the remote has 2GB RAM and 4GB FLASH so there is quite some space.
With adb my Philips TV can directly switch the different inputs and also the different sound outputs like ARC, BlueTooth or internal speaker. adb only needs USB debug enabled, the IP (which the integration already has), port 5555 and a string. The string could be made configurable as a source input like the http-get integration does it.
The text was updated successfully, but these errors were encountered: