Thanks I will give a fresh install a shot.
I’ve been having this issue.
I’ve added a line to the setPowerOnMode function to re connect the web socket. So whenever the driver detects the TV has been switched on, it’s ensures the socket is open.
I believe the issue was the socket was remaining closed and the invocation of the off function was not opening the socket and then sending the command as you’d expected.
So now, as long as the off command is sent 5+ seconds after the TV was detected as being on, it seems to be reliable.
I’m not sure why the behaviour changed or if my fix is reasonable but it seems to be working.
Hopefully Dave will be feeling better soon and can tell me if I’m nuts or not!
And on that note, no pressure Dave, focus on you and getting back to full health.
Solved. TV remote button in the actual Frame TV power menu config was set to ON/OFF. Changing this to ART MODE/TV seems to stop this behavior. Of course, now the physical remote power button doesn't turn the TV ON/OFF though.
Original Issue...
This is an awesome driver. I just recently bought a Samsung Frame TV so I'm still working out controlling it.
What I have notice is that when I turn it on with the Art Mode option it comes on for about 10-15 seconds and then turns back off. If I then send another ON command...it comes on and stays on. Here is the log. I'm assuming I have something set wrong. Any ideas?
THANKS!
dev:6212024-11-20 02:01:06.168 PMinfoReal Frame TV-2.3.9b: on: [frameTv: true]
dev:6212024-11-20 02:00:56.326 PMinfoReal Frame TV-2.3.9b: artMode: [artModeStatus:null, artModeWs:null, status:Sending Power WS Command]
dev:6212024-11-20 02:00:55.301 PMinfoReal Frame TV-2.3.9b: setPowerOnMode: [tvPwrOnMode: ART_MODE]
dev:6212024-11-20 02:00:46.255 PMinfoReal Frame TV-2.3.9b: on: [frameTv: true]
dev:6212024-11-20 02:00:31.071 PMinfoReal Frame TV-2.3.9b: setPowerOfMode
dev:6212024-11-20 02:00:27.762 PMinfoReal Frame TV-2.3.9b: off: [frameTv: true]
Steps to create logs
Click Off
Click On
Click On again
Wondering if it is the line w/ the "null" in it?
Finally solved the issue of the log reporting an Auto Config change to the TV every single minute.
Based on @bertabcd1234 advice in this thread:
I decided to do something similar and delete the scheduled task. This definitely got rid of the error every minute. It also got rid of the TV being connected to HE. I then clicked the configure and refresh buttons, which restored the connection between the TV and HE. It is now working without the every minute log data.
3 Likes
Hey there,
I have a Frame TV 2024 and if I enable the debug information for 30 minutes I'm able to get the Art Mode Status almost instantly.
Is it possible to obtain this value without the debug information? Also, is it possible to save the art mode status state to an attribute?
I know that the in the 2022 model Samsung removed this after an uptade but sound like in the 2024 model they bring this fearure back!
Have you checked to see if you can get the status without debug on, and immediately after an "initialize" command?
Dave, Great work on this driver.
I have a 2022 Frame TV. It appears that in the latest driver release, artmodews no longer appears as custom attribute that can be used in rules. Was a change made to the code that prevents that from being exposed? Or am I just missing something?
I removed and reinstalled the driver just to be sure—same behavior.
Hi Dave! I've been using your driver since 2021 and I am a big fan!
I use it in combination with Alexa, so I usually can control the tv via Alexa seamlessly. However, at some point last year this integration stopped working. I updated the driver to the latest version and I see I that I can control the TV via Hubitat device page, however, commands via Alexa no longer work. I noticed that before Alexa would recognise my TV as an Actual TV, but now it recognises as a switch.
Have you or anybody else experienced this problem?
The integration has stopped working with my 2022 Frame TV too. I'm not sure if Dave is back to coding yet. I might put this on my list to try to figure out in the meantime. Looks like it may take some time to come up to speed on tho.
I think Samsung must have made some firmware changes, as there seems to be a few issues with this driver, the Hubithings replica driver, and the soundbar drivers.
Edit: Happy to help with datalog and testing if required, I've got 4 connected TV's of various model years and a soundbar being controlled.
3 posts were merged into an existing topic: [2.4.1.103] Automated Command Retry for locks, switches, dimmers, shade [C-all]
Does anyone know if there’s documentation on the underlying API being used in this integration?
Originally, I believe he is using a hybrid of the Smartthings API (documentation here) and local web-socket which I can't find any docs.
The newer replica version uses that apps framework but still pulls from the Smartthings API.
Maybe check out his github
I just deleted the Smartthings token that I was using because I was trying to resolve some issues I was having and recreated it. It now seems that the personal access tokens after Dec 2024 can only be established for 24 hours (existing ones remain working). Did I just create a bigger issue for myself? How can I recreate a permanent token? Thanks!
Would you be able to bring this TV is using HubiThings instead? [RELEASE] HubiThings Replica
I believe that integration has already put a fix in place for the token changes. That's how I bring my fridge sensors and range oven into HE.
You would need to install HubiThings and then use the Dave drivers designed for HubiThings. That is probably the only way to use the 'new' PATs that work for 24 hours. I haven't done much testing with the new PATS, but HubiThings uses the OAuth token that is now required by ST.
I'm seeing some issues with this driver, the Hubithings driver, and the Samsung Soundbar driver, and wondered if anyone had made any progress in deciphering the code in Dave's absence?
The TV Remote driver no longer updates the TV volume state, the Hubithings replica driver produces a "null not found. Please try again." message on the TV screen when powering on, and the soundbar driver (and replica driver) media input settings no longer work (log below). I'm guessing that Samsung updated the SmartThings control a while back and these drivers need an update as a result of the changes, as all these functions used to work flawlessly.
info
Living Room Soundbar 1.2: setInputSource: [cmdData: [component:main, capability:mediaInputSource, command:setInputSource, arguments:[HDMI1]], status: [status:FAILED, errorMsg:non-HTTP Error]]
warn
Living Room Soundbar 1.2: syncPost: [status:ERROR, cmdData:[component:main, capability:mediaInputSource, command:setInputSource, arguments:[HDMI1]], httpCode:No Response, errorMsg:groovyx.net.http.HttpResponseException: status code: 422, reason phrase: Unprocessable Entity]
@djgutheinz I hope you are recovering well. I saw elsewhere that you might be on the verge of getting back into coding. If so, this driver could use some attention! 
If not, would you be able to point me in the right direction for any relevant API documentation that I could use to try to troubleshoot issues? Specifically on/off commands not working with my frame tv. Thanks!
1 Like
