Skip to content

Conversation

@passibe15
Copy link

I noticed that there wasn't a remote command for showing the input picker.

I use an AVR, so all inputs are only tied to one HDMI port and show up as (virtual) CEC player inputs in the input picker (basically the same as #515). But selecting the input on the AVR doesn't help in cases where I need to interact with the TV via the Control Center remote after switching the input. This is because the TV doesn't register that the AVR switched sources and keeps sending subsequent CEC remote commands to the device that is no longer shown on the screen.
That's why I wanted to have the option to show the input picker from the Control Center remote.

After some searching I came across this guide which mentions that com.webos.surfacemanager/showInputPicker can be used to show the input picker.

With my proposed changes, SHOW_INPUT_PICKER can now be set e.g. in ccRemoteRemap to make the input picker appear on screen.

I've implemented this in a somewhat minimally invasive way as a part of sendRemoteInputSocketCommand. This doesn't really fit the function's name anymore, since it's not using the remote input socket. It also means that the debug log output doesn't really match anymore. But I'm not sure if this could be implemented in a cleaner way without also making other major changes to how remote commands are handled.

@merdok
Copy link
Owner

merdok commented Aug 18, 2025

Thanks for the PR. I find your solution for this quite smart 😄 I am just thinking if this is really the right way, but i understand that it is the only way to use it for ccRemoteRemap. Would it be not enough to just have it as a switch on the TV group in the Home app?

@passibe15
Copy link
Author

Hm, for me, having it as a switch wouldn't be enough as I don't want to exit the CC remote. But of course, feel free to implement this (or not) as you see fit, no worries!

@merdok
Copy link
Owner

merdok commented Aug 22, 2025

In general this approach would allow for more functionality to be available on the CC remote which I actually find good. Maybe we should just name the actions differently so that it is clear that these are custom actions? SHOW_INPUT_PICKER sounds like it would come natively from the TV. Maybe we could a prefix or a completely different naming scheme something? Maybe like the function name showInputPicker?
That way we could keep a list of custom commands and these could also be bound to the CC remote...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants