I like the secondary device type idea. I ended up removing all of the humidity stuff from my code because I was getting tons of errors trying to determine the humidity. My stat does not have the sensors so troubleshooting was near impossible. I have updated the code on github with the new device type that is error free at the moment.
1 Like
Thatâs the way I was leaning, too. Stripping down the thermostat device code to just support the outdoor sensor was pretty darn easy. Hereâs the repo. It takes the same settings as the thermostat device type and youâll probably want to use Pollster to get it to update regularly.
Iâll go back and do a (hopefully) clean implementation of the humidity stuff. You pasted your API data from the web page source a while back, so I should be able to use the differences between that and what mine reports to do it so everyoneâs happy.
Sounds good. If you look at my device type here you can get an idea of how to make the various humidities selectable for display. Lines 59 and 60. This would allow the user to choose whichever humidity they would like displayed in the tile.
I think they changed their url structure. I kept getting unauthorized until I changed all the urls to start with https://mytotalconnectcomfort.com/portal/ instead of https://rs.alarmnet.com/TotalConnectComfort/ starting today.
Which code are you using? All of my urls are already the correct url.
Thanks! I just pushed a new version of the outdoor sensor device that allows choosing whether you want temp or humidity as the main value. Iâm going to take a crack at the thermostat device next.
Jody, Iâm looking at your github and I donât see the correct URLâs. Just FYI, either itâs late for me, or for you, and Iâm not super experienced at github⌠but in case it helpsâŚ
1 Like
I see. I got the from and to mixed up. I will change the code on github. Thanks for the heads up.
I updated my code on github to reflect the correct urls.
2 Likes
Iâve been having problems the last week or so with the thermostat not working through ST. The temps were always different than what the thermostat was showing, or the Honeywell app was reporting. I also could not change temps, modes, etc. through ST.
I just jumped on here to see if otherâs were having issues, and noticed you recently updated the code. I copied and pasted latest version over My Device Type and it started working again! I like the mode notification tile!
Thanks for keeping this up to date!!
It looks like there may be an issue today. I am having issues talking to the thermostat this morning.
They are definitely messing with things. If you have issues this morning, I am investigating. I will likely be moving away from this thermostat before the new year. I just want one that works.
Iâm not at home but I do not see any IDE errors when I click REFRESH in the SmartApp.
Hopefully ST @Ben will work with Honeywell to get this official! Please! I do not want to own a smart tsat and not be able to use it with ST.
I totally agree @Dave! I was so thankful that @jody.albritton was able to do such a great job integrating the two, and it would be a shame to have to go back to using multiple apps for thermostat control, especially since Honeywell opened up their API to Logitech for the Home Control stuff, so itâs definitely possible. I guess in theory I might be able to use the Harmony-ST connection to control the Logitech connection to this thermostat via ST, but it definitely adds complexity.
I was seeing a new cookie and several access denied. It may be a transient issue, because It started working again.
@Dave Can you post your working code?
Trying but all I have is my iPad and having a hard time copying the code. Not sure how to do âselect allâ using the iPad.
Trying to change the temp, I received this:
And a red banner âConnection Failedâ.
Yeah. That is what I am seeing as well. That âEccMyTccâ is new. I really donât want to replace my thermostat but every two weeks they break it.
ST should be able to work something out with Honeywell. I use it everyday to adjust my temp (and save me $$) depending on what ST mode Iâm in.
Thanks for your work!
I have heard that the iPhone uses a different API - which appears to by SOAP based. There is an open Ruby implementation of it. I donât know Ruby or SOAP so I couldnât really make heads or tails of it - but if someone can loo into it, Iâm guessing itâs much more stable that the API that we are using.
The code in my own thermostat project keeps breaking too, and Iâm getting very tired of constantly re-debugging their protocol. I havenât checked out this latest EccMyTcc issue - I will take a look tomorrow and see if I can offer any insight.
Ruby SOAP code is available here: