Need app to just turn the AC off at 10?

Hi, the smartapp has been used for more than 3 years by many contributors, just look at the testimonials under the thread.

If you click on the post, there are some screenshots included in the post above, and there are more screenshots at the ST community wiki:

And, all the use cases supported are described in details under the configuration section:

ScheduleTstatZones - Things That Are Smart Wiki.

In your case, you should look into the use cases #10,15, 16,17 and 19.

BTW, if you have many units around in your house, you can use one master unit (ex. the LG mini split) and all the other slave units will be synchronized with its setpoints. With the virtual zone device that you can instantiate under ST, you can easily set a temp delta for each zone vs. the main thermostat’s setpoints (cooling/heating).

The smartapp uses the concepts of zones/rooms/schedules to control all the units (using the room/zone thermostat in each room). If an unit is outside the scheduled zones, then the smartapp can turn it off till its associated zone becomes active in your schedule.

There is more than 4K lines of code in the smartapp as it supports many features.

You can’t reproduce this kind of logic in webCore or any rule engine as those are only good for simple custom logic.

P.S. I’ve also included some special logic for the Remote ZXT-120 (custom DTH) in order to control the fan speed based on the temp differential inside the zoned rooms. I posted some infos about ScheduleTstatZones smartapp in the Remotec ZXT-120 thread about a year ago…


The Zxt-120 has a switch capability, can’t you just create a simple automation in smart lighting so that at 10am (or 10pm) every day, an off command is sent to the “switch?”

I believe that will change the thermostat mode to off. Tagging @Ron, who has the most comprehensive community device handler for this thing.

I would imagine @yvesracine’s smartapps could do what OP is asking for, and no doubt many other things (never used any of them, myself).

But webcore could do this as well. And it’s free.

Webcore is free indeed, but if you add your time to learn Webcore (it’s not that simple to learn), then to code and test your custom logic (which would need to be changed every time you want to add a new schedule or a new setpoint), then it becomes an investment in money (as your time is money)… And, you still don’t have any virtual zone devices for easier control under ST…

That’s why I ask for a small contribution for my time in developing my products which have thoroughly been tested before each release.

If you read the ST community wiki, you’ll see that my zoning smartapp can do a lot of use cases for the Remotec ZXT-120 for a contribution which is less than a few cups of coffee…


The logic the OP is looking for appears to be “turn off at 10 every day” (he didn’t mention am or pm).

I’m not knocking your code, I’m just saying it doesn’t appear to be necessary for this purpose.

And I’m telling the OP that my smartapp can do it and more… Just to be aware of this powerful option for its remotec ZXT-120…

And, I’m sure that your statement is not against my code as you’ve never used it… People who haven’t used my code cannot really talk against it as they don’t know what it can provide in terms of use cases and options to them…

Dude I really don’t know why everything with you has to turn into an argument about people who use your code vs. don’t use your code.

I hope the OP has gotten some ideas that will help him.

Peace out.

Thanks for the ideas and enthusiasm. I look forward to reading more.

@marktheknife, when I look at switch apps like Smart Lights, the tstat does not show up as an option, so it doesn’t consider itself to be a switch at this point. I may be able to cobble something together from existing code I find, or glance at webCoRE per @TonyFleisher’s suggestion.

@yvesracine, thanks for the additional info & screenshots on your app. I’m not adverse to employing a nuclear powered blowtorch in order to light this simple match (how’s that for a metaphor?).
I’m looking through the wiki pages now, trying to find a use case like “At this time, turn this unit to mode (off)”. This is a LG mini split install, there is no central fan unit or vented “zones”.
The price is reasonable, although “no refunds will be given” if I can’t get this part to work.
Thanks again!

Hi @AlHolden Eh, it’s your call as a ST user!

Vents are optional as indicated in the prerequisites at the ST community wiki.

This specific use case below is about turning off the room/zone thermostats that are not part of the scheduled zones:

If your HA needs grow, just be aware that there is a HA solution available which has been thorougly tested in the past 3 years…

IF you think about it, the concepts of rooms/zones/schedules are very powerful, and I’m sure that you quite don’t know yet how you will structure your zones for better climate control (which you will need to do anyway no matter what’s your final solution). The smartapp can be parameterized to accomodate your present & future requirements as you understand the needs for your home.

P.S. And, the no refund policy is understandable given the fact that you download the source code (with a copyright/license) as ST has no appStore and I had to create my own.


Which DTH are you using for your ZXT-120s?

You should really look at webCoRE. Me personally, I think it is a fairly straight forward and simple Rule Engine but can be as complex as you need it to be.

Not only will you be able to do what you are asking for free, you will more than likely use it for everything else.

Good Luck

This is a large part of my I lost interest in the SmartThings community. Every time I would ask a question the answer was “Use Webcore”. At times I would even post my question stating I don’t want to use webcore so given that how would you do x…and the reply would be “why don’t you want to use webcore”.

