Help ! Samsung TV Bindings with >2016 Samsung TV

menzy · January 28, 2020, 12:39pm

I am also using the 2.5.0 version of the binding & after a restart of Openhab it detects the power state change to ON but then nothing else gets updated. I am only using the binding to monitor the power state for rules to control lighting. I did try the bundle:restart org.jupnp above but it made no difference.

*EDIT
I may have found the root of my issue.

Under 2.5.0 my TV config in the JSONDB (org.eclipse.smarthome.core.thing.Thing.json) is as follows:

      "configuration": {
        "properties": {
          "hostName": "192.168.10.239",
          "protocol": "WebSocket",
          "port": 8001,
          "refreshInterval": 1000

But under 2.4.0 it was:

      "configuration": {
        "properties": {
          "hostName": "192.168.10.239",
          "port": 55000,
          "refreshInterval": 1000

I have manually changed the JSONDB (org.eclipse.smarthome.core.thing.Thing.json) file to what was configured in my 2.4.0 setup & it is now working again in 2.5.0.

So it may just be mis-identifying the control type for my TV?

alexxio · January 28, 2020, 2:21pm

Mine seems fine…but it does not work anyway:

"configuration": {
        "properties": {
          "hostName": "192.168.10.40",
          "protocol": "Legacy",
          "macAddress": "60:6B:BD:D1:4C:CB",
          "port": 55000,
          "refreshInterval": 1000
        }

Does yours keep working in the long run?

menzy · January 28, 2020, 11:45pm

So far it has continued to work 12+ hours later. Before it would only work for minutes at a time.

RhavoX · February 23, 2020, 11:52am

This binding seems to be badly written. I’m on 2.5.2 now and the behavior I see is that the moment I use this binding openhab goes into R state in htop (uninterruptable sleep) which doesn’t normally happen. The plugin works ok though UNTILL a restart occurs. Then it loses all ability to control my TV (usually the token is wiped and cannot be restored). Openhab usually takes a few minutes to shutdown at this point (I’m guessing it is actually killed off by systemctl because the plugin actually hangs dead). Can Any logs be provided to finally fix these issues? I don’t want workarounds to detect if the TV is on or not. I want the full functionality.

I’m guessing that for everyone that see that it stops after some time - try to configure it and restart openhab. I guess this is the point at which it stops working.

jwiseman · February 23, 2020, 2:43pm

Please be aware there are some fundamental issues with this binding and jUpNp. It was taking down my Sonos devices for over a year until we figure out it was the SamsungTV binding.

Here’s the active debug on it right now.

github.com/openhab/openhab-addons

JuPnP failing - causing devices to go offline

opened 09:17PM - 05 Aug 19 UTC

closed 07:45PM - 01 Jan 21 UTC

morph166955

bounty external bug

<a alt="bounty" href="https://www.bountysource.com/issues/80365719"><img src="ht…tps://api.bountysource.com/badge/issue?issue_id=80365719"></a> Refer to https://community.openhab.org/t/too-much-time-before-a-sonos-thing-becomes-definitively-online/62214 For no observed reason, JuPnP seems to fail randomly and cause things to go offline. Sonos speakers seem to be the biggest culprit. Once this condition is reached, all things that rely on JuPnP seem to fall offline quickly. I've seen this happen between 3 days and 2 weeks, no specific time length causes the failure. This can be mitigated currently by having a rule monitor getThingStatusInfo(mything).getStatus().toString() and when it goes offline it executes "executeCommandLine(”/usr/bin/ssh -p 8101 -i /home/openhab/karaf_keys/openhab.id_rsa openhab@localhost bundle:restart org.jupnp", 120000)"

Best, Jay

witek_1308 · March 14, 2020, 9:11pm

Hi All,
to echo previous comments, I observe lost of reliability in binding 2.5.2. What I found too is that in the jsondb file I have settings:

          "protocol": "None",
          "port": 55000,

whereas if I click on the thing settings for some reason it forces in the GUI Websocket (2016 and above) and port change 8001. Pressing OK often (not every time) breaks the thing but I didn’t see it written to the jsondb file which I intended to change as some of the guys suggested above (any I was surprised it didn’t change). Any try in the GUI of changing from Websocket/8001 to None port 55000 is unsuccessful, it still displays the same

omatzyo · March 18, 2020, 1:14pm

Losing the token is driving me nuts. I find that I can keep it working… but every time openhab restarts I have to be near the TV to accept the “new” connection with the remote. None of the settings in the TV allow for and always allow type connection.

Hopefully @arjanmels is able to take a look at this when he has some time.

Otherwise the binding seems to work well.

brizzik · March 18, 2020, 6:19pm

I found out that i had some old WOL items for my samsung tv and some old rules etc.
Because they where wrong and not working it destroyed some ports or something with the samsung and tradfri binding. After i removed al those wrong items it works like it should.

Besides that the samsung binding is still very rocky and not stable at all.
Its better with the 2.5 update then before but still not stable enough to use easily.

Jonas88 · April 4, 2020, 8:49pm

hi

how can i launch apps like netflix or yourube with this binding?
it’s working fine but i cannot find any command …

Seth_K · April 7, 2020, 7:56pm

Hi @morph166955

Any chance you have the app ID number for Disney+? Similar to the ones I have extracted from your posts.

Many thanks!

curl -X POST http://192.168.1.145:8001/api/v2/applications/3201512006963 (Plex)
curl -X POST http://192.168.1.145:8001/api/v2/applications/3201512006785 (Prime)

mstormi · April 8, 2020, 10:34am

I just revisited the binding capabilities after running it more or less unattended for some time. I think a main problem is lack of documention rather than lack of things to work, or rather the combination of this: which features work and which ones do not, and, which models is functionality eventually limited to.
And I believe this is something this community can help to enhance better than the developers themselves can do. Any developer usually has “his” TV to develop against, but has no means of testing interoperability of his works with other models at large nor a comprehensive view on all the possibilities available in the API. But that’s what a joint community effort can deliver.
So I would like to encourage everyone of you to follow this thread to help with testing and documenting. Note to contribute knowledge is as easy as posting it here, it does not have to be comprehensive statements. I guess that’s what most people believe - but every reliable piece of information will help with slowly improving things.
You as users can also (in)validate, enhance or expand the official (samsungtv binding) documentation. There’s a link at the bottom of each docs page you just need to follow.

As to my own contribution, I’m starting with the basics. To be more precise, as basic stuff like on/off is working, first thing I tried was to check through all channels that the current binding’s doc page advertises to be supported, including not-as-often-used features such as switching color temperature.

First 2 attempts were pretty demotivating right away:

2020-04-08 12:29:56.969 [WARN ] [tv.internal.handler.SamsungTvHandler] - Channel 'samsungtv:tv:69166696_9325_4504_b659_af4fe77d4843:sharpness' not supported
2020-04-08 12:30:06.308 [WARN ] [tv.internal.handler.SamsungTvHandler] - Channel 'samsungtv:tv:69166696_9325_4504_b659_af4fe77d4843:contrast' not supported

Next, a .sendCommand() worked on a colorTemperature channel which according to the docs is of Number type, so I would expect that to work, but the response below shows it does not.

Has anyone encountered the same and can shed more light onto what’s supposed to work with respect to these features ? Would they need to be rewritten to become API based ? Has anyone tried using the API to change these ?

2020-04-08 11:57:54.594 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.handleCommand()' on 'org.openhab.binding.samsungtv.internal.handler.SamsungTvHandler@195cb3c': Command '2' not supported
java.lang.NumberFormatException: Command '2' not supported
        at org.openhab.binding.samsungtv.internal.service.MediaRendererService.setColorTemperature(MediaRendererService.java:330) ~[?:?]
        at org.openhab.binding.samsungtv.internal.service.MediaRendererService.handleCommand(MediaRendererService.java:163) ~[?:?]
        at org.openhab.binding.samsungtv.internal.handler.SamsungTvHandler.handleCommand(SamsungTvHandler.java:117) ~[?:?]
        at sun.reflect.GeneratedMethodAccessor4721.invoke(Unknown Source) ~[?:?]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_222]
        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_222]
        at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:152) [bundleFile:?]
        at org.eclipse.smarthome.core.internal.common.InvocationHandlerSync.invoke(InvocationHandlerSync.java:59) [bundleFile:?]
        at com.sun.proxy.$Proxy132735.handleCommand(Unknown Source) [?:?]
        at org.eclipse.smarthome.core.thing.internal.profiles.ProfileCallbackImpl.handleCommand(ProfileCallbackImpl.java:74) [bundleFile:?]
        at org.eclipse.smarthome.core.thing.internal.profiles.SystemDefaultProfile.onCommandFromItem(SystemDefaultProfile.java:48) [bundleFile:?]
        at sun.reflect.GeneratedMethodAccessor4782.invoke(Unknown Source) ~[?:?]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_222]
        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_222]
        at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:152) [bundleFile:?]
        at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:52) [bundleFile:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_222]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_222]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_222]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_222]

