[Feature Request] Add CYCLE_INPUT support for media_player entity

[mase1981]

Hey Team, suggesting to add CYCLE_INPUT feature and command to the media_player entity to support devices that can only cycle through input sources sequentially, rather than selecting them directly.
Use Case
Many Samsung soundbars (Q950T, HW-Q70T, and others) do not support direct input source selection via the SmartThings API. Instead, they only support cycling through available inputs sequentially using the setNextInputSource command.
Currently, the UC Remote API only supports:

SELECT_SOURCE - Direct selection of a specific input source
No cycling functionality

This creates an unsolvable problem for integration developers working with devices that only support sequential cycling.

Suggesting to add CYCLE_INPUT = "cycle_input" for both media player and remote entity

this should be very similar to:
Channels: CHANNEL_UP/CHANNEL_DOWN (cycle) vs direct channel selection
Volume: VOLUME_UP/VOLUME_DOWN (cycle) vs VOLUME (direct)
Tracks: NEXT/PREVIOUS (cycle) vs direct track selection

this is so i can potentially provide enhancement to my Smartthings integration (and other potential integrations) https://github.com/mase1981/uc-intg-smartthings

[rom-1]

+1, this is quite a problem with the Samsung Q990F soundbar too, as therefore I cannot use Remote3 to fully control my living room home theatre setup. Always need the soundbars remote in addition to Remote3.

[zehnm]

This sounds more of an integration specific issue than a generic feature of the Python integration library. If it's a requested API enhancement, then it needs to be added to the Integration-API first: https://github.com/unfoldedcircle/core-api
This Python library is only a wrapper for the Integration-API.

Please proivde more information what exactly you would like to achieve. Simply adding a CYCLE_INPUT command to the media-player is probably not what you have in mind. Should it replace or enhance the existing input functionality? I assume you'd also have UI enhancements in mind, or is a command sufficient that can be used in an activity or for button mappings?

This creates an unsolvable problem for integration developers working with devices that only support sequential cycling.

If it's just adding more commands, this can easily be added to the media-player with the "simple commands feature" (or by also exposing a remote-entity). Apple TV integration example: https://github.com/unfoldedcircle/integration-appletv/blob/664101044d6ec063001476ce5eb1fe378b249c98/intg-appletv/driver.py#L52-L82

[mase1981]

thank you so much @zehnm for taking the time to response, and i do apologize for the delay in mine (was focused on the Android app i forgot to respond :) )

To answer your questions,

1. This Should Be in Core-API
   You're 100% correct - I apologize for posting it here, do you want me to re submit or can it be moved?

2. Replace or Enhance?
   Enhance - CYCLE_INPUT should coexist with SELECT_SOURCE.

• Devices supporting direct selection: use SELECT_SOURCE (current)
• Devices supporting only cycling: use CYCLE_INPUT (new)
• Devices supporting both: integration chooses or both are available

3. UI Requirements
   Not just a command - needs UI integration:

• Single "Cycle Input" button in source control area
• Appears where input buttons normally show
• Available in activity editor like other media_player features

4. Why Simple Commands Insufficient
   Simple commands are for additional device-specific functions, not core device behavior.

Input control is core functionality like volume/channels - we needs proper feature support, not workaround.

Samsung Q950T/HW-Q70T are not edge cases - many soundbars only support cycling, TVs included. As of late many devices just have a single INPUT button which cycle vs direct input.

5. Real-World Impact
   Without this:

• Users forced to use physical remote for inputs
• Integration appears broken ("input buttons don't work")

Would you like me to resubmit in Core-API or you prefer to move it?
This is not a deal breaker, according to my stats about 202 Unfolded Circle users downloaded my Smartthings integration, and out of them 5 reached out about this input select usecase, prioritize as you see fit.

[zehnm]

Shame on Samsung for using such a broken design with only a cycle function (or company policy preventing to publish dedicated commands). This really makes it unsuitable for any kind of automation :-( Still interesting what kind of workarounds people come up with, like the “Bluetooth paring reset point” https://community.smartthings.com/t/samsung-q990-soundbar-input-switching-workaround-for-alexa/304114)
But yes, I agree that this is a required functionality for all the broken devices on the market. It’s one thing if the original remote only has a power toggle or a cycle input button but still provides dedicated IR or IP commands for power-on / off and switching to dedicated inputs (which many companies provide), versus not providing them at all.
/rant off

Without this:

• Users forced to use physical remote for inputs
• Integration appears broken ("input buttons don't work")

This only applies to the media-player entity and it’s UI view.

Most of the requested functionality can already be achieved with a “CYCLE_INPUT” simple command and using activities. This command can be mapped to a UI button / icon to cycle through inputs. That’s usually what most people use when controlling multiple devices like a TV and a receiver or soundbar. It would be interesting to know how many people prefer the simple media-player UI view over an activity.
Most of the media-player UI functionality like the input source selection list can soon be achieved in an activity screen as well. A new “select-entity” will be available later this month.

Adding this to the media-player entity and its specific UI screen requires more changes and is a lower priority right now. I will bring it up internally for discussion, but most likely this is an enhancement for the new UI app we are working on.

I will move this issue to the core-api repository.

[rom-1]

Hi, I just want to chime in and add to this topic that the cycle functionality with Samsung Soundbars is not only effecting INPUT selection, but also SOUNDMODE. e.g. the Q990F can only cycle between STANDARD, SURROUND, ADAPTIVE, GAME, etc, there is no direct selection possible. Not sure if this is information is relevant for this Feature Request, just a quick heads up that this problem is not only limited to INPUT selection, soundmode needs cycle functionality also.

[mase1981]

Thank you so much @zehnm ,and I 1000% agree with your rant 🤣🤣