I’m not sure what broke, but all 4 of my TV things just failed at the same time. They won’t update any state and the state of the thing is stuck in the state it was in. What can I do to provide trace/debugs? I’m on nightly 1633 right now.
For reference, when I set logs to TRACE, I get absolutely nothing other than:
2019-07-17 15:05:06.768 [DEBUG] [covery.SamsungTvDiscoveryParticipant] - Retrieved Thing UID for a Samsung TV '[TV]Living Room' model 'QN75Q75FM' thing with UDN 'REDACTED'
2019-07-17 15:05:06.768 [DEBUG] [covery.SamsungTvDiscoveryParticipant] - Created a DiscoveryResult for device 'QN75Q75FM' with UDN 'REDACTED' and properties: {hostName=REDACTED}
openhab> log:set TRACE org.openhab.binding.samsungtv
openhab> log:get | grep samsung
org.openhab.binding.samsungtv │ TRACE
256 │ Active │ 80 │ 2.5.0.201907050419 │ openHAB Add-ons :: Bundles :: SamsungTV Binding
jwiseman
(Mr. Wiseman (OH 4.2 Snapshot on Pi4))
43
I’ve been running the native OH 2.4 Samsung binding for quite some time. All I care about with the binding if the TV is ON or OFF due to rules firing based off that status.
Based on this new binding; anything special I need to know before I upgrade it?
Do I need 2 bindings for Samsung TV (one 2015 and below and one for 2016 and above)?
In haven’t tried manual specification like you do. It could be that you need to add a key to indicate yhe binding type legacy or websocket. As I am on holidays I cannot look up thr exact syntax.
I migrated some weeks ago from the native one to this one. I use the same settings like you and I am also interested in the on/off status.
This is working for me for a 2012, 2013 and a 2019 QLED.
jwiseman
(Mr. Wiseman (OH 4.2 Snapshot on Pi4))
46
Upgraded the binding to the latest 2.5 stable build; but all my TV’s are UNKNOWN.
Do I need to connect to a different port based on newer TV’s? I don’t see the documentation online about what years should be using a different port than the 55000?
Here’s my log file . . .
2019-08-04 17:48:33.837 [INFO ] [rnal.service.RemoteControllerService] - Using None interface
2019-08-04 17:48:33.852 [INFO ] [rnal.service.RemoteControllerService] - Using None interface
2019-08-04 17:48:33.867 [INFO ] [rnal.service.RemoteControllerService] - Using None interface
2019-08-04 17:48:33.885 [INFO ] [rnal.service.RemoteControllerService] - Using None interface
2019-08-04 17:48:33.899 [INFO ] [rnal.service.RemoteControllerService] - Using None interface
2019-08-04 17:48:33.914 [INFO ] [rnal.service.RemoteControllerService] - Using None interface
2019-08-04 17:48:33.927 [INFO ] [rnal.service.RemoteControllerService] - Using None interface
I’m not sure what is causing this, but it’s still happening. I believe it may be related to https://github.com/openhab/openhab2-addons/issues/5892 that I opened a month ago. If I restart the org.jupnp service it semi-fixes this but I end up having to completely restart openhab to get this stable.
EDIT: Apparently it didn’t clip my original post. I was referring to all of my TV things just ceasing to get state changes. I would believe that it’s somehow related to JuPnP. I’ve also noticed that I still get the occasional pop-up when the TV powers on that openHAB wants to connect.
@arjanmels,
I tested and can change to different HDMI (ex HDMI 1, 2, 3 or 4) with discrete IR codes.
So I think it would be plausible to do this via this binding as well via websockets.
Does the binding show everything that the TV broadcast via websockets?
Then maybe you could add that bit so we can trace it in the logs?
Or am I thinking wrong?
Using (on android) “Samsung TV remote”, there I can see all the applications that are installed. So that should also be possible.
I know you might not have the time, but I’m just asking.
I will continue to use google-foo and see if I can manage to get some information that can help.
KEY_HDMI works but toggles the different HDMIs.
But selecting a HDMI1, 2, or 3 directly does not work.
Since discrete IR codes work, I think via websocket should work as well.
Maybe the code is KEY_HDMI_1 etc.
I’ll try some different combos, but this is a needle in a haystack
EDIT: Its not possible to have own combos, the binding throws error its not a key.
@arjanmels, how do you send the command, do you send it with the comman KEY_HDMI or do you send the the value that corresponds to KEY_HDMI?
If so, can you check if the value is really 1205 and 1206 for HDMI 2 respective HDMI3?
From googling this everyone is saying you can’t choose HDMI input this way, but it seems odd that it works via IR.
What I ment with “everyone” is that all similar projects I’ve come across seems to use KEY_HDMIx but the ‘projects’ state that it does not work on all TV models.
Ex samsungctl.
I found on samsung developer site (can’t remember where) that the KEY_HDMI (etc) is represented by an ID (in this case 1205 and 1206 was hdmi2 and 3).
@sintei I happen to have the same TV as you (Q6FN) and get weird behavior from the binding with the current 2.5.0.M3 version:
I do not get the current app, source name etc.
I can turn off, but not turn on. Exception: There is a certain set of actions after which turning off does turn on the TV, e.g. if it thinks the TV is on (but failed due to wake on LAN somehow not working). If needed, I can try to explain in detail and post logs. This tells me that somehow it must be possible to turn on the TV, but the binding does not do it correctly. Also, it seems that it turns on even when not sending wake-on-lan but tries to turn off?! I am lost here.
Detection of power on/off works.
I can change the volume most of the time.
@sintei Does turning on and off work for you without hassle? Do you see similar problems?
Also I want to add that I added the MAC of the TV manually, because otherwise an error about missing MAC address appeared in the logs.
Having trouble with a 2017 UN65MU8000. I can get it’s on off status to be recognized under the thing page, but as you can see from the log, it doesn’t like my colorTemperature inputs. I can select a mapping via my iPhone & see the mapping change on PaperUI, but nothing is changing on the TV. Any ideas??? Thanks!
Here’s my item:
//Samsung TV
Number SamsungTV_ColorTemp “ColorTemp” { channel=“samsungtv:tv:colorTemperature” }
modelName "UN55MU6300"
Nmap scan report for 10.10.5.118
Host is up (0.0024s latency).
Not shown: 8281 closed ports
PORT STATE SERVICE
1908/tcp filtered dawn
3740/tcp filtered heartbeat
5339/tcp filtered unknown
5456/tcp filtered apc-5456
7676/tcp open imqbrokerd
8001/tcp open vcom-tunnel
8002/tcp open teradataordbms
8080/tcp open http-proxy
9119/tcp open mxit
9197/tcp open unknown
9999/tcp open abyss
32768/tcp open filenet-tms
32769/tcp open filenet-rpc
32770/tcp open sometimes-rpc3
32771/tcp open sometimes-rpc5
MAC Address: F8:3F:51:7C:92:94 (Samsung Electronics)
jwiseman
(Mr. Wiseman (OH 4.2 Snapshot on Pi4))
58
Here’s my config and it seems to be working “most” of the time.
What Samsung TV binding version do you use and which Java have you installed? It doesn’t work for me (author didn’t promise it to work with U and 6 generation). I do not know if samsungctl is used in this binding but that currently published version of the samsungctl is not working with Python 3.7 either.
jwiseman
(Mr. Wiseman (OH 4.2 Snapshot on Pi4))
60
Binding Version:
openhab> list -s | grep samsung
232 │ Active │ 80 │ 2.5.0.201908041228 │ org.openhab.binding.samsungtv
I’m using Java 8.
Let me know if I can help in any other way. I understand the frustration that happens when trying to get something to work that someone else has working.
