Not sure if this an issue with LG IP Control module, or WebOS quirk? The following via lgtv-ip-control commands:
Set TV to HDMI1
Set screenmuteon
Set TV to HDMI2
HDMI1 is displayed... this does make sense?
IMHO. expected result is allmuteoff state, and TV displays HDMI2, however, TV displays HDMI1, as set in step 1. So although allmuteoff is the new screen mute state, the HDMI2 set input never seems to happen. Either the WebOS is not honoring HDMI2 or lgtv-ip-control is not?
The issue is masked, if you do the following...
Set TV to HDMI1
Set screenmuteon
Set TV to HDMI1
HDMI1 displayed
Never see the changed input being dishonored, because original input and new input is same.
The issue never happens if you do...
Set TV to HDMI1
Set screenmuteon
Set allmuteoff
HDMI1 displayed
The issue is also masked depending on the actual TV remote, some models of TV remotes have direct input for HDMI1, HDMI2, etc. In my case, not having direct input buttons, my remote seems to send allmuteoff when I hit the input button. And I have to hit input again to select a different input. So maybe the above behavior is WebOS design?
Not sure if this an issue with LG IP Control module, or WebOS quirk? The following via lgtv-ip-control commands:
IMHO. expected result is allmuteoff state, and TV displays HDMI2, however, TV displays HDMI1, as set in step 1. So although allmuteoff is the new screen mute state, the HDMI2 set input never seems to happen. Either the WebOS is not honoring HDMI2 or lgtv-ip-control is not?
The issue is masked, if you do the following...
Never see the changed input being dishonored, because original input and new input is same.
The issue never happens if you do...
The issue is also masked depending on the actual TV remote, some models of TV remotes have direct input for HDMI1, HDMI2, etc. In my case, not having direct input buttons, my remote seems to send allmuteoff when I hit the input button. And I have to hit input again to select a different input. So maybe the above behavior is WebOS design?