I looked at the events and didn’t see any clues. Originally I thought it might just be Honeywell’s servers were overloaded but the fact that it’s only happening when turning it back on would rule that out I think. I’ve turned it on and off many times via the Smartthings tile and didn’t experience any failures. As long as the workaround is reliable I’m happy with it though! 
Hey,
I just wanted to share something that I encountered yesterday. My iphone automatically updated the smarthings app yesterday. it looks like they mostly updated thelook and feel to the layout of the the app. I dont see any real changes to function or fixing any know issues or flaws. But what did happen with the update has affected the availability to add a new function of your thermostat manager. If you now go to the SmartApp section of smartthings, your thermostat manager appears and disappears randomly from the list of apps available. if it does happen to appear and you click on it, it attempts to open and just closes out immediately. so adding any new function is not possible at all. If you already have existing things set up they are still in your automation list and are available to use and make changes. (I am not sure if the update has affected any of the functionality of it yet)
My ipad does not have the app auto update on and the old version of smarthings is still active on it. So when I go on it and use the old smartthings version everything is still the same and works perfectly with the thermostat manager. You are able to select it and add a new function. so something in the app update is causing an issue for sure.
Interesting. I wasn’t aware TM had been officially published. I made it available to Samsung for publication a long time ago but I’ve never seen it published. Of course I haven’t seen them publish anything new at all really in quite some time.
This isn’t going to have anything to do with the Thermostat Manager app I think. This is going to have to do with your installation of the SmartThings app or its connectivity to the Samsung cloud. I would recommend contacting support about this one. Reinstalling SmartThings might help but … you might lose some settings you want if you do that… I also wonder if the old app could interfere with the functionality of the new app. It has been awhile and I’m pretty sure the old app is no longer supported.
Hi,
I don’t think they officially published it. I just followed your instructions from this community. After I followed the instruction i went back to the smartthings app in the SmartApp section and it was there. If it wasnt there I dont know how I would have acceded it. I thought that is how it was supposed to happen.
Also the first thing i did was to uninstall and reinstall the smartthings app, that didn’t fix the issue.
as far as the old app. The old app was the most up to date version until they updated it the other day. like I said I had auto update on my iphone for the apps and for the phone itself, so everything was current and up to date.
additionally I am experiencing the same issues as [Yossarian] the door sensor may be open beyond the set time and it wont shut off the AC. and if it does shut it off it may not come back on after it closed.
To Install Thermostat Manager Smart App:
- Login to the SmartThings IDE .
- Click My SmartApps .
- Click the New SmartApp button.
- Select the From Code tab.
- Copy all of the code from the thermostat-manager.groovy file into the box.
- Click the Create button.
- Click the Save button.
- Click the Publish button and click For Me .
Regarding the app issues, I recommend contacting SmartThings support.
Regarding the TM Energy Saver issue, have you updated to the latest version? What model of Honeywell Wi-Fi thermostat are you using?
I would recommend that you do as Yossarian did and enable debug logging and record some logs from the IDE during an Energy Saver pause. But if your app is up-to-date, the most likely case is that Honeywell has made some change in their system that is causing commands to be dropped for some reason.
FWIW I haven’t seen any similar issues with the Android version of the new ST app. And so far the latest version of TM is working great with my Honeywell WiFi thermostat. (RTH9585WF)
1 Like
Hi I have the debugging selected and someone has has triggered it by leaving a window open for longer then the set time of 5 minutes. I received the notification the “thermostat manager is turning off the thermostat temporarily due to an open contact” but it did not turn the thermostat off I had to turn it off manually. it seems like when I set the time to shut it off over a minute or two it doesn’t shut the thermostat off. I am not sure how to access the debug log to share with you. any help you can provide to resole this would be greatly appreciated,
Login to the SmartThings IDE
Click on Live Logging
Your debug output will be there under Thermostat Manager. If you record these events I will do my best to analyze. It appears that Honeywell has done something that changes the way that their cloud-based thermostats respond to SmartThings apps…
Sorry I am new to this, I don’t see where the logs are, I went to smartthings app, then to your thermostat manager app that I have set up, I open it up, the togel for debug is selected, but I dot see where the logs are.
It’s not in the app, it’s on the IDE. The SmartThings cloud interface.
Again I am very sorry I am totally new to all this. I had looked around in the IDE also before looking in the app as I previously replied. I have looked again and I am not sure where to navigate to get to the debug logs. can you please direct me to where they are and I will post it.
This is the only area that I see that contains logs but I dont see anything that would help.
That’s the right place. Now all you have to do is wait for the logs to roll in. You’ll see the Thermostat Manager events labelled clearly.
Recommend you remove that image you posted so that people can’t see your login e-mail address.
ok now I see the logs start after I opened that page. But am I correct that the logs only populate from that point forward when that page is open? meaning that you cant just log on and look back at an ongoing history of all the events, it only starts to records when the page is open?
That’s right, you have to leave it open.
Here are the debug logs, front door contact was opened and triggered it but the thermostats stay on… the thermostat manager was initially working sometimes now it doesn’t seems to work at all
1:59:31 PM: debug Thermostat_Manager.contactClosedHandler(): A contact has been closed.
1:57:23 PM: debug Speed Response [message:[payload:[:]], coapToken:179600000fe6c47b, responseCode:UNAUTHORIZED, receiverDi:472e9a5d-7352-6134-f21c-bbba20c766b7, observeOption:NOTHING, path:/oic/route/472e9a5d-7352-6134-f21c-bbba20c766b7/SamsungWRNetTraffic, senderDi:OCFDeviceType
1:57:23 PM: debug in getInitialSpeedsHandler() method
1:57:23 PM: debug getInitialSpeeds called()
1:48:40 PM: info Thermostat Manager - Thermostat failed to change to off mode.
1:47:40 PM: info Thermostat Manager - Cannot set thermostat mode. No thermostat or thermostatMode devices have been configured.
1:47:40 PM: debug Thermostat_Manager.verifyAndEnforce(): Thermostat has failed to initiate off mode. (3/3) Trying again.
1:47:23 PM: debug Speed Response [message:[payload:[:]], coapToken:179600000fe622da, responseCode:UNAUTHORIZED, receiverDi:472e9a5d-7352-6134-f21c-bbba20c766b7, observeOption:NOTHING, path:/oic/route/472e9a5d-7352-6134-f21c-bbba20c766b7/SamsungWRNetTraffic, senderDi:OCFDeviceType]
1:47:23 PM: debug in getInitialSpeedsHandler() method
1:47:23 PM: debug getInitialSpeeds called()
1:46:39 PM: info Thermostat Manager - Cannot set thermostat mode. No thermostat or thermostatMode devices have been configured.
1:46:39 PM: debug Thermostat_Manager.verifyAndEnforce(): Thermostat has failed to initiate off mode. (2/3) Trying again.
1:45:39 PM: info Thermostat Manager - Cannot set thermostat mode. No thermostat or thermostatMode devices have been configured.
1:45:39 PM: debug Thermostat_Manager.verifyAndEnforce(): Thermostat has failed to initiate off mode. (1/3) Trying again.
1:44:39 PM: info Thermostat Manager is turning the thermostat off temporarily due to an open contact.
1:44:39 PM: info Thermostat Manager - Cannot set thermostat mode. No thermostat or thermostatMode devices have been configured.
1:44:39 PM: info Thermostat Manager is turning the thermostat off temporarily due to an open contact.
1:44:22 PM: debug Thermostat_Manager.contactOpenHandler(): A contact has been opened.
This is the key line. Thermostat Manager says that you have not configured a thermostat mode device. Please post a screenshot of your, “Alternative Configuration” page.
Okay, this is a weird one. Need you to do 2 things. The first one will help me figure out what happened:
- Login to your IDE: https://account.smartthings.com
- At the top of the screen, click on the link labeled, “My Locations”.
- In the table on the page, click on the link labeled, “smartapps”.
- Find Thermostat Manager in the table on this page and click on the words.
- In the screen that pops up, scroll all the way to the bottom of the, “Settings” table and take a screenshot that shows the values of, “useAltThermostatConfig” and, “tstatMode” and reply with that screenshot.
Now to fix the problem. Go into your, “Alternative Thermostat Configuration” settings in the TM app and disable the, “Use Alternative Thermostat Configuration” slider. Then, click on the, “Thermostat Mode Controller” selector and touch the one you selected to deselect it. If you have trouble with this, selecting a different device will work also. Now save your settings and exit Thermostat Manager.
Next, go back to the Alternative Thermostat Configuration page and re-select the proper thermostat for the Thermostat Mode Controller. Re-enable the, “Use Alternative Thermostat Configuration” slider. Save your settings.
I believe this will fix your problem. Somehow your variables got set wrong.
ok there is definitely something strange going on. followed your directions and the Thermostat Manager is not in the table on this page so I stopped there.
My guess would be that you named the TM instances as one of the AC off labels. Try one of those.