FYI to the binding owners. [SamsungTV] Several Thread Issues · Issue #9495 · openhab/openhab-addons · GitHub was opened earlier as a byproduct of looking into other thread issues. Kai found a few issues where this binding is causing issues with UPnP.
Does anybody know why the Samsung QLED 4K The Frame (GQ65LS03TAUXZG) does not support the ArtMode although it is probably the TV for presenting Art with an embedded art galery as a subscription?
[tv.internal.handler.SamsungTvHandler] - Channel 'samsungtv:tv:00071a0c_b05d_4905_a178_9766f9820c46:artMode' not supportedIt does on my 65 inch 2020 The Frame.
On my 2019 Q90R, the artmode channel switch powers off my TV (when operated from the paperUI). Maybe it is a 2019 thing?
If I start the art mode with the TV remote, the ArtMode channel switch in openhab also does not switch on in my case.
Or is the artmode still something different and not present on a non-frame? I do have an ‘ambient mode’ with several (moving) wallpapers on my flagship 2019 q90r.
I just realised, my mistake, the rest didn’t work either. The wrong port was enough to display the volume, but only with the correct port was it possible to send commands. Thanks.
Hi, I did some more testing and I figured out that my problem of the TV not responding to commands was due to the fact that, after the wake on LAN, I started the apps through calling a python script, which was making a separate connection, probably confusing the TV. (I used this before the samsung binding was updated, there was no other way of controlling it before the binding enabled the secure websocket connection with tokens.)
I changed this to use the sourceApp channel in the binding and that worked good for a few days.
I do get an error now when starting an app like that: (it was probably there right away, but I was not monitoring the logs)
WebSocketRemote: Error (java.lang.IllegalStateException: Expected BEGIN_OBJECT but was NUMBER at line 1 column 12 path $.data) in message: {"data":200,"event":"ed.apps.launch","from":"host"}
com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was NUMBER at line 1 column 12 path $.data
at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:224) ~[bundleFile:?]
at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:129) ~[bundleFile:?]
at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:220) ~[bundleFile:?]
at com.google.gson.Gson.fromJson(Gson.java:888) ~[bundleFile:?]
at com.google.gson.Gson.fromJson(Gson.java:853) ~[bundleFile:?]
at com.google.gson.Gson.fromJson(Gson.java:802) ~[bundleFile:?]
at com.google.gson.Gson.fromJson(Gson.java:774) ~[bundleFile:?]
at org.openhab.binding.samsungtv.internal.protocol.WebSocketRemote.onWebSocketText(WebSocketRemote.java:94) [bundleFile:?]
at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onTextMessage(JettyListenerEventDriver.java:231) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.websocket.common.message.SimpleTextMessage.messageComplete(SimpleTextMessage.java:69) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.appendMessage(AbstractEventDriver.java:65) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onTextFrame(JettyListenerEventDriver.java:179) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.incomingFrame(AbstractEventDriver.java:150) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.websocket.common.WebSocketSession.incomingFrame(WebSocketSession.java:321) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.websocket.common.extensions.ExtensionStack.incomingFrame(ExtensionStack.java:202) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.websocket.common.Parser.notifyFrame(Parser.java:226) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.websocket.common.Parser.parseSingleFrame(Parser.java:262) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.readParse(AbstractWebSocketConnection.java:582) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:441) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:428) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:426) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:320) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:158) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:367) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:782) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:918) [bundleFile:9.4.20.v20190813]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_221]
Caused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was NUMBER at line 1 column 12 path $.data
at com.google.gson.stream.JsonReader.beginObject(JsonReader.java:385) ~[bundleFile:?]
at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:213) ~[bundleFile:?]
... 34 more
The app does start, but there is a delay.
I searched the forum and found this post with exactly the same problem, but it was closed off without a solution: https://community.openhab.org/t/samsung-smart-tv-error/99895
Does anyone have any idea on how to get rid of this error? (It would result in a more responsive setup in my case (no delay of 4sec for starting an app).)
I have a 2019 TV (UE50MU6120) on a wired network. I can power on via WoL, power off via the samsungtv binding and control volume. Yay.
But I’d really like to be able to see the playing source.
Samsung’s preferred Android mobile app for controlling/monitoring the TV now seems to be SmartThings. This does show the playing source app or (for live TV) channels.
@arjanmels Any idea how it’s doing this? Is this something that could be included into the binding?
I have a 43" Samsung Frame and a 50" Samsung Frame in use with the binding, with mixed results.
OH3.0.0 docker, on a Ubuntu host. TVs are connected by Ethernet cables, not WiFi (my AT&T router didn’t seem to like the TV WiFi for whatever reason…).
Both are properly detected, and the secure token is added. The token doesn’t persist across reboots (/restarts of the docker container I use for openHAB), but this isn’t a show stopper - I don’t mind selecting ‘Allow’ the next time the TV turns on.
Volume and mute seem to work fine when the TV is on.
The main commands I would like to suss out are Power on / off and art mode. I get errors in the openHAB logs occasionally, and after this I need to disable and re-enable the thing to get it back to ‘normal’.
Example of an error when going from OFF to Art Mode:
2021-01-30 15:27:35.905 [INFO ] [rnal.service.RemoteControllerService] - Using SecureWebSocket interface
2021-01-30 15:27:35.951 [INFO ] [tv.internal.handler.SamsungTvHandler] - Service found after 2 attempts: resend command ON to channel artMode
2021-01-30 15:27:35.952 [WARN ] [ngtv.internal.protocol.WebSocketBase] - WebSocketRemote sending command while socket not connected: {"method":"ms.remote.control","params":{"Cmd":"Click","DataOfCmd":"KEY_POWER","Option":"false","TypeOfRemote":"SendRemoteKey"}}
2021-01-30 15:27:35.953 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
java.lang.NullPointerException: null
at org.openhab.binding.samsungtv.internal.protocol.WebSocketBase.sendCommand(WebSocketBase.java:119) ~[?:?]
at org.openhab.binding.samsungtv.internal.protocol.WebSocketRemote.sendKeyData(WebSocketRemote.java:224) ~[?:?]
at org.openhab.binding.samsungtv.internal.protocol.RemoteControllerWebSocket.sendKeyData(RemoteControllerWebSocket.java:331) ~[?:?]
at org.openhab.binding.samsungtv.internal.protocol.RemoteControllerWebSocket.sendKey(RemoteControllerWebSocket.java:265) ~[?:?]
at org.openhab.binding.samsungtv.internal.protocol.RemoteControllerWebSocket.sendKey(RemoteControllerWebSocket.java:250) ~[?:?]
at org.openhab.binding.samsungtv.internal.service.RemoteControllerService.sendKeyCode(RemoteControllerService.java:413) ~[?:?]
at org.openhab.binding.samsungtv.internal.service.RemoteControllerService.handleCommand(RemoteControllerService.java:311) ~[?:?]
at org.openhab.binding.samsungtv.internal.handler.SamsungTvHandler$2.run(SamsungTvHandler.java:421) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
However, the TV will then allow me to turn Art Mode off.
When I try and turn it back on, however, I get the below:
2021-01-30 15:31:09.483 [INFO ] [tv.internal.handler.SamsungTvHandler] - Send WOL packet to 192.168.1.80 (bc:7e:8b:ed:53:a3)
2021-01-30 15:31:09.484 [WARN ] [tv.internal.handler.SamsungTvHandler] - Channel 'samsungtv:tv:a2aebcfe_e93e_4ad7_879f_be1a40578ace:artMode' not supported
And then the TV Thing goes offline. After this, it will sometimes work again by stopping and restarting the thing, sometimes I have to restart openHAB.
Also worth noting that I’m unable to use the curl -X POST commands mentioned above - I always get either a 401 or 404 error.
If anyone has experienced something similar, I would be grateful for any tips on how to further troubleshoot! Thank you in advance!
Hi,
I am not sure what these errors you posted mean, but I can tell you for sure WOL is not supported by Samsung TVs, even in the Smart Things app. So if you have your TV on Ethernet try switching to WiFi.
I am using with The Frame 43 for a while now and it works fine.
Good luck.
Hi Gustavo,
It’s strange you say that - I was experimenting with using WoL to wake the TV up from another program on the same device(to see where the issue might be arising), and WoL from the other program works fine… where did you see the reference that WoL isn’t supported?
Hi all,
is there any update on TV models supported by the Samsung tv binding? I have GQ55Q80 model.
Thanks a lot.
Matthias
I’m very interested in be able to know power status of a 2021 Samsung TV too. Is there any beta binding or any other way to just get that channel?
The standard samsungtv binding on port 8002 gives that functionality on my 2020 model QLED. Its one of the few things that work
Thanks @kevin, by knowing the issue was in my end and not in the binding helped me a lot. I uninstalled the binding, rebooted and installed it again and seems it is working now. I tried it before but didn’t work and it also vanished all the other bindings, so I had to reinstall them all (very weird), that’s why I thought this route wouldn’t solve the issue as it did
I don’t know why it stopped working and why it did not fix when I firstly reinstalled the binding, but I’m glad is is working now. I have a lot of automation associated to the TV turn off after evening (“Go to bed” sequence) and it was very annoying not having it after you get used to just turn off the TV and expect everything to happen magically
What a pity… I thought it was fixed but it continues failing. But this time I catch the debug log of the TV thing by removing by itself and then reappearing. This explains why the TV was suddenly offline and then back online.
2021-05-03 22:27:16.939 [DEBUG] [rnal.service.RemoteControllerService] - Received channel: power, command: REFRESH
2021-05-03 22:27:17.941 [DEBUG] [rnal.service.RemoteControllerService] - getSupportedChannelNames: [keyCode, volume, mute, power, channel, url, sourceApp, artMode]
2021-05-03 22:27:17.943 [DEBUG] [rnal.service.RemoteControllerService] - Received channel: power, command: REFRESH
2021-05-03 22:27:18.945 [DEBUG] [rnal.service.RemoteControllerService] - getSupportedChannelNames: [keyCode, volume, mute, power, channel, url, sourceApp, artMode]
2021-05-03 22:27:18.947 [DEBUG] [rnal.service.RemoteControllerService] - Received channel: power, command: REFRESH
2021-05-03 22:27:19.949 [DEBUG] [rnal.service.RemoteControllerService] - getSupportedChannelNames: [keyCode, volume, mute, power, channel, url, sourceApp, artMode]
2021-05-03 22:27:19.950 [DEBUG] [rnal.service.RemoteControllerService] - Received channel: power, command: REFRESH
2021-05-03 22:27:20.474 [DEBUG] [covery.SamsungTvDiscoveryParticipant] - Retrieved Thing UID for a Samsung TV '[TV] Samsung Q80 Series (65)' model 'QE65Q82TATXXC' thing with UDN '7b254216_6a3d_4f5d_95a5_a9d1417a42f3'
2021-05-03 22:27:20.474 [DEBUG] [nternal.service.MediaRendererService] - onStatusChanged: status=false
2021-05-03 22:27:20.477 [DEBUG] [tv.internal.handler.SamsungTvHandler] - Thing Removed: samsungtv:tv:7b254216_6a3d_4f5d_95a5_a9d1417a42f3
2021-05-03 22:27:20.482 [DEBUG] [tv.internal.handler.SamsungTvHandler] - Shutdown all Samsung services
2021-05-03 22:27:20.485 [DEBUG] [l.protocol.RemoteControllerWebSocket] - RemoteControllerWebSocket close
2021-05-03 22:27:20.488 [DEBUG] [l.protocol.RemoteControllerWebSocket] - RemoteControllerWebSocket closeConnection
2021-05-03 22:27:20.495 [DEBUG] [ngtv.internal.protocol.WebSocketBase] - WebSocketRemote connection close requested
2021-05-03 22:27:20.499 [DEBUG] [ngtv.internal.protocol.WebSocketBase] - WebSocketArt connection close requested
2021-05-03 22:27:20.500 [DEBUG] [ngtv.internal.protocol.WebSocketBase] - WebSocketRemote connection closed: 1000 - null
2021-05-03 22:27:20.504 [DEBUG] [ngtv.internal.protocol.WebSocketBase] - WebSocketV2 connection close requested
2021-05-03 22:27:20.507 [DEBUG] [ngtv.internal.protocol.WebSocketBase] - WebSocketV2 connection closed: 1006 - Disconnected
2021-05-03 22:27:20.510 [DEBUG] [ngtv.internal.protocol.WebSocketBase] - WebSocketArt connection closed: 1006 - Disconnected
2021-05-03 22:27:20.529 [INFO ] [.openhab.core.model.script.BlackBeam] - Turning OFF GF_LR_HiFiAmplifier as TV is turning OFF
2021-05-03 22:27:20.537 [INFO ] [.openhab.core.model.script.BlackBeam] - GF_LR_HiFiAmplifierActions ReceivedCommand=0
2021-05-03 22:27:20.542 [INFO ] [.openhab.core.model.script.BlackBeam] - >>GF_LR_HiFiAmplifier_OFF
2021-05-03 22:27:20.755 [DEBUG] [covery.SamsungTvDiscoveryParticipant] - Retrieved Thing UID for a Samsung TV '[TV] Samsung Q80 Series (65)' model 'QE65Q82TATXXC' thing with UDN '7b254216_6a3d_4f5d_95a5_a9d1417a42f3'
2021-05-03 22:27:20.756 [DEBUG] [covery.SamsungTvDiscoveryParticipant] - Created a DiscoveryResult for device 'QE65Q82TATXXC' with UDN '7a254218-6a3d-4f5d-95a7-a9d1517e42f3' and properties: {hostName=192.168.0.60}
2021-05-03 22:27:20.758 [DEBUG] [tv.internal.handler.SamsungTvHandler] - thingDiscovered: 192.168.0.60, DiscoveryResult [thingUID=samsungtv:tv:7b254216_6a3d_4f5d_95a5_a9d1417a42f3, properties={hostName=192.168.0.60}, representationProperty=hostName, flag=NEW, label=[TV] Samsung Q80 Series (65), bridgeUID=null, ttl=-1, timestamp=1619987240756]
2021-05-03 22:27:20.759 [DEBUG] [tv.internal.handler.SamsungTvHandler] - thingDiscovered, thingUID=samsungtv:tv:7b254216_6a3d_4f5d_95a5_a9d1417a42f3, discoveredUID=samsungtv:tv:7b254216_6a3d_4f5d_95a5_a9d1417a42f3
2021-05-03 22:27:20.760 [DEBUG] [tv.internal.handler.SamsungTvHandler] - Check and create missing UPnP services
2021-05-03 22:27:20.761 [DEBUG] [nternal.service.MediaRendererService] - Creating a Samsung TV MediaRenderer service
2021-05-03 22:27:20.761 [DEBUG] [tv.internal.handler.SamsungTvHandler] - Started service for: QE65Q82TATXXC, MediaRenderer (7a254218-6a3d-4f5d-95a7-a9d1517e42f3)
2021-05-03 22:27:20.766 [DEBUG] [rnal.service.RemoteControllerService] - Creating a Samsung TV RemoteController service: false
2021-05-03 22:27:20.768 [INFO ] [rnal.service.RemoteControllerService] - Using SecureWebSocket interface
2021-05-03 22:27:20.773 [DEBUG] [l.protocol.RemoteControllerWebSocket] - RemoteControllerWebSocket start Client
2021-05-03 22:27:20.783 [DEBUG] [ngtv.internal.protocol.WebSocketBase] - WebSocketRemote connecting to: wss://192.168.0.60:8002/api/v2/channels/samsung.remote.control?name=b3BlbkhBQg==&token=87690442
2021-05-03 22:27:20.784 [DEBUG] [ngtv.internal.protocol.WebSocketBase] - WebSocketArt connecting to: wss://192.168.0.60:8002/api/v2/channels/com.samsung.art-app?name=b3BlbkhBQg==
2021-05-03 22:27:20.787 [DEBUG] [ngtv.internal.protocol.WebSocketBase] - WebSocketV2 connecting to: wss://192.168.0.60:8002/api/v2?name=b3BlbkhBQg==
2021-05-03 22:27:20.952 [DEBUG] [rnal.service.RemoteControllerService] - getSupportedChannelNames: [keyCode, volume, mute, power, channel, url, sourceApp, artMode]
2021-05-03 22:27:20.953 [DEBUG] [rnal.service.RemoteControllerService] - Received channel: power, command: REFRESH
2021-05-03 22:27:21.050 [DEBUG] [ngtv.internal.protocol.WebSocketBase] - WebSocketRemote connection established: 192.168.0.60
2021-05-03 22:27:21.954 [DEBUG] [rnal.service.RemoteControllerService] - getSupportedChannelNames: [keyCode, volume, mute, power, channel, url, sourceApp, artMode]
2021-05-03 22:27:21.955 [DEBUG] [rnal.service.RemoteControllerService] - Received channel: power, command: REFRESH
2021-05-03 22:27:22.382 [DEBUG] [tv.internal.protocol.WebSocketRemote] - Remote channel connected. Token = null
2021-05-03 22:27:22.410 [DEBUG] [ngtv.internal.protocol.WebSocketBase] - WebSocketArt connection established: 192.168.0.60
2021-05-03 22:27:22.490 [DEBUG] [ungtv.internal.protocol.WebSocketArt] - Art channel connected
2021-05-03 22:27:22.492 [DEBUG] [ngtv.internal.protocol.WebSocketBase] - WebSocketV2 connection established: 192.168.0.60
2021-05-03 22:27:22.560 [DEBUG] [sungtv.internal.protocol.WebSocketV2] - V2 channel connected. Token = null
2021-05-03 22:27:22.957 [DEBUG] [rnal.service.RemoteControllerService] - getSupportedChannelNames: [keyCode, volume, mute, power, channel, url, sourceApp, artMode]
2021-05-03 22:27:22.958 [DEBUG] [rnal.service.RemoteControllerService] - Received channel: power, command: REFRESH
2021-05-03 22:27:23.960 [DEBUG] [rnal.service.RemoteControllerService] - getSupportedChannelNames: [keyCode, volume, mute, power, channel, url, sourceApp, artMode]
Any idea on what can be wrong with the binding? It was working flawlessly for long time and it is failing for the last month or two. I even upgraded the TV because I thought it was because the old one was failing
I’m using a wired connection. Is it possible you have momentary dropouts in your WiFi that is upsetting it?
I’m using wired connection too, and even fixed ip (given via dhcp)), and even if I did, it should not remove the item but rater just mark it as offline. But the log states “Thing Removed: samsungtv:tv:7b254216_6a3d…” what is really weird for me
Hello there!
I do also face issues after updating to the latest snapshot.
My tv did not ask me again for authorization. i removed the old ones (made some significant changes).
Everything seems to work but the power state (the most important for me).
first i got an error (mac address wol-package). after adding the mac address in the things file i do not get an error anymore but the tv cannot be started or shut down via openhab nor does it update the switch if i turn on/off the tv with the remote.
can i trigger the authorization on my tv again somehow?
I rebooted several times but the authorization prompt never showed up again on my tv.
EDIT: I am using a 2019 “The Frame”
EDIT2: It doesnt seem to aquire a token from my tv (checked the advanced options in paperui although i am using textual configuration. )
i can only read values but not write. for power it does not read at all.
EDIT2: It doesnt seem to aquire a token from my tv (checked the advanced options in paperui although i am using textual configuration. )
I have had similar issues as this, and after many hours I am able to reproduce the error. I discovered that the missing token always happens when Openhab was restarted with the TV powered on. I don’t restart often (if ever), but it happened after an Ubuntu update that needed a reboot, and through testing I was able to reproduce. My fix:
- Clearing out authorizations on the TV and powering off.
- Delete TV thing (restart Openhab if you like, but should not matter)
- Start scan in binding
- Power on TV, Openhab should discover so you can add it
- Authorization should be on TV screen
May not work for you, as I am on OH3 (stable) and do not use text files. A restart of Openhab with TV powered off does not produce the token error on my system.
1 Like
Hi
over night it seemed to heal itself (maybe the tv was not in deep sleep before).
So it asked me again today. Everything working fine again 