As many have requested, Iâve added in an optional a âhold-afterâ timer option to the Energy Saver feature. If set, the hold-after timer will hold the thermostat in a paused status for a specified number of minutes after all contacts have been closed. This timer works in conjunction with the hold-down timer which is configured using the setting, âMinimum Pause Timeâ. If both are set, TM will use whichever timer takes the longest to complete.
As always, I rely on you to report any problems. Please let me know if you notice that anything isnât working right. Feel free to make further recommendations for changes or additions and I will continue working to perfect Thermostat Manager. Enjoy!
Another happy user here. Just wanted to say that I am also interested in this option: the app to check periodically if the thermostat is really off and if not, to send a command to turn it off.
Peter2, Iâve looked at doing this before but I previously ruled it out because I donât want to override manual user commands at the thermostat. However, I think there may be a way to have it as an option by adding another toggle switch⌠Iâll put it in the list of things to look at.
I just installed your app from Github. It does exactly what I need it to do- i.e. turn off the thermostat if doors are left open x minutes then reenable once all doors are closed. The issue I have is that my door switches are âvirtualâ or âsimulated switchesâ - not physical switches (My Abode security system sets the simulated switch via IFTTT). When I use Energy Saver, it doesnât display my simulated switches. Is there a work-around for my situation?
I believe it should work. You mention virtual âswitchesâ. TM is looking for, âcontact sensorsâ (capability.contactSensor) for the device type so Iâm thinking that it will work if you change the device type.
Good catch. Youâre right. If I create a âsimulated contact switchâ it shows up in the pick list. Unfortunately, Iâm using IFTTT to link my Abode security door sensors to SmartThings and IFTTT only supports On/Off âswitchesâ, not contact sensors. Iâm back to the drawing board.
I have a RCS TBZ48 thermostat and for some reason in the main configuration of this smart app, I have a red bar by âThermostatâ with a message stating âYou canât currently add this.â Any suggestions on how to remedy this? The thermostat is set up as a âthingâ in my home and i can control the various functions from there, but I was hoping to automate the fan control a bit, hence this smart app.
Chris, it appears that Thermostat Manager doesnât recognize any thermostats on your network (which means that SmartThings doesnât). Have you added your thermostat to SmartThings yet? If you have, you should be able to see a thermostat device in which you can set temperatures and modes.
Thanks for the quick response! Yes the device is part of my network and is controllable from the smartthings app (both classic and the newer version), i.e. I can tap on my z-wave thermostat âthingâ to set and automate cooling/heating, just not the fan.
Before proceeding further, I will try removing the thermostat from âMy Thingsâ and re-joining it my network. On my IDE page itâs the only device that is listed as having an execution location in âthe cloudâ so maybe thatâs part of it.
No, that shouldnât affect anything. Iâll see if I can find the device handler for this thermostat. Maybe there is something unusual there. If you know what device handler it is using, that would be helpful.
What Thermostat Manager is looking for is a device with, âThermostatâ capability. So as long as the device has a proper device handler, is connected to the ST hub and is online, you should be able to add itâŚ
Just as a test, try adding your thermostat to one of the pre-installed SmartThings apps. It can be anything that requires a thermostat device, like âThermostat Mode Directorâ or, âKeep Me Cozyâ. See if you get the same result.
Chris, apparently there are many device handlers for the GoControl RCS TBZ48 out there. Youâll have to tell me which one youâre using. If youâre not sure, go to the SmartThings IDE, click on âMy Devicesâ, near the top, and then select your thermostat from the list. On the thermostat page, what does the row that says, âTypeâ, say?
Itâs not limited to your smartapp, iâve tried a few others like âRun circulate in HVACâ and âThermostat Fan On/Auto v4â and they same thing when trying to choose a thermostat.
No, Iâm talking about the device type that the device handler says it is, or in other words; the name of the device handler. In the ST IDE, click on âMy Devicesâ, near the top, and then select your thermostat from the list. On the thermostat page, what does the row that says, âTypeâ, (3rd row from the top) say? What does the 1st row (Name) say also?
Perfect. Thanks, I found it. Hereâs the code from the ST Repo if youâre interested:
The problem is that this device handler doesnât use a âthermostatâ capability. âthermostatâ capability is pretty standard although there are alternatives to use, it is what most thermostat device handlers use. Let me take a look and I can make a suggestionâŚ
Okay, now I will first say that this is something that I could fix by modifying Thermostat Manager. However, this would be a significant change and you are the first person to have run into this issue so Iâm thinking that you are probably just using a bad device handler. If thermostats begin to move away from using, âthermostatâ capability to something else however, I will eventually change TM. But I donât think that this is something that is necessary at this time.
I found you some alternatives. I also suggest that you search these forums and find some other options yourself, there will be plenty to choose from. Just make sure that you see the line:
capability âThermostatâ
near the top of the code.
Others in the forum say that they use this device handler for your thermostat. Itâs just called, âZ-Wave Thermostatâ. FYI, I also read people saying theyâre using a device handler called, âZ-Wave Thermostat Genericâ but I couldnât find it in the repo. If you see it in the SmartThings app, I suggest trying the, âgenericâ one first.
Now here is a developer from the forums who CHARGES for his work. This thermostat is a PAY thermostat. If you want the code you have to buy it â or something like that. Iâve never used any of his stuff myself. But it looks like a very full featured device handler. If you donât mind paying some money and want a really nice device handler, this one might be for you:
If you have any other questions or concerns, let me know. Always glad to help. And again, if this starts to be a trend I will modify TM to keep up.
Found one more. Some people from the forums also use this one. I donât know anything about it but it appears to be from a guy like myself who develops free apps.
Jordan, thank you for the âHold Overâ timer. I installed it shortly after it came out, and because of the situation I am using it in, it has been tested well. Thus far, it (and the rest of the app) has worked to perfection. Thank you again for your work. HS Barrett