Skip to content
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

Unable to PowerOff on PowerOn the device #3

Open
frazrepo opened this issue Dec 23, 2018 · 2 comments
Open

Unable to PowerOff on PowerOn the device #3

frazrepo opened this issue Dec 23, 2018 · 2 comments

Comments

@frazrepo
Copy link

Hello,

Successfully working on my samtvcli UE55JU6900. Most of the keys command work but the only one that i'm unable to send is the power key ( by sending POWER key like KEY_POWEROFF or KEY_POWEROFF2 or KEY_POWER ).

The TV does nothing.

This is the debug log of KEY_POWEROFF command :
INFO[0000] Using config file: /home/me/.config/samtvcli/samtvcli.yaml DEBU[0000] Fetch URL: http://tvip:8000/socket.io/1/?t=1545597519531 DEBU[0000] Reading WS message... DEBU[0000] Read message (type 1):1:: DEBU[0000] Got greetings from TV DEBU[0000] Sending SmartView handshake... DEBU[0000] Sending WS message:1::/com.samsung.companion... DEBU[0000] Reading WS message... DEBU[0000] Read message (type 1):1::/com.samsung.companion DEBU[0000] SmartView handshake completed DEBU[0000] Reading WS message... DEBU[0000] sendMessage('KEY_POWEROFF') DEBU[0000] Sending WS message:5::/com.samsung.companion:{"name":"callCommon","args":[{"Session_Id":1,"body":"[28, 252, 219, 239, 245, 241, 57, 50, 160, 29, 68, 84, 218, 132, 176, 134, 187, 58, 225, 199, 214, 222, 235, 56, 216, 108, 143, 245, 4, 228, 118, 71, 200, 179, 195, 111, 18, 10, 183, 7, 94, 134, 85, 5, 165, 132, 188, 15, 130, 162, 154, 120, 78, 206, 64, 59, 70, 242, 41, 12, 220, 11, 154, 0, 71, 154, 205, 47, 137, 34, 62, 139, 95, 80, 182, 253, 121, 213, 208, 136, 170, 185, 45, 207, 22, 113, 18, 221, 127, 134, 67, 132, 112, 168, 56, 253, 236, 253, 17, 221, 110, 205, 149, 15, 155, 92, 231, 45, 143, 241, 102, 143, 42, 28, 95, 253, 252, 120, 179, 144, 104, 179, 73, 20, 45, 72, 138, 32, 130, 3, 241, 135, 3, 191, 182, 20, 179, 92, 195, 204, 255, 250, 214, 109, 210, 241, 55, 165, 154, 69, 207, 39, 108, 198, 167, 173, 202, 103, 226, 75, 170, 72, 7, 94, 207, 236, 19, 106, 164, 52, 103, 204, 169, 172, 5, 140]"}]}... DEBU[0001] Read message (type 1):5::/com.samsung.companion:{"name":"receiveCommon","args":"[222,188,199,108,97,96,91,176,23,173,149,216,225,156,86,55,48,90,240,13,255,82,50,231,208,253,167,115,215,183,37,26,133,112,55,74,47,144,224,111,65,192,149,43,112,202,38,92,49,211,86,53,54,200,110,252,134,152,54,147,218,123,231,252]"} DEBU[0001] SmartView message received DEBU[0001] data: 22726573756c74223a7b7d7d04040404 DEBU[0001] padlen: 04 DEBU[0001] plain text: []byte{0x22, 0x72, 0x65, 0x73, 0x75, 0x6c, 0x74, 0x22, 0x3a, 0x7b, 0x7d, 0x7d} DEBU[0001] Successfully decrypted response: [34 114 101 115 117 108 116 34 58 123 125 125] DEBU[0001] SmartView message: "result":{}} DEBU[0001] Reading WS message... DEBU[0001] TV message:"result":{}}`
DEBU[0001] Closing websocket

`

@McKael
Copy link
Owner

McKael commented Dec 23, 2018

Hi,
Glad to hear it (mostly) works for you :)

I'm not sure I can help, unfortunately. The KEY_POWER works for me (on a JU6000), and AFAICT the TV reply is the same... :/

@barfnordsen
Copy link

I had same issue.
Changing KEY_POWER to KEY_POWEROFF in .config/keybindings.yaml solved it for UE55H6200

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

No branches or pull requests

3 participants