PLUGIN: Honeywell Total Connect Comfort Thermostats

Plugins & Plugin Development Unmaintained
141

I couldn’t wait for the reply. :stuck_out_tongue: So I went for it and I had success, ;D 8)

here is what I did:

[ol][li]Completely uninstall the existing Honeywell TCC Plugin.[/li]
[li]Install all of the files form the file called “Version 1-0 RC.zip” that is on page 7 of the above referenced thread or here: http://forum.micasaverde.com/index.php?action=dlattach;topic=29938.0;attach=21790[/li]
[li]If you need help on how to install these files, the instructions are on page 2 of the above referenced thread or here: http://forum.micasaverde.com/index.php/topic,29938.msg212975.html#msg212975[/li]
[li]Reload luup[/li]
[li]Open your new device and provide your Honeywell TCC login credentials. Make sure you can successfully log in.[/li]
[li]Manually enter your Thermostat ID numbers. If you don’t know these, you can get them from going to www.mytotalconnectcomfort.com, login and select one of your thermostats. You will see a 6-digit number at the end of the URL on your browser. This is the Thermostat ID.[/li]
[li]After you enter these numbers in and click the Update IDs button, the thermostats will be added. Please note that in Vera, the Thermostat names will just be the ID numbers, but you can manually change this.[/li][/ol]

Overall, this version of the app works fine. It is a lot more “manual”, than the other version, but it gets rid of the error message and will work fine for those who didn’t already have the app set up when the issue started. Also, this version of the app is limited to 3 Thermostats…just be aware of that if you have more than 3.

142

[quote=“lingerba, post:141, topic:185402”]I couldn’t wait for the reply. :stuck_out_tongue: So I went for it and I had success, ;D 8)

here is what I did:

[ol][li]Completely uninstall the existing Honeywell TCC Plugin.[/li]
[li]Install all of the files form the file called “Version 1-0 RC.zip” that is on page 7 of the above referenced thread or here: http://forum.micasaverde.com/index.php?action=dlattach;topic=29938.0;attach=21790[/li]
[li]If you need help on how to install these files, the instructions are on page 2 of the above referenced thread or here: http://forum.micasaverde.com/index.php/topic,29938.msg212975.html#msg212975[/li]
[li]Reload luup[/li]
[li]Open your new device and provide your Honeywell TCC login credentials. Make sure you can successfully log in.[/li]
[li]Manually enter your Thermostat ID numbers. If you don’t know these, you can get them from going to www.mytotalconnectcomfort.com, login and select one of your thermostats. You will see a 6-digit number at the end of the URL on your browser. This is the Thermostat ID.[/li]
[li]After you enter these numbers in and click the Update IDs button, the thermostats will be added. Please note that in Vera, the Thermostat names will just be the ID numbers, but you can manually change this.[/li][/ol]

Overall, this version of the app works fine. It is a lot more “manual”, than the other version, but it gets rid of the error message and will work fine for those who didn’t already have the app set up when the issue started. Also, this version of the app is limited to 3 Thermostats…just be aware of that if you have more than 3.[/quote]

Just had my Mitsubishi splits installed, Followed these instructions and it worked great. Just wish it could do more than 3 thermostats as I have 4.

Thanks for posting.

Ken

143

[quote=“mystic860, post:142, topic:185402”][quote=“lingerba, post:141, topic:185402”]I couldn’t wait for the reply. :stuck_out_tongue: So I went for it and I had success, ;D 8)

here is what I did:

[ol][li]Completely uninstall the existing Honeywell TCC Plugin.[/li]
[li]Install all of the files form the file called “Version 1-0 RC.zip” that is on page 7 of the above referenced thread or here: http://forum.micasaverde.com/index.php?action=dlattach;topic=29938.0;attach=21790[/li]
[li]If you need help on how to install these files, the instructions are on page 2 of the above referenced thread or here: http://forum.micasaverde.com/index.php/topic,29938.msg212975.html#msg212975[/li]
[li]Reload luup[/li]
[li]Open your new device and provide your Honeywell TCC login credentials. Make sure you can successfully log in.[/li]
[li]Manually enter your Thermostat ID numbers. If you don’t know these, you can get them from going to www.mytotalconnectcomfort.com, login and select one of your thermostats. You will see a 6-digit number at the end of the URL on your browser. This is the Thermostat ID.[/li]
[li]After you enter these numbers in and click the Update IDs button, the thermostats will be added. Please note that in Vera, the Thermostat names will just be the ID numbers, but you can manually change this.[/li][/ol]

