Ok - gave it a try. Took me a few attempts, so the new Thermostat came in at #48. It’s missing the “altid” - not sure if I should manually enter it, but it’s still not reporting any info and clicking the buttons yield no changes. The Thermostat_Old is my old TRANE, I just haven’t deleted the entry yet.
The altid is important. Looking at your screenshots, let’s go back to device 45 for a sec. The altid is TCC_XXXXXXX (7 digits). It should only be 6 digits and it should be the same as your thermostat ID shown in the TCC setup on device 44. So try fixing that first (you may have to edit it in the variables tab). Then if that doesn’t get you going, try adding the altid in your new device. It should be TCC_XXXXXX (6 digits).
I noticed that my thermostat IDs are all in the 900,000s. So I guess it is possible that your ID is in the 1 millions (7 digits). If you verify that your thermostat ID is 7 digits long, this could be the issue.
It is 7 digits, or at least I think it is. Screenshot of the Honeywell site attached.
Maybe I’m not dropping a digit I should?
[quote=“cohibafan, post:263, topic:185402”]It is 7 digits, or at least I think it is. Screenshot of the Honeywell site attached.
Maybe I’m not dropping a digit I should?[/quote]
Nope, you shouldn’t have to drop a digit. I am looking through the code to see if anything limits it to 6-digit numbers. In the mean time, is your system setup for “auto changeover” meaning it changes from heat to cool as necessary? If so, try putting it in one mode or the other (through Honeywell’s interface) and then re-login with the Vera app.
I hear ya on the digit problem regarding the code. Maybe I’m one of the few with 7 digits.
I currently only have an AC unit, no heat, so I’ve told the thermostat that I don’t have a heat unit and so it only shows the “Cool” option, but I’ll play around and see if there’s a magic series of clicks to get them chatting.
First as a disclaimer: I am not a programmer. I looked through the six files associated with this app. Only one of the looked like it could have any impact on this. Attached is the updated file where I changed “TCC_######” to “TCC_#######”. You can try loading this file and see what happens. You may have to uninstall what you have and reinstall with this updated file. But I would try just adding this file first to see what happens. No promises either way.
[code]function refreshAllStatus()
– performs an immediate refresh of the status for all thermostats.
local childID
local altID
local statResult
local statText
for i=1,3,1 do
luup.variable_set(TCC_SID,"t." .. i .. ".refreshStatus" ,"",TCC_DEVICE)
end
for k, v in pairs(luup.devices) do
-- if I am the parent device
if v.device_num_parent == TCC_DEVICE then
childID = k -- this is the device number as known to vera
altID = v.id -- this is the altID (TCC_######)
statResult, statText = refreshStatus(altID)
end
end
return statResult, statText
end[/code]
I glanced at this and it looks like you changed the comment…
[quote=“lingerba, post:266, topic:185402”]First as a disclaimer: I am not a programmer. I looked through the six files associated with this app. Only one of the looked like it could have any impact on this. Attached is the updated file where I changed “TCC_######” to “TCC_#######”. You can try loading this file and see what happens. You may have to uninstall what you have and reinstall with this updated file. But I would try just adding this file first to see what happens. No promises either way.
[code]function refreshAllStatus()
– performs an immediate refresh of the status for all thermostats.
local childID
local altID
local statResult
local statText
for i=1,3,1 do
luup.variable_set(TCC_SID,"t." .. i .. ".refreshStatus" ,"",TCC_DEVICE)
end
for k, v in pairs(luup.devices) do
-- if I am the parent device
if v.device_num_parent == TCC_DEVICE then
childID = k -- this is the device number as known to vera
altID = v.id -- this is the altID (TCC_######)
statResult, statText = refreshStatus(altID)
end
end
return statResult, statText
end[/code][/quote]
[quote=“CudaNet, post:267, topic:185402”]I glanced at this and it looks like you changed the comment…
[quote=“lingerba, post:266, topic:185402”]First as a disclaimer: I am not a programmer. I looked through the six files associated with this app. Only one of the looked like it could have any impact on this. Attached is the updated file where I changed “TCC_######” to “TCC_#######”. You can try loading this file and see what happens. You may have to uninstall what you have and reinstall with this updated file. But I would try just adding this file first to see what happens. No promises either way.
[code]function refreshAllStatus()
– performs an immediate refresh of the status for all thermostats.
local childID
local altID
local statResult
local statText
for i=1,3,1 do
luup.variable_set(TCC_SID,"t." .. i .. ".refreshStatus" ,"",TCC_DEVICE)
end
for k, v in pairs(luup.devices) do
-- if I am the parent device
if v.device_num_parent == TCC_DEVICE then
childID = k -- this is the device number as known to vera
altID = v.id -- this is the altID (TCC_######)
statResult, statText = refreshStatus(altID)
end
end
return statResult, statText
end[/code][/quote][/quote]
Ah crap your right, I ignored the “–” since it was not the first characters of the line…see, I told you I’m not a programmer… :o
We really need someone capable to pick up this plugin since JoeyD isn’t around anymore…
Agreed about JoeyD.
I did a search through the luua and don’t see any other reference to “######”. Maybe there is no limitation set in the code to number of digits 
So what is it that you are trying to accomplish between Vera and Honeywell? Maybe you can do it with IFTTT?
Hey, kudos for trying and more kudos for helping out others. I’m tempted to go through all of JoeyD’s code and see what’s going on. He has abundant debug code commented out so that would help. I’m just buried in stuff to do…
Can someone tell me exactly what the issue with this plugin is ? In really short summary.
[quote=“lingerba, post:268, topic:185402”][quote=“CudaNet, post:267, topic:185402”]I glanced at this and it looks like you changed the comment…
[quote=“lingerba, post:266, topic:185402”]First as a disclaimer: I am not a programmer. I looked through the six files associated with this app. Only one of the looked like it could have any impact on this. Attached is the updated file where I changed “TCC_######” to “TCC_#######”. You can try loading this file and see what happens. You may have to uninstall what you have and reinstall with this updated file. But I would try just adding this file first to see what happens. No promises either way.
[code]function refreshAllStatus()
– performs an immediate refresh of the status for all thermostats.
local childID
local altID
local statResult
local statText
for i=1,3,1 do
luup.variable_set(TCC_SID,"t." .. i .. ".refreshStatus" ,"",TCC_DEVICE)
end
for k, v in pairs(luup.devices) do
-- if I am the parent device
if v.device_num_parent == TCC_DEVICE then
childID = k -- this is the device number as known to vera
altID = v.id -- this is the altID (TCC_######)
statResult, statText = refreshStatus(altID)
end
end
return statResult, statText
end[/code][/quote][/quote]
Ah crap your right, I ignored the “–” since it was not the first characters of the line…see, I told you I’m not a programmer… :o[/quote]
At first glance, there doesn’t appear to be a limitation. Again, first glance. It’s been forever since I stepped through his code.
Agreed about JoeyD.
I did a search through the luua and don’t see any other reference to “######”. Maybe there is no limitation set in the code to number of digits :([/quote]
I just want to be able to trigger the AC to turn on and off with my scene controller and manually from my phone.
Right now I can only use the Honeywell app to control the thermostat.
I’d like to set up some scenes to turn on the air for 1 hour. Run the fans for 1 hour, etc.
Then when I leave the house I trigger a “Leave” scene that shuts everything down including the AC.
Simple control really - I’d even be okay if I couldn’t control the temp, just on or off would be ideal.
I do like the display of the Honeywell. Having the humidity and outside temp in a color panel is nice.
Real short summary:
First the version of the app at is available at the app store stopped working. It wold log in successfully, but it wouldn’t “find” any thermostats. Then someone discover a beta version of this app was still working. My guess is because you have to manually enter your thermostat ID rather than it being discovered automatically.
Then an issue started with this (older) version of the app which was failed authentication after a certain period of time. My speculation is that once it fails authentication, it doesn’t try again. Most people’s work around for this was to create a scene that re-logs in with Honeywell every so-often. That fix has worked fine for me.
An now this latest issue that @cohibafan is having. His issue is that the parent “app” is not passing the thermostat data to the actual child “device” that the app created, even though the parent app says it successfully connected to Honeywell and successfully verified the thermostat ID number. This is the first case that I know of where someone has a 7 digit thermostat ID.
I just want to be able to trigger the AC to turn on and off with my scene controller and manually from my phone.
Right now I can only use the Honeywell app to control the thermostat.
I’d like to set up some scenes to turn on the air for 1 hour. Run the fans for 1 hour, etc.
Then when I leave the house I trigger a “Leave” scene that shuts everything down including the AC.
Simple control really - I’d even be okay if I couldn’t control the temp, just on or off would be ideal.
I do like the display of the Honeywell. Having the humidity and outside temp in a color panel is nice.[/quote]
You can actually probably do most of that with IFTTT. Honeywell Total Connect Comfort Integrations - Connect Your Apps with
I would be frustrated not being able to do these simple controls that you are asking to do in Vera.
Ok, I remember some of this. When JoeyD was developing (like never sleeping developing) we noticed that if a login failed the stat(s) never recovered/refreshed. This was the beta, the store release must be where he corrected it (or tried to). I’m currently running version 1.2 (appid 8132) and the only issue I have is the message:
'HNYWL TCC: : Honeywell thermostat user authentication failed. Check TCC SetupSeems this is caused by updateCredentials which in turn calls retrieveLocationsAndDevices. I need to get a dump of what’s being returned by that function [return resultCode, resultText , tblLocations] . I don’t know when I’ll get a chance to do this. I was hoping to defer this until I tried to make this plugin work under openLuup. Let me look through the posts on Cohibafan. I don’t see why the [7] digit would cause issues, at least not in the Lua file. I understand Lua really well but I don’t know how a plugin is constructed so I’ll do what I can to help. No guarantees …
Edit: I also need to check retrieveLoginCookie
Real short summary:
First the version of the app at is available at the app store stopped working. It wold log in successfully, but it wouldn’t “find” any thermostats. Then someone discover a beta version of this app was still working. My guess is because you have to manually enter your thermostat ID rather than it being discovered automatically.
Then an issue started with this (older) version of the app which was failed authentication after a certain period of time. My speculation is that once it fails authentication, it doesn’t try again. Most people’s work around for this was to create a scene that re-logs in with Honeywell every so-often. That fix has worked fine for me.
An now this latest issue that @cohibafan is having. His issue is that the parent “app” is not passing the thermostat data to the actual child “device” that the app created, even though the parent app says it successfully connected to Honeywell and successfully verified the thermostat ID number. This is the first case that I know of where someone has a 7 digit thermostat ID.[/quote]
Interesting…
Edit: Although it does redirect (302). Now I’m stuck on where he’s storing the cookie he received… He mentions it’s global.
Mind you I’m hacking his code to straight Lua to see how far I can get…
auth_response{ [1] = <html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="/portal/">here</a>.</h2>
</body></html>Thanks for the help!
If I can test or provide data (screenshots, etc.) pls do not hesitate to ask.
Hopefully we can get this to work… and maybe even update the official Vera app for Honeywell - that would be ideal for all.
Same for me, please let me know if there is anything that I can do to help!