https Authentication help: Honeywell Total Comfort Connect

So it looks like we have success!

Thanks to mikee and CudaNet I am now able to successfully get data from the WiFi thermostats, and send data to change a setting.

So at this point it’s basically time to really start building the app itself.

It’s not clear to me at this time if I’ll be able to query the API to get a list of locations and devices associated with an account, or if for at least the short term I’ll require the user to enter in device Ids via the UI. Then I’ll add standard HVAC thermostat child devices and start building out the implementation.

Awesome ! I have no doubt others will contribute, after all - that’s what makes this product great (the forum and it’s members)…

[quote=“JoeyD, post:21, topic:185223”]So it looks like we have success!

Thanks to mikee and CudaNet I am now able to successfully get data from the WiFi thermostats, and send data to change a setting.

So at this point it’s basically time to really start building the app itself.

It’s not clear to me at this time if I’ll be able to query the API to get a list of locations and devices associated with an account, or if for at least the short term I’ll require the user to enter in device Ids via the UI. Then I’ll add standard HVAC thermostat child devices and start building out the implementation.[/quote]

[quote=“JoeyD, post:21, topic:185223”]So it looks like we have success!

Thanks to mikee and CudaNet I am now able to successfully get data from the WiFi thermostats, and send data to change a setting.

So at this point it’s basically time to really start building the app itself.

It’s not clear to me at this time if I’ll be able to query the API to get a list of locations and devices associated with an account, or if for at least the short term I’ll require the user to enter in device Ids via the UI. Then I’ll add standard HVAC thermostat child devices and start building out the implementation.[/quote]

Awesome work! thanks to all…

Also, be careful hitting their server too many times in x amount of time. I read last night that they recently implemented a short period lockout (to keep polling to a minimum), I’d say every 5 minutes or so should be safe…

Thanks…I’ll make that the default refresh rate.

That also explains some sporadic authentication issues I’ve encountered during development. :slight_smile:

So I have something that those following this thread can test. What is done so far:

  1. Installs a parent device. (Honeywell TCC).
  2. Allows you to enter up to three thermostats to connect to
  3. Creates the child thermostat devices for those IDs
  4. I think I have put in support for all the UI elements (at least with UI7)
    • Indoor Temperature
    • Current set-point
    • Fan mode
    • Thermostat mode (Heat / Cool / Auto).
  5. The UI information will refresh every 5 minutes

Right now…communication is ONE WAY. Only reading the data and updating the UI. You can try and click buttons to change settings, but it won’t do anything. This is more or less designed to test the set-up process, authentication and updating of the UI. So if you install this, please report back on if it appears to work, or if you’re having any problems.

TO INSTALL:

  1. Download the attached zip file.

  2. Upload the 6 files contained in the zip to your vera. For UI7

    • Apps–>Develop Apps–>luup files
    • Click on the Upload button.
    • You can select multiple files at once, or upload 1 one at a time, but you must upload all 6.
  3. Add the parent device:

    • Apps → Develop Apps – > Create Device
    • In Upnp Device Filename type the device file name: D_HoneywellTCC1.xml
    • In Description type what you want, such as: “Honeywell TCC”
    • Click “Create Device”
  4. I typically reload luup at this point for good measure:

    • Devices → The device you just added → Click on “>”, then click on Advanced and scroll to the bottom. Click on “Reload Engine”
  5. After luup reloads, go to the “TCC Setup” tab of the new device

  6. Enter your Total Connect Comfort user name and password, and click “Update”. After a few seconds, you should see that authorization is “successful”

  7. Enter your wifi device ids in the spaces provided (up to 3) and click “Update Ids”. (To get your device IDs, log in to mytotalconnectcomfort.com. Navigate to one of your thermostats (so that you see all of the controls for an individual thermostat). In your bowser URL, you will see something like “Honeywell Home - My Total Connect Comfort”. Where XXXXXX is the device ID for that thermostat.

8.) After you update the IDs, it will take Vera a minute or two to add the child devices and then sync them. they should refresh every 5 minutes.

Good luck!!

Not displaying correctly in UI 1.5

It’s connecting at least !
So awesome to see this being brought to life.

[quote=“rayp”]It’s connecting at least !
So awesome to see this being brought to life.[/quote]
How did you enter the password to connect? The field is not displaying on mine.

Entered it in the advanced tab.

Thanks for posting…this is exactly the kind of feedback I’m looking for!

Unfortunately, I don’t have UI5 to test with…I’ll see if there’s something obvious that might fix the UI placement for UI5. Otherwise, I may need someone with UI5 to take a look at the .json file and tweak it.

Yeah I’m just sitting in my office with a couple of minutes to kill. I too am running UI5 so let me install and provide my observations…

How is the systems ON/OFF state identified on the Vera thermostat?

I guess that depends on what you mean by on/off state.

