Howdy,
If you need real time communication, subscriptions to SmartThings cloud is required. See Dave’s drivers here using the HubiThings Replica framework.
1 Like
For the TV itself, The off is determined by the state of a poll to port 8001. It first goes to Standby and then goes silent (the wifi goes to sleep). I wait until the wifi goes to sleep. If not, you can get into a wierd state.
The opposite is true for on. A WOL command is sent and verified by the power state going to on. I then set the status on and determine the on-state for the display (ambient, artMode, tv).
SmartThings does the same thing for on. It uses the WOL to turn on and the 8001 poll result to determine on/standby state (with a timeout being off).
I have updated Remote Builder to add a profile for the latest update to @djgutheinz amazing Samsung TV driver.
You just need to re-apply the profile for the new driver to have it take effect and use the new command set. BTW The newest version of Dave's driver is 2.3.9 to align with the platform version. Version 4.1-2 is the older version.
For those not familiar with Remote Builder its a way to control household devices using simple and realistic remotes that can be run from any device or put into the Hubitat Dashboard.
For example, this is the TV Remote.
2 Likes
When I go to HPM, it tells me Updates are Available for this package. However, it says I have 4.1-2 installed, and that the current update is 2.3.9. This seems incorrect and thus I did not install the "update". Screenshot below.
Anyone know what is going on and how I fix this? What is the proper current version of the Samsung Hubitat TV Integration?
2.3.9 is the latest version mate, the numbering has changed to align with the platform version. 4.1-2 is the older version.
1 Like
Is anyone else having issues with the updated driver? Since updating, whenever I send an off command, the first command fails and the second works, and last night the TV was off all night but the switch was reported as on. When I tried to refresh the device this morning, it failed to update the switch state, so I tried to manually open the web socket and refresh again, and the web socket failed.
Edit; I've resolved the issue by rolling the driver back to version 4.1-2
1 Like
Hi All,
I am still having some issues with this driver having previously enjoyed a largely issue free experience (version 4.1.2 as version 2.3.9 creates unreliable power on/off issues for me as described in my last post).
Basically, I have a webcore piston setup to set the TV volume based on different conditions (Roomba on/off, Mode etc), which has historically worked perfectly, but for the last few months is unreliable, and I think I've finally traced the problem.
There appears to be an issue with the SmartThings polling reporting the correct volume to the current state. A "Set Volume" command results in the desired result at the TV (providing the targeted volume is different to the current reported state), but the state is not updated unless you manually push the "Configure" command. If the "Set Volume" command is sent to the TV and the targeted volume is the same as the current reported state, then the command is ignored.
So (for example) in practical terms, what happens is that when the TV is turned on, the volume is set to 25 (providing the reported current state is not already 25). When my Roomba starts, the actual volume is set to 75, but the reported state remains at 25. When the Roomba stops, the volume remains at 75 as the command to set the volume back to 25 is ignored due to the reported state still being 25.
Is anyone else experiencing any similar issues?
1 Like
I too have been having issues with the latest 2.3.9 driver, and needed to rollback to 4.1-2.
I have a script which checks room brightness levels, and then manually adjusts the brightness on the FrameTV using this SamsungTVRemote device. The script sends key press events (e.g. arrowUp, arrowRight, enter, etc.) to wake the device and change the brightness setting. I'd send 16-22 keypress events in total.
With the old driver (4.1-2), it would generally work (99% of the time), although sometimes with a 500ms-1500ms delay per keypress.
With the new driver (2.3.9), only the first 1-3 keypress events would get received by the TV, and then nothing else would happen. Manually hitting keypresses on the Hubitat device page would only get keypresses registered 20% of the time.
I upgraded this driver recently (is there a way to check exactly when I upgraded?).
Looking at my logs, I see that something is happening with this TV in Hubitat every single minute, even when the TV is off. This never used to be the case, and I'd like to stop it. How do I stop this?
Below is an example (the black lines cover the personal info that is part of the device name) during a time when the TV is off:
@djgutheinz Hi - just wondering if you have any suggestions on how to stop this from running every minute 24/7/365...
Hello, I seem to have run into an issue lately where i can no longer control the off/on in 1.3.9 driver I seen where there was an updated driver in post 182 to seem to fix this issue is this correct? if so where do i find the latest driver 1.3.9.1 if there is one i checked with no success. Or would this be another issue on my part with the configurations? I to am getting the same logs as calinati above.
Thanks in advance
Hi how did you roll back the driver version?
If you go to the GitHub page for the driver, you can see the version history (link below) by clicking the three dots then “view code at this point”, then just copy and paste the code for the version you want over your current driver code 
HI thank you. I tried the roll back with no luck commands still wont work to turn on or off the TV. Did work perfect but just stopped.
Sorry for the lack of responsel In hospital and no residual energy. Perhaps in a week or two.
2 Likes
Damn, sorry mate, hope you are ok 
Do you have static ip addresses set for your tv’s?
Get well tv can wait. yes set to static
Focus on your health please!!
Sorry to hear you are in hospital. Wishing you a speedy and painless recovery.
1 Like
With my limited knowledge, I think I’m correct in saying that as long as the IP’s in the tv’s match the Hubitat device, on/off should work. Have you tried deleting the devices and setting up again from scratch?
