On the device's page, go down to the Device Detail section. It should have multiple entries that are used in operations of the system. For WOL, the following should exist in the format depicted by example.
deviceMac: 64:a7:d8:a7:5d:a9
alternateWolMac: 64A7D8A75DA9
With the latest enhancements, I am thinking of modifying the code. If the user has selected preference "Connect to SmartThings for added functions", I can use the SmartThings on/off command vice WOL.
I am having an odd issue with my automation which I think is related to this driver.
My automation is set to turn a light off when the TV is turned off, if that light is on.
However, sometimes when the TV is on, the light will just randomly go off, and then go back on about a minute later. I looked in the device events for this driver, and found that it is reporting the TV switching off, and then back on about a minute later when in reality, there is no activity with the TV switch. At first I suspected user error in my household. But yesterday I observed it - the light went off, the tv remained on, the tv remote was sitting on the table untouched and I was definitely not in the Hubitat interface. Yet the event log states the TV was switched off and then back on less than a minute later. TV was never off in this time.
Any ideas what is causing this and more important, how to fix it?
First question, regarding the Smartthing integration for this dever, could someone please advise how l obtain the 'SmartThings Device ID' to enable me to input this value into this driver.
Second question, has anyone been able get the 'ArtMode' button to put the Samsung Frame into Art Mode?
Also.. l am having the same issue as others have reported whereby the Frame TV is waking up from time to time going to one of the HDMI inputs instead of Art Mode - Very annoying
And even easier, get to the help pages by selecting the help function at the upper right corner of the device's page. It links to a GitHub page with links to all available manuals. When all else fails, read the instructions.
I’ve confirmed that the MAC addresses are in that format and that the mac address is the same as I’m using in the Ramdev WakeOnLan hubitat driver. For some reason I can power on the TV with that driver but not with this one.
Referring back to your comments about using the SmartThings API vs direct WOL. Would it be possible to use that same API to invoke ArtMode? Assuming that based on those other posts that the direct call to the TV has been removed.
Yes, l have read the instruction but they don't entirely match up with what is being displayed on the screen
for example..
"on a seperate loggin page, you will need this in a minute"
What loggin page are they reffering to? Hubitat or SmartThings web site?
"Find you device on log page and copy deviceid"
Again.. which 'log page'? Hubitat logs section?
The instructions appear to be a bit outdated and don't really match
For the seperate log page, it is refering to a hubitiat log. It can can be the tvs specific log page or the current full log. You can even go into past logs to find the the ST Device IDs after the API key has been entered. Once you enter the ST/Samsung API key the hubitat logs listed above will show the ST Decive IDs of all the eligible devices in your ST/Samsung account if the API key is correct and Hubitat can sucessfully access the API.
I do not know why. I use the documented Hubitat WoL implementation. I will add a ST ON/Off that will use the ST interface (if enabled) for the on/off.
One issue: If you unplug (or switch off) the TV then turn the switch on followed by powering on the TV, it takes 30 seconds or so before the WOL to work. This is internal to the device and can not be corrected. I see this behavior consistently on my TV.
def wol = new hubitat.device.HubAction ("wake on lan ${wolMac}",
hubitat.device.Protocol.LAN,
null)
No. Not in the ST implementation (yet). However.....
I reread the above. I will look into modifying the code - not clear if I can. If I can, I will need assistance testing.
Hi
I am trying to set up my home theatre with my Dennon AVR and now having found this integration, I can hopefully set up a proper Movie Night Scene in Hubitat.
Update to 3.0.2. A non-critical update to version 3.0.2 has been posted. I have decided to version this update since the condition may be long-term.
Reason: 2022 FrameTV an ArtMode Support. Samsung has apparently disabled the FrameTV ArtMode Key on the 2022 (and later?) model TVs. They may have also disabled the Ambient mode key. These functions may not work on these models.
Update: Adds note in states stating problems with Frame TV. Adds log warning to ArtMode and AmbientMode functions that these may not work on 2022 and later models. NO OTHER CHANGES.
Update Procedures:
Load and saveupdated code:
HPM if originally installed via HPM.
Use the Import Button on the Driver's edit page using the default url.
I deleted my post as I had a query regarding the ugrade to 3.02 by HPM and didnt read the instructons properly before posting. I forgot to to a Save preferences. all good now.
I always forget that step myself. And I write the instructions.
As a general practice; before reporting a problem to anyone but myself, I execute any configure and save preferences commands on the device's page. The final step is to refresh the browser's page. Then I look at the results and retest. If the pre-check does not fix the issue OR if I have to do this pre-check regularly, then I report the issue to the developer. But once is a case where the developer may not be able to duplicate (the infamous CND (could not duplicate)).
Browser refresh note: HE only updates Current States (attibutes) on the displayed device's page. HE doesn't updates state variables, nor schedules on the page without a browser refresh of some sort (i.e., after a save preferences). Also, occasionally I have seen attributes that should update w/o a browser not update. (I do a LOT testing). The browser update verifies the noted anomaly is a driver and not transient HE issue.
Just tested and it works on mine. I need to see a log.error or log.warning message to be able to determine the cause.
Also, the Set Volume uses the SmartThings interface. Try the Set Input Source or Toggle Sound Mode function. If that doesn't work, it points to your SmartThings interface. Still need log.warn/log.error message to troubleshoot.
all good now.