Seth_K · April 9, 2020, 8:54pm

If anyone is still reading this I have solved it.

Master79 · April 10, 2020, 9:51am

Hi,
I cannot connect to websocketV2 App. SAMSUNG 7 Series.
I need a connection to a Samsung account on TV or enable developer mode?
From browser link i reach …/api/V2.
The TV is asking for connection too. But after allow the connection, the error arrives.
Any ideas?
Thanks and greetings,
Markus

Seth_K · April 10, 2020, 12:58pm

Hey,

Can you use terminal (Mac)/command prompt (Win)? Try the command below.

curl -X POST http://192.168.1.145:8001/ws/apps/Netflix

brizzik · April 10, 2020, 4:50pm

Samsung UE55NU7400S - 4K tv @mstormi

ON/OFF is working after i updated to 2.5 a while ago.
Mute is working also.

After reboot on raspberry i need to manually accept openhab on my samsung tv. I get a notification in my screen and i have to press ok on the tv.
After that the secure websocket works. But i have to do this every time i reboot openhab.

One other little problem is that turning the tv off and then on again does not work. It needs like 5 or 10 minutes to reset something. Not sure what that is.

On google home, with my tv connected trough smartthings it can instantly turn on and off again.

All other commands are not supported, when using things like mute or brightness i get this message:

