Samsung Smart TV Switch

#1

1) Give a description of the problem
Trying to turn an outlet on/off based on TV switch status

2) What is the expected behaviour?
Switch turns on/off

3) What is happening/not happening?
Doesn’t appear DTH recognizes ‘switch’ off command from remote.

**4) Post a Green Snapshot of the piston!

download
download.png1178×466 40.9 KB

5) Attach logs after turning logging level to Full
Logs aren’t helpful here:

Hello everyone, have spent hours trying to toy with this and search the boards, can’t find any definitive solution or lack thereof. I have a 2019 samsung smart TV, I’ve tried the 2015/2016 Samsung Smart TV, Samsung OCF Smart TV, and Samsung Smart TV DTHs, all seem to be the same (although it returns a heck of a lot more states on OCF). The ‘switch’ state doesn’t seem to virtually turn off when the TV is turned off by basic infrared remote. On works just fine. Anyone know the deal here? Not really looking to jerry rig it with a watt meter or Harmony remote, but I’ll probably go that avenue if it’s the only solution. Any help is much appreciated.

#2

The logs might give us some insight.

#3

I have two Samsung TVs a 2016 and 2020, I had the 2016 model connect during the migration from classic. Prior to that I was using the OCF DTH but noticed some reliability issues. I disconnected and reconnected using the V3 app. Functionality has improved BUT if you look in IDE, it only has a placeholder listing as the DTH yet Webcore is still able to subscribe to certain events/states including the switch.

Might be time to consider resetting the connection to ST.

#4

Well, if I re-add the TV, you are correct it will have the placeholder DTH, but then the device won’t show up as a physical device in WebCore, nor are there any states reported in ST. Interesting this isn’t the same case for you…

Edit: Forgot to re-add device in WebCore, will report back soon

#5

Are you able to find it as an available device when adding it to the WebCore SmartApp…it took me a while to find but it is listed in capability group 3 under switches.

#6

6/22/2021, 10:40:17 AM +798ms
+1ms ╔Received event [Dave’s House].test = 1624372817798 with a delay of 0ms
+55ms ║RunTime Analysis CS > 16ms > PS > 5ms > PE > 33ms > CE
+58ms ║Runtime (36644 bytes) successfully initialized in 5ms (v0.3.113.20210203) (56ms)
+60ms ║╔Execution stage started
+83ms ║║Comparison (enum) on is (string) off = false (2ms)
+85ms ║║Condition #2 evaluated false (19ms)
+86ms ║║Condition group #1 evaluated false (state did not change) (20ms)
+91ms ║╚Execution stage complete. (30ms)
+92ms ╚Event processed successfully (92ms)

No change when re-adding device and using placeholder DTH. I think the bottom line is the remote off doesn’t trigger a change to the switch state. Don’t think there’s much more that can be done

#7

That log is from running a test…just to clarify…the TV is actually OFF when you hit test and it reports as still on?

Do you see the switch event in IDE?

This is my 2016

image
image.png1253×167 10.8 KB

Wondering if it is your trigger, currently written as a condition (Switch is Off), maybe try the actual trigger of changes to Off. WebCore will treat conditions as trigger if it is the only condition but it might not be subscribing correctly.

#8

That’s correct, I don’t see the switch status change in IDE when using the remote, so it’s probably a ST or TV reporting issue and not WebCore, oh well, thanks for everyone’s help. I’ll probably just get a receptacle power meter and use that to trigger events