Overall, this version of the app works fine. It is a lot more “manual”, than the other version, but it gets rid of the error message and will work fine for those who didn’t already have the app set up when the issue started. Also, this version of the app is limited to 3 Thermostats…just be aware of that if you have more than 3.[/quote]

Just had my Mitsubishi splits installed, Followed these instructions and it worked great. Just wish it could do more than 3 thermostats as I have 4.

Thanks for posting.

Ken[/quote]

It might be worth trying to install a 2nd instance of this plugin to see if you can have 4-6. I only have 3 thermostats so I haven’t tried this.

144
It might be worth trying to install a 2nd instance of this plugin to see if you can have 4-6. I only have 3 thermostats so I haven't tried this.

This worked , I am now able to have more than 3 thermostats. Great idea to add another instance, I often forget you can do that.

145

Follow the above listed instruction, app seemed to install, communicate and pulled down the initial readings. Since the initial contact the app in my situation does not seem to receive updates from thermostat.

146

hmm…that is interesting. I am assuming you know the refresh interval is default set to 300 seconds and you have not changed that value?

I would open the parent app, click Advanced, then Variables. From there you can see “t.1.refreshStatus” (as well as 2 & 3). When the app is working properly the field should say something similar to, “Successful Refresh: Thu, Aug 20, 07:50:53 AM”. You should be able to check that ever five minutes or so and see the time updated. If it doesn’t say sucessful, then maybe it will give some indication as to what error there is.

147

Thanks for all of the instructions and links on how to install the LUUP files and set this up. I specifically went and bought a Honeywell TSTAT because it would work with Vera and was quite disappointed when I could not get it set up. This really helped a lot!

Since I’m new, I read that UI7 will not allow an “Auto” temp setup. In Texas, and in many states, heat needs to run in the morning and AC in the afternoon. Is this something that can be set up as a scene rather than in the device settings?

148

[quote=“Scoutmedic, post:147, topic:185402”]Thanks for all of the instructions and links on how to install the LUUP files and set this up. I specifically went and bought a Honeywell TSTAT because it would work with Vera and was quite disappointed when I could not get it set up. This really helped a lot!

Since I’m new, I read that UI7 will not allow an “Auto” temp setup. In Texas, and in many states, heat needs to run in the morning and AC in the afternoon. Is this something that can be set up as a scene rather than in the device settings?[/quote]

I don’t use AUTO so I wasn’t aware of this issue, but I just tried it and I see what you are talking about. There is a separate set point for the heating mode as compared to the cooling mode. For example, the way my system is setup, when I am “away” Vera performs the following actions:
“urn:upnp-org:serviceID:TemperatureSetpoint1_Heat” “SetCurrentSetpoint” to 62
“urn:upnp-org:serviceID:TemperatureSetpoint1_Cool” “SetCurrentSetpoint” to 78

So this way, regardless of mode I have the thermostat in, it applies both set points and I am covered whether I am heating or cooling. I am not 100 sure if this will work properly for AUTO, but it might be worth a try. You would just set your thermostat to AUTO either at the thermostat or using Honeywell’s website. Then, just use Vera to change the set point(s). You could accomplish this with a scene, but PLEG may be easier/more efficient for you and give you a lot more ability to customize what you want.

149

I looked into this a little and it looks like it’s getting an HTTP 500 Response (Internal Error) when it tries to access:

https://mytotalconnectcomfort.com/portal/Location/GetLocationListData

Going to this page directly also gives an error so it’s likely that Honeywell has made changes on their side. The code that makes this call looks like it’s just looping through the device list to get the ids. But it seems to work fine with out it though and wasn’t in the initial 1.0 version. I could remove the calls to this function and prevent the error from showing, but it’d be nice if JoeyD was around to give a definitive answer.

~John

150

Thanks lingerba. There is so much to learn coming from years using Nexia.
Where did you insert the instructions for the heat and cool temps? It looks a lot easier than the scenes I threw together.

151

I did it using the PLEG app. Search the forums and there is tons of information about it. You can do the same thing by using a scene. When you are setting up the actions that should be taken in the scene (called “Finish the Scene” in UI7), you choose “Advanced Editor”, select “Add First Action”, select your thermostat, then select the items from my post above. You will see there are several headings in the list that match the first part in the quotes above (i.e urn:upnp-org:serviceID:TemperatureSetpoint1_Heat) then below there are the options which match the second part of the quotes (i.e. SetCurrentSetpoint). You will actually only select the second part, just make sure it is under the proper heading. Once you do that, you will have a field where you can enter your desired setpoint. This is very similar in PLEG when defining an action.

