-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT] Some new found endpoints to document #103
Comments
@elupus How did you find these? I'm trying to dig and see if there's an endpoint (or via Android) to get the current HDMI input. Are you aware of any such functionality? |
You can extract the xtv.apk package from an android tv and dissassemble it. You get most sourcecode back. There is no endpoint for hdmi source sadly. Should be possible to get if one writes their own android app thou. You can trigger a switch to hdmi source using an intent. |
@idantene, I agree with @elupus: there are no HDMI source endpoints and writing your own Android app is probably the best way to get this info reliably. Alternatively, you can write a simple script to query the system logs via adb: |
The But alas - if it is not available by default, I will make my own workarounds within HA 👍🏻 Thank you for your suggestions and time! |
Has anyone meanwhile found a way to know what source the TV would be on? Seems pretty ridiculous that this basic functionality is hidden so far away. |
Is your feature request related to a problem? Please describe.
I found some new endpoints that might be worth documenting. No idea what they are, but wanted to write them down:
/6/context
/6/channeldb/servermapping/X
/6/channeldb/tv/channelLists/{channel_list}/{ccid}/logo
/6/recordings/list
/6/recordings/refresh
/6/reminder/list
/6/input/textentry
/6/input/pointer
/6/input/onscreenkeyboard/visible
/6/companionlauncher/launch_request_details
/6/companionlauncher/launch_response
/companionlauncher/registration
The text was updated successfully, but these errors were encountered: