Honeywell TCC Total Connect Comfort Drivers

The best solution I've found is to use SmartThings API access so I don't get rate limited. Don't know how much longer that will work for though with how they are removing classic.

1 Like

Explain?

SmartThings has a partner connection allowing them to poll more frequently. Use the partner integration within smartthings and then hubconnect to control.

1 Like

Ah, I thought that is what you meant. Unfortunately, without a Smartthings hub I cannot make an account. They ask for the hub code (or something like that) when making an account, and I have no such thing, so it won't even let me do cloud based stuff.

There are probably other partners they don't rate limit. ST was just the first I came across since I had an old hub.

1 Like

I'm in the same boat. If they disconnect hubconnect from working I'm left with TCC, because IFTTT is no longer an option.

1 Like

Wink is another, but I am not going back to that!

Maybe someone will chime in with another that we haven't thought of.

If they disconnect hubconnect, I'll probably just replace the thermostats with some zwave thermostats. Lots to choose from now. The only reason I haven't already is I am trying to save up cash in case I get laid off. I'm in the oil and gas business.

Most Zwave stats are ugly and lack function. I need multi-stage (3 heat and 2 cool), with lockouts for my heat pump using an outdoor sensor. That one thing disqualifies most thermostats period, smart or not.

Plus I would miss the dehumidify on demand, ventilation, auxiliary inputs and outputs of my current thermostat. (Prestige IAQ Pro). And I also would have to deal with having a noisy thermostat on the other side of the bedroom wall instead of having the totally silent IAQ Equipment Module in the basement.

That's way more complicated than my setup. I just have two separate units. One for the main living areas and one for the bedrooms.

1 Like

Thermostats make noise?

Lots of them have mechanical relays for heat and blower. At least the Honeywell ones typically do. You can definitely hear those clacking away every time the heating or cooling or fan turns on.

Learned something new.

You can do this now. It is a little complicated - and you have to use the new SmartThings app and not the Classic app.

I am fairly certain I tried both a while back, probably around June/July. It kept asking for that code no matter what I did.

Is there someplace that outlines that workaround?

Use the new app - not the Classic app. I just did it with a dummy account and added my neighbor's ecobee as a cloud integration. Worked perfectly .....

1 Like

This is exactly my issue as well. I have 2 Prestige IAQ’s and have the same setup + humidifier. I’d need more wires run to my walls if I wanted to handle everything with a regular thermostat. If hubconnect stops working in ST land I will be sad.

1 Like

I think the API calls you linked to are for a relatively new "Honeywell Home" API - there's an older API (Honeywell "Total Connect Comfort") that, I think, was used by drivers such as (GitHub - HubitatCommunity/HoneywellThermo-TCC). Any idea where that Total Connect Comfort API can be found? The new "Home" one doesn't (yet) support the Redlink line of thermostats.

As an further FYI - I have six thermostats and I was hoping to rework the HoneywellThermo-TCC driver so that, rather than having to set up 6 copies, which would each generate calls to the API and likely have the throttling problem you mention, I was going to try and set it up as one driver which creates child devices for each thermostat and makes a single call to the API to get all the device info. from honeywell in one call / transfer. Obviously, this only makes sense if the API supports getting all the data at once. That's what I want to figure out first.

1 Like

it works fine at my two houses with a rate of every hour.. i belive they were blocking the st ips not the account itself becuae i was blocked there but now it is working again..