-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[lgwebos] mediaPlayer does not accept NextPreviousType #7278
Comments
@sprehn : do previous and next commands exist in the API? I don't see these commands in the code. |
It is all reverse engineered based on connectsdk. |
option A) we could simply give it a try, for example with No access to my TV at the moment, so cannot try. option B) |
@sprehn: Thank you for getting back to me and indeed for all your work on the lgwebos binding. I am self-isolating due to the coronavirus at the moment and set myself a project to get to grips with openHAB to control my entertainment system. It is proving to be a most enjoyable way to isolate :-) Option A Option B But... Thanks for the pointer. |
I updated the code to use
Failing too with PS: I tested for the first time play/pause when the Music app is running and it works as expected. |
Now that I checked the code and tested the media player feature, I can see that something is missing in the code, the state of the channels |
@lolodomo: Thank you for investigating. I am of no help looking at the source code side of things but if there is any testing I can help with in openHAB then do let me know. |
@optmax : unfortunately, this is clearly not obvious to guess what are the SSAP commands to be used for PREVIOUS/NEXT commands. We are not sure they even exist. I just tried the most probable ones but without any success. |
@lomodomo: I have just tried the Next and Previous buttons in the LG TV Plus app on Android and they don’t work! So maybe LG never implemented the code? |
@sprehn : if sendRCButton is working with LEFT and RIGHT, we could simply use it as commands for the player item. |
Tested but not really "reliable" because it depends on what was the previous mouse position. |
I've been experimenting with an RCButton sequence and find that its slightly more reliable if you also have a sequence to step back through the PLEX App to the Home page before changing to another input. I found that starting the 'escape sequnce' with |
Hi, Item 'TV_Bed_Player' received command NEXT Item 'TV_Bed_Player' received command FASTFORWARD The Player item in openhab sends "NEXT". If it would send "FASTWORDWARD" the buttons will work. |
This simple workarourd will do the job:
|
The normal commands for the openHAB player widget are play/pause, previopus and next. |
Expected Behavior
Within a mediaPlayer clicking the Next icon should move to the next track
Similarly clicking Previous icon should move to the previous track
(Pause and Play work as PlayPauseType input is accepted)
Current Behavior
==> /var/log/openhab2/openhab.log <==
2020-04-02 21:25:18.529 [DEBUG] [ebos.internal.handler.LGWebOSHandler] - handleCommand(lgwebos:WebOSTV:a3c77ba0-654a-0982-c480-f726662f05b8:mediaPlayer,NEXT)
2020-04-02 21:25:18.534 [INFO ] [.lgwebos.internal.MediaControlPlayer] - Only accept PlayPauseType, RewindFastforwardType, RefreshType. Type was class org.eclipse.smarthome.core.library.types.NextPreviousType.
Possible Solution
Steps to Reproduce (for Bugs)
Context
Control apps on webOS TV
Your Environment
Raspberry Pi 3 ARMv7
Raspbian GNU/Linux 9 (stretch)
openHAB 2.5.4 Build #74
LG web OS Binding 2.5.4.202004020414
Item
Player TV_Player { channel="lgwebos:WebOSTV:a3c77ba0-654a-0982-c480-f726662f05b8:mediaPlayer"}
Wihin a Rule
TV_Player.sendCommand( NEXT )
==> /var/log/openhab2/openhab.log <==
2020-04-02 21:25:18.529 [DEBUG] [ebos.internal.handler.LGWebOSHandler] - handleCommand(lgwebos:WebOSTV:a3c77ba0-654a-0982-c480-f726662f05b8:mediaPlayer,NEXT)
2020-04-02 21:25:18.534 [INFO ] [.lgwebos.internal.MediaControlPlayer] - Only accept PlayPauseType, RewindFastforwardType, RefreshType. Type was class org.eclipse.smarthome.core.library.types.NextPreviousType.
The text was updated successfully, but these errors were encountered: