quickSetCool and quickSetHeat

rayzurbock · 2017-08-27 22:04:09 UTC

Just curious. When did quickSetCool and quickSetHeat go away in webCoRE? I’ve searched the ST forums and couldn’t find an announcement or anything regarding these going away.

I noticed my thermostats were not syncing with webCoRE anymore (Thermostat A setpoint changes, send change via piston to Thermostat B) and went to investigate to find that where I had used actions for quickSetCool & quickSetHeat, when I went to edit them, those Do functions were blank and those actions were no longer in the list of selectable options. I had to change to set cooling point and set heating point.

I previously had to use the quickSet functions with my CT100 thermostats because it wasn’t as responsive to the setCoolingSetpoint and setHeatingSetpoint commands. I’ve adjusted my pistons now but noticed that my CT100 still wasn’t reliable when programatically changed. I realized this started a couple of months ago when my thermostat interface in the SmartThings app changed with an update. I created a Device Handler based on the original code here and added two lines to the command section:

command "setCoolingSetpoint"
command "setHeatingSetpoint"

All is well now. So, my issues were compounded. A) webCoRE appears to no longer support quickSetCool/quickSetHeat actions and B) SmartThings updated the Device Handler for the CT100 thermostat and the new version isn’t as dependable when settings are changed programatically.

ady624 · 2017-08-27 22:37:01 UTC

webCoRE is device agnostic and does not implement/support any such commands - it picks them up from the devices, so it may be that the DTH dropped them at some point?

rayzurbock · 2017-08-27 23:23:24 UTC

webCoRE used to have this do action:

The “Set quick cooling point” and “set quick heating point” options are no longer available. When I clicked on “Set quick cooling point at {CoolingSetpoint}F;”, the do action was blank as if it had been removed from available selectable options in programming, the value was still {CoolingSetpoint}. I clicked the Do action and then was able to set it to “Set cooling point…” and “Set heating point…” respectively.

ady624 · 2017-08-27 23:35:20 UTC

Like I said, the DTH most likely removed the two. The script still references them, but they are no longer there…

rayzurbock · 2017-08-27 23:37:55 UTC

Ok, thanks. I rolled back to a DTH version that had them. We’ll see if they show up or not (although I’ve changed my piston to use the non-quick versions which are working now with the older DTH).

bangali · 2017-08-27 23:38:43 UTC

looks like a month ago the commands quickSetCool and quickSetHeat were removed from the DTH by ST:

github.com/SmartThingsCommunity/SmartThingsPublic

ICP-1103, ICP-1125, ICP-1194 CT Thermostat issues (#2181)

* ICP-1103, ICP-1125, ICP-1194 CT Thermostat issues
- Added modes and changed mode names to reflect specification in thermostat capability
- Changed how device is initialized poll by sending all commands separated by 3 seconds
  instead of sending a request and on its response send the next. This to give all
  commands a chance in case one is dropped by the network.
- Reduced the time from 30 to 1 second between setting and requesting a setpoint
  using the setHeating/setCooling method. This is now the same as changing using
  the ST DTH tiles.
- Also modified the UI to use the multi attribute tile and using arrows instead of sliders
  for changing setpoints.

* Update ct100-thermostat.groovy

by marstorp on 12:27AM - 22 Jul 17

changed 1 files with 387 additions and 327 deletions.

rayzurbock · 2017-08-27 23:41:17 UTC

Yeah, I’ve found that thread, that’s where I found my solution of rolling back to the previous (non-SmartThings updated DTH)… cost me $400 bucks at least since it had my A/C running at 69F (night temp) 24/7, home, away, night, etc. I found out my thermostats weren’t changing/syncing but couldn’t/didn’t dive into it until today.

bangali · 2017-08-27 23:46:14 UTC

ok. sorry to hear that the DTH change impacted you this way. i wouldnt be happy either, if that happened to me. i personally find it safer to stay with a known good DTH instead of upgrading unless you need the new/changed functionality.

rayzurbock · 2017-08-27 23:54:12 UTC

In this case, it was SmartThing’s change of the official DTH regarding the CT100 thermostat. I rolled back to a community hosted earlier version which has resolved the issue.

It’s not webCoRE’s fault at all, I thought that Set quick cooling point/Set quick heating point may have been removed and went to look for the announcement and didn’t see it so I thought I’d ask.

Sometimes, you pay to play and I don’t mind playing.

ady624 · 2017-08-28 00:16:13 UTC

Sorry to hear that ;( you need to revisit Available Devices after changing the DTH, but I guess you figured that out already

rayzurbock · 2017-08-30 01:48:36 UTC

That’s the magic sauce.
Quick Set Cool and Quick Set Heat are showing up after visiting the “Available Devices” page in the SmartApp.
Thanks.