Not the volume. That value comes from the SmartThing interface whilst switch (on/off) come from the local interface. Are you willing to do a special code . It will be instrumented for determining on/off value anomalies as well as SmartThings changes.
Niew Router?? Check the protection capabilities on your router. It may be protecting your TVs (but not al).
Ok, sending you the logs for one of my three TV's not working... In the logs, it appeared to show the TV getting the commands off and on, and the TV was turning on and off, but the status always remained off in the hubitat instance...
I will assist if I can.
Are you looking for a specific TV model? Or any TV model is fine?
Need real ST hub or just the cloud account? I do jot own a real ST hub
Got the data I needed.
Test update available.
Location: - https://raw.githubusercontent.com/DaveGut/Test-Code/master/Samsung_TV_Remote_Test.groovy
Problem: Certain early TVs do not update switch.
Cause: Data not available on interface (but expected)
Change: If preference "use SmartThings..." is enabled, use the poll SmartThings for the switch value every poll interval. Otherwise use current method (and some older TVs will not be able to detect power on unless Hubitat is used for the commands.)
Problem: SmartThings volume not updating.
Cause: SmartThings did not update the data. reason unknown.
Change: none.
Thanks for the quick update! I have the SmartThings connection in play, and have since you first introduced it, but I have an issue that makes it unreliable...
I don't know about the rest of you, but my TV's, (10 of them between multiple locations) routinely fall off SmartThings every few weeks/months. I have to manually delete the TV in the app and re-add it... Some TV's stay on longer than others, including a couple that have never dropped off...
I'm just worried the more we rely on the SmartThings connection, the more unreliable this becomes. The local commands work flawlessly... Is there no way to determine if the set is on or off locally? I believe that's the way you had it working back toward the beginning... 
Not reliably and there were a lot of squawks on Art Mode turning off in the middle of the night. Aside from the port 8001/api/v2 interface, smartthings is the only way to determine power on/off.
I will be thinking about it some more, but not a lot I can do.
Well not trying to start a battle with the others here, but none of my 10 TV's have art mode... 
Your original drivers without art mode worked reliably perfect for me.
Anyway, this new driver seems to have fixed the issue for me... Of course, I went through and made sure the connections with my TV's and SmartThings were all refreshed... So now its a waiting game to see when they fall off, if this still works...
Thanks again for all your hard work!
And that is where the trouble starts. It is not on the remote nor in SmartThings to automatically load Ambient/Art mode. As I write the driver for the hubiThings (an event-based ecosystem for people coming over from SmartThings with orphaned devices), I will remember this.
Same here. I have never used the Samsung hub integration, and I swear volume and on/off states worked previously. I don't use this every day, but do use the Hubitat control via Dashboard maybe once a week to change volume on the TV when I am in another room or turn it off if someone left the TV on. it is possible I am imagining things, but I really do think it did work correctly at one point.
It is being worked. Everyone please stop dumping on me.
Hey Dave,
We are sorry... Seriously, you tackled something extremely complex and we are very very thankful for you doing it. I have been able to do some really cool things with your drivers. So, again, thank you... Take break and forget about this one for a while...
Not dumping on you, really! It is hard to read tone through the screen, so don't take what we said as trashing your work. That was totally not my intent, sorry if you took offense.
In my case I was just trying to give you background as to what I believe I experienced so maybe you can pinpoint whatever changed. Sorry again for any troubles, I won't post again.
Overly sensitive developer~!
Seriously no biggie brother... Just like @neonturbo said, we both think it was working locally before the addition of the frame stuff... And the frame stuff is cool, glad you got it working for the folks who need it...
I'm working on the volume data dump you asked me for... Its really more of an issue for neonturbo, but he doesn't do the ST integration, so I'll run the test and send you the data...
I use your driver and status of the TV's on or off for a lot of automatons. I originally bought all Samsung TV's cause I naively thought they would be the best in terms of technology... 
Boy was I wrong! But you cracked the code and got them working for us, so again I say, thanks and cheers to all your hard work!
Hi,
I have tried the new driver and could not get this working i.e. same issue on/off state not updating. This time around, the on state is permanently on and does not change.
Moving forward, could l kindly make a suggestion?
Would it be possible please to simply release two drivers?
This would save you a lot of back-n-fourth effort and would allow others like me to reinstall the old driver to get our automations working again for the older Samsung TV's.
I think l speak for most of us to say that there is no shame (certainly not from my side) in having two drivers released, as this would address the issue now and would also save you some time trying get things working into a single driver. I appreciate that you (being a perfectionist ) would like to getting everything all tied up and working in the one driver to work for all Samsung TV's.
Could you please give this some thought..
I do appreciate your time and how quickly that you have jumped onto this when l had originally raised this issue, which was also echoed by others shortly after.
Thanks again for your effort and perseverance!!
BTW: I couldn't locate the older drivers on GitHub as the driver l located was created in Dec'22
Hello,
I just installed driver and the only issue I'm having is when I press HDMI in device page it takes me to antenna input.2017 samsung tv.Any ideas?
Press it again. What that key does is cycle through the various input. It is a remote command key and will do whatever Samsung has programmed it to do. (on my tv, it will cycle through all active inputs (digitalTV, HDMI1, HDMI2). For your tv, the antenna is a active input.
Thanks so much that does work.Is it posible an a RM rule to tell it to press it twice so I can get to the HDMI input I want? Thanks again
Instead of pressing the HDMI button several times to get to the source you want, use the Set Input Source. Imputing the Source you want.
Download the Hubitat app