The vera (UI7 at least) themostat shows you

  1. Which “Switch Position” your themostat is in:
    – Heat Mode
    – Cool Mode
    – Off
    – AutoChangeover

  2. The UI also shows you what your “fan mode” is set to:
    – Continuously On
    – Periodically On (also known as “circulate”
    – Automatic (on when heating or cooling is active)

In other words, what the UI does not show you (at least from what I can tell) is whether or not your unit is actually running.

So if you want to know “hey, is my unit running or not”…I don’t think you can tell. Does anyone know if I’m wrong?

Note this is no different than going to mytotalcomfortconnect.com. You cant tell if your unit is “on” or “off” either. I imagine this may be a liability / design thing? Technically, the thermostat knows if it is signalling your unit to turn on, but I guess that doesn’t imply your unit IS actually on if there is some connectivity issue or failure with your heat or ac unit. So it’s likely that by design – it gives the state of your thermostat settings…NOT the state of your furnace / ac unit itself.

I did not see anything obvious in the packet of information that comes back to indicate a “running” status…other than perhaps a variable called “load”. I can look at that and see if that’s an indication that your unit is at least signalled to turn on.

That is exactly what I was asking… ;D Sorry to make your translate…

I’ve always found it strange that TCC doesn’t identify the systems running state, yet every thermostat I’m aware of (I’m an HVAC Tech) (including the entire Honeywell digital line) display’s this information for the user on the actual stat… Crazy I tell ya Crazy…

So I guess it would require a custom plug-in then ?

Thanks for your reply.

I guess that depends on what you mean by on/off state.

The vera (UI7 at least) themostat shows you

  1. Which “Switch Position” your themostat is in:
    – Heat Mode
    – Cool Mode
    – Off
    – AutoChangeover

  2. The UI also shows you what your “fan mode” is set to:
    – Continuously On
    – Periodically On (also known as “circulate”
    – Automatic (on when heating or cooling is active)

In other words, what the UI does not show you (at least from what I can tell) is whether or not your unit is actually running.

So if you want to know “hey, is my unit running or not”…I don’t think you can tell. Does anyone know if I’m wrong?[/quote]

Do you know if any other web enabled stats report running state?

Note this is no different than going to mytotalcomfortconnect.com. You cant tell if your unit is “on” or “off” either. I imagine this may be a liability / design thing? Technically, the thermostat knows if it is signalling your unit to turn on, but I guess that doesn’t imply your unit IS actually on if there is some connectivity issue or failure with your heat or ac unit. So it’s likely that by design – it gives the state of your thermostat settings…NOT the state of your furnace / ac unit itself.

I did not see anything obvious in the packet of information that comes back to indicate a “running” status…other than perhaps a variable called “load”. I can look at that and see if that’s an indication that your unit is at least signalled to turn on.[/quote]

Yeah, I looked for this also. Note the zwave Honeywell does tell you when it is calling for heat but I don’t yet see it in the wifi version. Also, I don’t see any indication in vera’s UI (UI7) of this value (ModeState) although it is recorded. AutHomationHD does show this value in its tile. I wish vera’s stock thermo display was a bit more configurable (like disabling the fan settings when you have a heat only boiler setup) and showing the state. I think the perfect place for this would be the icon. It changes with ModeStatus but this info is duplicated in the buttons …

Just checked, StatusHeat seems to indicate heat calling on/off. (1/0) Use this to set ModeState.

Thanks! I will incorporate that. (Along with StatusCool…)

Now if you really want to impress me, figure out WTF is up with UI5 variable display. :slight_smile:

I have been granted access to a UI5 unit and I can’t make any progress on what is probably something really dumb that I’m missing… >:(

Loaded all the files, then restarted LUUP.
Created the device, restarted LUUP and got the message to configure.
Configured the plugin using my ‘stat’ device and credentials.

The credentials gave success but I got a refresh error code 3(Unsuccessful. Error code: 3). Waited for a refresh (300s) and then received an error 200, looks as if my credentials were cleared. I added them back in and the refresh occurred but the last log entry is probably keeping me from seeing the stat results…

06      01/12/15 14:11:51.100   Device_Variable::m_szValue_set device: 235 service: urn:joeyd-com:serviceId:HoneywellTCC1 variable: credAuthorized was: Unsuccessful.  Error code 200 now:  #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 __LEAK__ this:1245184 start:2727936 to 0x1a74000 <0x2f6df680>

06      01/12/15 14:11:51.796   Device_Variable::m_szValue_set device: 235 service: urn:joeyd-com:serviceId:HoneywellTCC1 variable: cookieRefreshTime was: Mon, Jan 12, 02:10:56 PM now: Mon, Jan 12, 02:11:51 PM #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f6df680>

06      01/12/15 14:11:51.801   Device_Variable::m_szValue_set device: 235 service: urn:joeyd-com:serviceId:HoneywellTCC1 variable: cookieRefreshTimeSuccess was: Mon, Jan 12, 01:08:37 PM now: Mon, Jan 12, 02:11:51 PM #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f6df680>

06      01/12/15 14:11:51.802   Device_Variable::m_szValue_set device: 235 service: urn:joeyd-com:serviceId:HoneywellTCC1 variable: credAuthorized was:  now: Successful #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f6df680>

01      01/12/15 14:11:52.647   LuaInterface::CallFunction_Timer-5 function startupDeferred failed [string "local version = "1/9/2015 @JoeyD"..."]:264: attempt to concatenate local 'fanMode' (a nil value) <0x2