2020-04-10 18:44:48.691 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.handleCommand()' on 'org.openhab.binding.samsungtv.internal.handler.SamsungTvHandler@13d8eec': Command '0' not supported

java.lang.NumberFormatException: Command '0' not supported

	at org.openhab.binding.samsungtv.internal.service.MediaRendererService.setBrightness(MediaRendererService.java:282) ~[?:?]

	at org.openhab.binding.samsungtv.internal.service.MediaRendererService.handleCommand(MediaRendererService.java:154) ~[?:?]

	at org.openhab.binding.samsungtv.internal.handler.SamsungTvHandler.handleCommand(SamsungTvHandler.java:117) ~[?:?]

	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_222]

	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_222]

	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_222]

	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_222]

	at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:152) [bundleFile:?]

	at org.eclipse.smarthome.core.internal.common.InvocationHandlerSync.invoke(InvocationHandlerSync.java:59) [bundleFile:?]

	at com.sun.proxy.$Proxy3418.handleCommand(Unknown Source) [?:?]

	at org.eclipse.smarthome.core.thing.internal.profiles.ProfileCallbackImpl.handleCommand(ProfileCallbackImpl.java:74) [bundleFile:?]

	at org.eclipse.smarthome.core.thing.internal.profiles.SystemDefaultProfile.onCommandFromItem(SystemDefaultProfile.java:48) [bundleFile:?]

	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_222]

	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_222]

	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_222]

	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_222]

	at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:152) [bundleFile:?]

	at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:52) [bundleFile:?]

	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_222]

	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_222]

	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_222]

	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_222]

For me this is enough, im happy on/off is working well.

mstormi · April 10, 2020, 7:01pm

I think you would need to store the token (as a thing property via PaperUI).
I don’t use the secure websocket and never needed a token to pair OH with the TV.

omatzyo · April 10, 2020, 7:15pm

I’ve tried this via paperui and the .things file. It never persists unfortunately.

brizzik · April 11, 2020, 7:30am

Hmmm, what token are we talking about. I have never seen any kind of token from my tv, just a little notification that ask if i want to accept openhab to control the tv yes or no.

I’m gonna look into it today if i find something

mstormi · April 11, 2020, 7:45am

never used the secure variant. Possibly it’s logged when you enable DEBUG level

Master79 · April 11, 2020, 7:58am

@Seth_K:
Yes, it works from my openhab Terminal. The TV asks again and then it starts.
Now the TV says allow a Media Decive. Out of the binding it says openhab.
Openhab is running on an Ubuntu server.
But in the logs cannot connect to webSocketV2 app.
Greetings, Markus