152

Is there any news on a european version? I would realy like to have that running :smiley:

153

I was able to get the error message to go away by commenting out the following lines in L_HoneywellTCC.lua:

-- now we can make API calls to add the device thermostat information for i,v in pairs(tblLocations) do -- local devResult, decText, theDevice = getDevicesInLocation(i) -- if devResult == 1 then -- for j,k in pairs(theDevice) do -- tblLocations[i].Devices[j] = {Name = k} -- end resultCode = 1 -- successful retrieval of location and device info resultText = "Success" -- else -- resultCode = 3 -- resultText = "Issue with processing getDevicesInLocation. (Issue already logged)" -- end end

It’s a hack until a proper fix can be made but I did a quick test and everything seems to be working properly.

~John

154

[quote=“lingerba, post:141, topic:185402”]I couldn’t wait for the reply. :stuck_out_tongue: So I went for it and I had success, ;D 8)

here is what I did:

[ol][li]Completely uninstall the existing Honeywell TCC Plugin.[/li]
[li]Install all of the files form the file called “Version 1-0 RC.zip” that is on page 7 of the above referenced thread or here: http://forum.micasaverde.com/index.php?action=dlattach;topic=29938.0;attach=21790[/li]
[li]If you need help on how to install these files, the instructions are on page 2 of the above referenced thread or here: http://forum.micasaverde.com/index.php/topic,29938.msg212975.html#msg212975[/li]
[li]Reload luup[/li]
[li]Open your new device and provide your Honeywell TCC login credentials. Make sure you can successfully log in.[/li]
[li]Manually enter your Thermostat ID numbers. If you don’t know these, you can get them from going to www.mytotalconnectcomfort.com, login and select one of your thermostats. You will see a 6-digit number at the end of the URL on your browser. This is the Thermostat ID.[/li]
[li]After you enter these numbers in and click the Update IDs button, the thermostats will be added. Please note that in Vera, the Thermostat names will just be the ID numbers, but you can manually change this.[/li][/ol]

Overall, this version of the app works fine. It is a lot more “manual”, than the other version, but it gets rid of the error message and will work fine for those who didn’t already have the app set up when the issue started. Also, this version of the app is limited to 3 Thermostats…just be aware of that if you have more than 3.[/quote]Total Vera noob here (just received my VeraEdge today).

This app is one of the things I had my eye on when researching automation and it’s sad to find out it’s no longer maintained. I’d really like to be able to push some setpoint overrides on “away” status, while keeping the regular “occupied” schedule within native realm of TCC & thermostats.

I initially installed the app store version of this, and ran into the same error message as the last few posts. Searching the error led me here. The app would login to my TCC account but would not list any thermostat devices.

I followed the instructions quoted above to install previous version of the app manually, and am unfortunately stuck.

I have files installed, parent device created, and have entered the thermostat IDs for my two t-stats, causing the app to create two child thermostat devices. Unfortunately the Vera is not pulling any info from TCC regarding either of the thermostats - it shows 0*F setpoint, mode:off, fan:off for both units. There is no log activity showing under either unit.

I don’t even know where to begin with looking at event logs on this device or other troubleshooting. I’m a 15 year IT pro but this is all new to me - so if anyone could give me a pointer or two on troubleshooting this configuration, I might be able to fix it. :slight_smile:

Any help would be most appreciated!

Edit to add: due to a LAN settings fiasco I ended up factory defaulting my Vera and reinstalling this as the first plugin on the new install. Same behavior. The app says it is refreshing every 5 minutes (I have tried adjusting the refresh timeout variable down to 60 from 300 and it seemingly has no effect). The thermostat devices are not showing any data for current setpoint, mode, fan mode, or indoor temp. I attempted to change setpoint and mode in Vera and did not see any change on Honeywell’s website or at the stat.

Logfile has some errors… I can’t attach here so here is a google doc.

https://docs.google.com/document/d/1YjrX4r1ssRkDxrlQLm3LR_RrVQEOQBCEF-q1dk4Lk_w/edit?usp=sharing

155

[quote=“James92TSi, post:154, topic:185402”][quote=“lingerba, post:141, topic:185402”]I couldn’t wait for the reply. :stuck_out_tongue: So I went for it and I had success, ;D 8)

here is what I did:

[ol][li]Completely uninstall the existing Honeywell TCC Plugin.[/li]
[li]Install all of the files form the file called “Version 1-0 RC.zip” that is on page 7 of the above referenced thread or here: http://forum.micasaverde.com/index.php?action=dlattach;topic=29938.0;attach=21790[/li]
[li]If you need help on how to install these files, the instructions are on page 2 of the above referenced thread or here: http://forum.micasaverde.com/index.php/topic,29938.msg212975.html#msg212975[/li]
[li]Reload luup[/li]
[li]Open your new device and provide your Honeywell TCC login credentials. Make sure you can successfully log in.[/li]
[li]Manually enter your Thermostat ID numbers. If you don’t know these, you can get them from going to www.mytotalconnectcomfort.com, login and select one of your thermostats. You will see a 6-digit number at the end of the URL on your browser. This is the Thermostat ID.[/li]
[li]After you enter these numbers in and click the Update IDs button, the thermostats will be added. Please note that in Vera, the Thermostat names will just be the ID numbers, but you can manually change this.[/li][/ol]

Overall, this version of the app works fine. It is a lot more “manual”, than the other version, but it gets rid of the error message and will work fine for those who didn’t already have the app set up when the issue started. Also, this version of the app is limited to 3 Thermostats…just be aware of that if you have more than 3.[/quote]Total Vera noob here (just received my VeraEdge today).

This app is one of the things I had my eye on when researching automation and it’s sad to find out it’s no longer maintained. I’d really like to be able to push some setpoint overrides on “away” status, while keeping the regular “occupied” schedule within native realm of TCC & thermostats.

I initially installed the app store version of this, and ran into the same error message as the last few posts. Searching the error led me here. The app would login to my TCC account but would not list any thermostat devices.

I followed the instructions quoted above to install previous version of the app manually, and am unfortunately stuck.

I have files installed, parent device created, and have entered the thermostat IDs for my two t-stats, causing the app to create two child thermostat devices. Unfortunately the Vera is not pulling any info from TCC regarding either of the thermostats - it shows 0*F setpoint, mode:off, fan:off for both units. There is no log activity showing under either unit.

I don’t even know where to begin with looking at event logs on this device or other troubleshooting. I’m a 15 year IT pro but this is all new to me - so if anyone could give me a pointer or two on troubleshooting this configuration, I might be able to fix it. :slight_smile:

Any help would be most appreciated!

Edit to add: due to a LAN settings fiasco I ended up factory defaulting my Vera and reinstalling this as the first plugin on the new install. Same behavior. The app says it is refreshing every 5 minutes (I have tried adjusting the refresh timeout variable down to 60 from 300 and it seemingly has no effect). The thermostat devices are not showing any data for current setpoint, mode, fan mode, or indoor temp. I attempted to change setpoint and mode in Vera and did not see any change on Honeywell’s website or at the stat.

Logfile has some errors… I can’t attach here so here is a google doc.

https://docs.google.com/document/d/1YjrX4r1ssRkDxrlQLm3LR_RrVQEOQBCEF-q1dk4Lk_w/edit?usp=sharing[/quote]

Open the device settings for the plugin and go to the TCC Setup page. It shows “authorization status”, that should be “Successful”. Below that, where you enter your thermostat IDs, to the right of each one should be details of when it was last refreshed. For example, mine says, “Successful Refresh: Mon, Aug 31, 08:20:34 AM”. If you aren’t seeing “successful” in both of those locations, something is wrong with your login credentials and/or thermostat IDs. If they are both successful, then I am at a loss for what the issue could be.

156

Thanks for replying! The user/pass authorization has always shown successful, and for a while I had a message next to the 1st tstat stating “successful refresh”, but no temperatures (indoor or setpoint) would trickle into the child device for that tstat. The 2nd tstat did not say anything next to it and its child device also had no info coming through. The refresh timestamp (on the 1st tstat) did not seem to change very often and I could not push a setpoint adjustment to either tstat.

In the past couple days I’ve noticed (while working on other projects in Vera) it has started refreshing the current indoor temp more regularly, but setpoint still said 0.0. Refresh interval is set to 120 and I just watched it refresh a few times while typing this post. I’m not sure what the issue was but perhaps it was transient - my Vera being busy (odd since it’s not doing much yet), or something on Honeywell’s end - who knows.

I just remembered from reading this thread months ago that having the tstats in Auto heat/cool changeover mode creates issues. I put one of my tstats in Cool mode and was able to push a setpoint to it from Vera. Success! :smiley: Verified with the 2nd tstat as well.

Time to go back and re-read the thread… looking for any info on Auto mode, to see if I could accomplish the same type of functionality another way in Vera. Texas transitional seasons have wide temp swings and Auto changeover is too convenient to lose.

