Yes. If you use multiAttributeTile in your DTH:
tileAttribute("device.thermostatSetpoint", key: "VALUE_CONTROL") {
attributeState("VALUE_UP", action: "setLevelUp")
attributeState("VALUE_DOWN", action: "setLevelDown")
attributeState("default", label:'${currentValue}°')
}
tileAttribute("device.thermostatSetpoint", key: "THERMOSTAT_SETPOINT") {
attributeState("default", label:'${currentValue}°')
}
Should end up looking like this:
Thx.
That’s what the tile looks like for me too!
My issue is that there I don’t see thermostatSetpoint for this device- only heatingSetpoint and coolingSetpoint.
I’d like to be able to use the thermostatSetpoint variable in a webcore piston.
This is a snap of what I see for the device using this DHT with the wifi module. There is no {thermostatSetpoint}. 
After posting this last night I started playing around with mine, and checking up on documentation. Unfortunately it’s not a variable ST supports within the multiatributetile for thermostat, but I’d think that variable would be available in webcore. I don’t use it (yet) to know for sure, so try posting your question in the main webcore thread?
Hey everyone, I really need some help with this. I specifically purchased a SmartThings hub so I can control this thermostat with Alexa. I purchased a Alexa Enabled Thermostat and for a while it worked fine but I hated it because of its lack of features (specifically logging of the temperature and runtime). I put my 3M-50 back in and still love it however I have followed these instructions to allow it to work with the SmartThings hub but nothing I do will work. No matter what, it never finds my thermostat and updates the Device Network ID from the random one I put in. I have deleted the device and the device handler several times trying to make this work but it never updates the device ID and I am at a loss.
When I go into the SmartThings App (the new version…I cant use the old one because I activated the hub on the new app I think), it always shows my thermostat status as “Checking status…”. I cannot enter it to refresh or anything since it does not seen the device yet.
I have tried to check any log I can find for a Device Network ID but so far nothing. I am at a total loss. Any thoughts?
Update: Forgot to mention that I am using the Wifi Module although both Z-wave and Wifi are installed. I can poll the API manually from my browers and it all works fine with the Native Radio Thermostat App. I know it is setup right and working on my network, for what ever reason, it cannot be found by the ST Hub/Device Handler.
does the Filtrete native phone app work with your Tstat? NOW I see you answered yes.
there is a Samsung phone app, that you cannot/should-not use until you are specifically INVITED to do by ST support . But I assume you are using the old-but-updated-ST-native-phone-app (so am I) which does allow you to use custom device types such as your Wifi Tstat.
you are familiar with installation of gecko’s Wifi custom device type? My old Wifi integration still works, I assume the custom device type has not changed. I am on hub v1.
you are familiar with ST IDE? Check your cut-and-paste action, it’s easy to lose a character or 20 lines.
consider uninstalling Zwave module (USNAP). I do not know how. I am not using Zwave module.
there is only one place to see “Device Network ID”, right? IDE Device list.
Thanks for the help, I removed the zwave which did not help. After some more exploring I found a page with configuration info that was not included with the setup steps. I am not sure if it was required but the moment I put in the IP Address, Port, and Polling Interval manually in the device config, everything started working and the device network ID populated. If this step is required, why was it not included in the instructions? Below is a screenshot I took of what I’m talking about
Thanks again for the help. While it seems to finally be communicating with the SmartThings Hub and getting updated when its polled, for some reason it is not working with the SmartThings iOS app (Samsung Version). In the attached screenshot, you can see it just says “Checking Status…” still. I figured this would go away once I got it working but it is still doing it. Any thoughts?
I use the android app which I think is the primary interface to update the name, address, port, polling.
I don’t look at the thermostat with the phone app anyway, but it is updating.
Looks like live data. Did you try it with Alexa now.
at 21:03 on Jun11, my thermostat received an unrequested cooling setpoint change to 35F, for one minute. Pretty interesting - I noticed the fan should not be running. I suspect I can’t even set this low setpoint at the physical device.
Recorded by the tstat-manuf-app, but not ST, so this one does not look like an ST latency ghost command. Besides, I never sent any request for 35 ever, so ST has no record to ghost an old command.
Still, them’s the risks - I dunno - save your packet logs.
I have the same problem. Online ST shows I am connected. My iPhone using the new ST app only says “Checking Status.” I am also connected to Amazon with an Echo and it has connectivity to the thermostat so I know the ST Hub is connected to the thermostat. The issue is with the 2nd gen (new) ST app.
Any help would be appreciated.
jalari, did you ever get your set up, the same as mine, working and if so may I ask how?
D
So I finally gave up on the newer Smartthings app. It seems that this method is not compatible with it. Once I went back to the older version of the app (The non-Samsung Account version) everything works perfectly. I do not know of a way to make it work with the newer app. It most likely need to be adapted for the newer app and who knows if or when the author of the code will be able to do that.
Thanks for the quick reply. I think I’ll go to the old app as well.
I have three of these thermostats, two for heatpumps and one for a gas fireplace, and they all seem to work fine in SmartThings now. I love sitting in my family room and being able to turn on the fireplace by just saying “Alexa, set fireplace to 75 degrees”! Thank you so much geko for providing this device handler.
I’ve had this thermostat since 2010, I believe, and the same thing happened to me 3 or 4 times. Luckily I was at home and was able to quickly turn the AC off. I could not trace it to ST either. Could be a firmware glitch.
I’m afraid that’s not going to happen. Unfortunately, under Samsung leadership, ST is moving away from open, customizable platform. I’m still using the “classic” app and will do so while it’s still an option. Once it’s gone, I’ll be moving over to a more robust platform.
stuck on checking status…
Android
I think I’ve done everything right.
Created a new device handler from code, created the new device and published.
Thermostat is showing in smartthings. set the IP in smartthings
Stuck on
“Checking Status…”
It’s almost as if I working on the simulator.
When I edit the device handler code there are buttons across the top right:
Save Publish IDE Settings Device Type Settings Simulator<
The Simulator “<” sign changes to “>” when I click it. No Idea what that means.
Reading older posts, I see that the problem may be that I need the “Old” non-samsung smartthings app. Any idea where I can get this?
Any help would be appreciated!
do you have access to this thermostat by its native/non-ST app, or by the Filtrete web portal? To validate remote control works at all. https://my.radiothermostat.com/filtrete/login.html
Mine Tstat is still working via ST. I got a vague notion ST changes will break that within a year.
My original-smartthings-phoneapp/Android, points to the new app and I think it suicides. Not helpful. I haven’t tried the historical app repositories and I don’t expect it to work anymore.
FWIW, the 3M-50 Thermostat device handler still works after upgrading to the latest SmartThings iOS app (Version 1.6.67-520).
@geko, now that my smartthings hub-v1 is practically dead, am I right thinking that now my old Filtrete 3M-50 (Radio Thermostat CT-50? CT-30?) Wifi Tstat is inaccessible to smartthings (and also Alexa)? (I am unlikely to use a USNAP Zwave module). Very sad… at least the manufacture app and portal still work, but my wife is kinda shutout since the physical interface is so bad, and she is texting ME to make adjustments - ooohhh noooooo
It’s not clear to me yet if I can somehow use your custom device handler with hub v2 or v3 (I have both but deprecated. I am not going get into the new API.) I would appreciate your comments.
I am guessing it is time to open the ecobee3…
I’ve upgraded to ST hub V2 long time ago and my 3M-50 device handler still works just fine, including Alexa. The thermostat itself is showing signs of age, but as long as it works, I’m in no hurry to replace it. In fact, I don’t think there’re any thermostats on the market today with open local control. Everyone has gone cloud-based and I totally hate it.