@AlHolden As a part of my zxt-120 code base I have a smart app that does what you wanted.
You can find it here.

It still works if you are not using the zxt-120 but some other thermostat because it just needs a thermostat capability.

That’s understandable, I know that in your case it’s because you are able to code a solution of your own and would prefer to do it that way.

For those of us that can’t develop our own code, webcore is very useful.

For @AlHolden, even smart lighting can do what you’re asking, if you’re using @Ron’s device handler. There’s another device handler out there that doesn’t use the switch capability, I believe.

Here’s a screenshot from my ST app of a smartlighting automation that will tell a zxt-120 to turn off at 10pm. The device will interpret that as a mode off command.

Thanks @marktheknife - I’m using the ZXT-120 HVAC Control handler by Brian Dahlem. It was the one mentioned in Amazon reviews and questions in the product page. I think the seller even posted the github link.
Sounds like there’s a better one to install?

I’m not adverse to geeking out over at WebCore or elsewhere. I write code for a living, just under a different platform. Projects like ST seem like the next generation of hobby for me, like model railroading, but for a new generation ;-]

@AlHolden feel free to try my handler if you like.

Here is a screen shot of what you get in the UI (note the page has screen shots which are out of date)

Yes, Much like railroading it gets expensive fast also :), enjoy!


Thanks a lot @Ron

I see now how the handler can make so much more difference than the apps. Yours causes the thermostat to consider itself a candidate for simple on/off switching (instead of only heat/cool/off “mode” options, which apparently are interpreted differently by manufacturers).

Unfortunate that this “big fix” also introduces a “small glitch” in my LG mini-split environment:
While Brian’s up and down setpoint arrows work with my unit, the blue thermometer slider in this one fail to produce any change, response or “ding” from the unit, even after trying all of the codes that came listed for LG in the zxt-120 box. Even Alexa will revert the setpoint if you try to change it. So there must be some difference in how setpoint changes are processed between the two handlers.

But that’s a minor issue when compared to the futility I was feeling a week ago. Thanks again!

I did this by design. I didn’t like that when I wanted to change temp from 70 to 75, 5 signals where issues 71, 72, 73, 74, 75. I just wanted 75 issued. I also didn’t like that when initially setting up my system and setting cooling to 75 and Heat to 80 the signals where sent which turned on my Mitsubishi system, when all I was doing was setting up my preferred temps so “On”, “Cool”, “Hot” would send the temps I desired when I used them. So I removed the code to send the temp when temp changes.

With my DH the process is

  1. Set temp for Cool and/or Heat. No signal is issued.
  2. Press Cool/Heat/On and both the Mode signal and Temp signal are issued.

If you don’t like this you could compare the two DH and move the code back into the set temp to issue that temp. It should be relatively easy.

Not sure what you mean by “revert”. This isn’t clear to me.

Ah. Got it.
It’s what our IT department overlords refer to as a “training issue”. I can work with that, or can experiment with changing it as a learning experience. Thanks.

More details on the Amazon Alexa app: Since it’s tied to the SmartThings hub, the devices show up under the “Smart Home” panel with some rudimentary controls. For thermostats, there’s only the current temp setting with plus and minus buttons.
Under your handler, the user can press the plus button and the display will increment by one degree. But, upon receiving no confirmation from the device, the display will revert back to the original setting after a few seconds.
This behavior makes sense actually, given your recent reply on the nature of the design.

Not that I need it, but if you ever work on this handler again, you may want to consider an option in the config to enable incremental degree transmissions, with a few word explainer.
Remember the IT mantra: good UI design reduces help desk support volume!

Does anything happen when you ask an Alexa device to, “set the [device name] to 72 degrees,” for example?

Alexa’s primarily meant to be controlled by voice anyway, isn’t she?

There are probably ways, with an Alexa routine and SmartThings virtual switches, to even get her to raise (or lower) the temperature by a degree if you say something like, “Alexa, crank it up one degree in here.”

That would probably require a custom smartapp or webcore to do something like define the current setpoint as n, and then set the temp to n+1 when a certain virtual switch is turned on.

If you are using the Alexa app to manually control your device, you might as well just use the SmartThings app and edit the device handler as needed to get the functions you’re looking for.

Hi @marktheknife
Sorry about that confusing detail. The Alexa note was about a debugging process I did - to see why the verbal command wasn’t working with Ron’s handler. You’re right, normally I would go straight to SmartThings or just tell that little Amazon hockey puck what I wanted ;-]

@Ron’s comment of a couple days ago has helped me understand what’s going on a little better. His handler apparently doesn’t set temperature points - unless it’s part of a mode setting command.

Great, I just took a look at the DH and I just commented out the code that sends the temp to the zxt-120 so you should find if very easy to add it back in if you want. Just remove the comments here.