(Edited to remove bit about cancelling holds programatically - info is in the first few posts and sample luup code provided is tested and working on my Vera. I am setting this up to place temperature holds on arming security system Away, and release the holds upon disarm.)

157

Late night tinkering with the vera and tstats…

I’ve created a scene that pushes cool/heat setpoint holds to both tstats when the alarm is armed Away or Maximum, and another scene that removes hold on disarm (tstats revert to schedule). Gave it a trial run earlier and it worked, takes about 20 sec after arming to change. Tomorrow is the first real test. :slight_smile:

I also think I have a strategy, albeit a rough one, to accomplish auto mode changeover using scenes that could be triggered by schedule (say every 15-30 min, or whatever is appropriate to how quickly weather in your house changes, lol). Requires 2 scenes per tstat. Pseudocode…

Scene 1: TStat Heat Switchover
Trigger: Schedule
Action: Set TStat mode to Heat
Lua Code: If AmbientTemp >= HeatSetPoint then abort scene (do not change mode)

Scene 2 would be the inverse, evaluating ambient temp vs cool setpoint and changing to cool if necessary.

Lua for scene 1 looks like this…

local lul_temp = luup.variable_get("urn:upnp-org:serviceId:TemperatureSensor1","CurrentTemperature",4) local lul_setpt = luup.variable_get("urn:upnp-org:serviceId:TemperatureSetpoint1_Heat","CurrentSetpoint",4) if (lul_temp >= lul_setpt) then return false end

That code worked (had to manually set tstat to 77 heat / 80 cool / cool mode; ambient was 76).

I’ll add a conditional to check what mode the tstat is in. No need to it to change to heat mode if it’s already there - only need to change if it’s on cool. I also specifically only want to change from heat to cool or cool to heat. I do not want vera to change it from off, in case the system was manually turned off.

I think it’s pretty rough to have to code 4 objects to manipulate 2, but in my noobness to Vera that’s the best and only idea I’ve got right now. If someone knows a better and/or easier way, please do share. :smiley:

This vera thingy is fun!

158

Having dug into some documentation I found how to change thermostat operating mode in lua code, so I can do this in one scene instead of four. Typical process for me - have an idea late at night and make it better when I’m more awake.

I did not yet find a way to trigger the scene whenever the TCC parent app performs a refresh - that would be ideal I think. So for now, I’ll set it to run on a scheduled basis.

Code below is working for me on veraedge/UI7. This example controls one thermostat (device ID 4). Like most things you need to know the device ID of your child thermostat device and edit that in place of the 4 at the end of each line.

[code]-- Declare and get ambient temperature, heat setpoint, cool setpoint, and operating mode

local lul_TS1_CurrentTemp = luup.variable_get(“urn:upnp-org:serviceId:TemperatureSensor1”,“CurrentTemperature”,4)
local lul_TS1_HeatSetPoint = luup.variable_get(“urn:upnp-org:serviceId:TemperatureSetpoint1_Heat”,“CurrentSetpoint”,4)
local lul_TS1_CoolSetPoint = luup.variable_get(“urn:upnp-org:serviceId:TemperatureSetpoint1_Cool”,“CurrentSetpoint”,4)
local lul_TS1_ModeStatus = luup.variable_get(“urn:upnp-org:serviceId:HVAC_UserOperatingMode1”,“ModeStatus”,4)

– evaluate conditions and change operating mode if necessary

if lul_TS1_ModeStatus == “CoolOn” and (lul_TS1_CurrentTemp < lul_TS1_HeatSetPoint) then
luup.call_action(“urn:upnp-org:serviceId:HVAC_UserOperatingMode1”,“SetModeTarget”,{NewModeTarget = “HeatOn”},4)
elseif lul_TS1_ModeStatus == “HeatOn” and (lul_TS1_CurrentTemp > lul_TS1_CoolSetPoint) then
luup.call_action(“urn:upnp-org:serviceId:HVAC_UserOperatingMode1”,“SetModeTarget”,{NewModeTarget = “CoolOn”},4)
end
[/code]

One could perform the auto-changeover function for multiple thermostats by copy/pasting the entire codeblock for additional thermostats and editing in their device ID.

159

A shortcut to get this working in Europe is to create us US account and register your device on that account.

So far it works just fine for me.

160

Sadly, I have to report that making a us account is not the way to go for me. Setting up the account was no problem and the plugin was working fine using my new account.

Downside is, that you can only select a US or Canadian location and therefore the clock on my Evohome is automatically set to that location.

I switched back to my European setup and hope that there will be a European version soon.