WE ARE NOT ALONE IN HAVING DOWN STATS - GOOD NEWS!!!
After speaking with the Honeywell customer support, it appears Honeywell did an upgrade last night and they are having issues with many customers seeing the same issues we are seeing. SO, they said the usual sorry and give it a few hours. The good news to me, it’s nothing we did or them blocking folks like us trying to get workarounds to suit our needs. Will keep ya posted if I get any update info. I too will be out later though.
Absolutely nbothing to do with my scene or us trying to interface Vera.
FYI All my stats are back up and running. They must have resolved the issue on the servers.
Another issue I found was that I had to change my user name in the plugin from the username I created with TCC to my registered email address with them. This worked for a while, but then the plugin didn’t save my new login credentials. It took a few days but I discovered Ihad to update the username fields on both the TCC setup page AND the advanced tab.
So far, so good.
Now to figure out the auto changeover.
Lingerba, did you create that as a separate scene or is it combined with another one?
I have not created this scene yet, it was ShawnInFL’s idea. I have not had the authentication issue in a couple of weeks, so I am just keeping my fingers crossed at this point.
It might be that the reason the update was done by Honeywell (the one that knoceked out all remote access, even their own website) was in fact the same reason for our issue requiring the scene. I have had no trouble since the scene but it could be that there is in fact no need for the scene since the last update to honeywell servers.
So of course right when I brag about not needing that scene, I had the login issue again. I created the scene per ShawnInFL’s instructions and it logged back in fine. I set the interval for 4 hours. We will see how it goes.
On a different but related note, I have applied for the Honeywell TCC API multiple times using my personal email address and I never got a response. I applied a couple of months ago using my work email address and I actually got a response from Honeywell. The guy I talked to was real nice and he admitted that Honeywell was keeping a tight grip on their API. He said they were actively working on integration with multiple other vendors but he was not sure if Vera was one of them. He went on to tell me that they were aware that people had reverse engineered the online access and were able to control the thermostats that way. He said that was against what Honeywell was trying to do, so those accounts were suspended (people noted this with frequent poll times earlier in this thread). Anyway, the point I am trying to get to with this is that the Honeywell guy told me that they want to push data out to other systems (i.e. Vera) rather than those systems polling for the data. In its current state, the Vera plugin does not operate this way so I think we should expect to continue to see issues…
I guess Honeywell just doesn’t want to relinquish control of their systems to someone else, like the end user. The reason I purchased the thermostat was to have Vera control and backup Wifi control should it lose interface with Vera.
Thank you for trying and pushing to get the API. I hope they loosen their reigns and finally grant it. So many talented developers here and its too bad they won’t work with them or allow them access.
I finally had to delete the device and reload it. I hope that solves some of my issues. For some reason, the device would not allow me to update the login username and password.
I tried making sure that they understood that their main competitors for this (mainly the Nest) were a lot more open with their API. Honeywell didn’t seem to care…
I got mine for the same exact reasons why you are mentioning.
Since I just activated the re-login scene, we will see how it goes for me. I’ll let you know if I have any issues.
Awesome suggestions on reverting back to Ver. 1.0. I want say that it worked for me, adding device ID and I’m back to being able to see/use my thermostats, when I had to reload the app after a full reload about a month ago… I was getting frustrated till I dug through this, found lingerba’s and Joey’s old notes and followed what they said. I’m not a programmer (actually an Exchange Admin who deals a lot with powershell), but I might play around with this to grab the newer interface (which I liked better) - if I can make it happen… I’ve missed having the ability to control my tstats from Vera. Thanks for helping me get it back… 
Well, mines back down again. I deleted and reinstalled the device and it worked for a while, but can’t control the Tstat from Vera or get updates unless I manually update the login credentials. I even changed the refresh time to 15 minutes.
same here lost functionality. What a shame 
to think I wasted nearly a grand so I could control them from vera.
All 3 of mine are working just fine…have you tried my scene?
SEE REPLY #169 for photos if needing additional explanation
SHORT VERSION:
- Create NEW SCENE
- ADVANCED TAB
- Find your Parent AC Device in the PICK A DEVICE Drop Down
- Press ADD
- Choose “SetUsernamePassword” in the Drop Down
- Provide your Honeywell USER ID and PASSWORD
- SCHEDULES TAB - ADD (every 4 hrs)
- SAVE
Wait a few minutes and try RUN on the new scene to confirm working - Look for AUTHORIZATION PASSED in Vera GUI (top of web app).
Shawn, it’s sad that we have to resort to this as Honeywell isn’t working with the end user at this time. I had set the scene up earlier, but without the username/password action. I will try and see if it works.
I’m about ready to replace the Honeywell Tstat with another, dedicated zwave one if this doesn’t work. The whole idea was to have one controller running the house and Honeywell does not like to play nice.
I hear ya but would save my money for now. The scene and plug in seems to be working fine. For now at least GL
Honestly, I think the issue is with the fact that we are using the old plug-in. I think (guessing) that the old plug-in is not handling a failed login attempt properly and failing there rather than trying to login again. So I don’t fully blame Honeywell for this specific issue. However, if Honeywell would be more helpful, the newer version of the app would still be working so I agree I wish they would get their act together.
I never got to use the newer app, for me, I’m just super happy I can control all three stats with my voice and add them to my many scenes. Working great here, just hope that don’t cut us off at the pass LOL
I am using UI7 and your scene does not seem to have the same options as shown in your pics
Sorry, I am on you UI5. Perhaps another member can assist you with UI7. This solution seems to work very well on UI5.
I am UI7 and it works fine. I will not be in a position to help you much for a couple of days, but I just wanted to reply and confirm that it does indeed work with UI7.
Yesterday, I created the scene and set it to update the username/password every hour. I also changed the parameters for the thermostat device to poll every 15 minutes thinking this would not be too frequent. It was working fine last night, but when I got up this morning to check and the interface device named HONEYWELL APP, it said the refresh was successful, but I could not adjust the temperature in the Vera web interface from the device from a scene or from a third party app. :-\
I’m just about to go straight z-wave and forget the web interface Tstat. Too much hassle to get it to work reliably.