I seem to be using the "C" version for some reason I see "B" referenced a few posts up, but...
FYI to anyone that's maintaining this driver:
Those posts above are from 2021 when "B" was the best... now that it's 2022, and "C" is better, but the Parent/Child version is best 
I've read the report regarding: Updated supportedThermostatModes and supportedThermostatFanModes to add double quotes to support HE platform version 2.3.3.x
I'm looking at the cascaded impact.
4 Likes
Released the code with "\" for Platform v2.3.3.x
Don't want to hijack this topic because it's for the "other models" of Honeywell WiFi than "My" code. Please comment further in the respective topics:
OR
2 Likes
Goodday to all. I've installed the above parent child drivers, but I'm running into the following problem:
I live in Greece. Apparently honeywell has two total connect versions. One for the US (mytotalconnectcomfort) and the international one (international.mytotalconnectcomfort)
I had no idea. I found out when trying to hook up my thermostat with the hubitat. When I tried to log into the standard mytotalconnect website it didn't recognize me. I had to re-register an account there (with bogus address etc because I live in Greece) , add my thermostat there, and hubitat could access it fine. However since it's using a bogus location I can't add my proper location to it for outside temperature etc. So I switched the thermostat back to the international account, which made it inaccessible again for the hubitat. I did sharpen my hacking skillzz by changing the URL in the device code to point to the international site, but that didn't help.
Anyone ever ran into this problem ? Google Home operates my thermostat without problems, I might add. So technically it should be possible, even on the international account. I tried to connect Google Home to the hubitat, but that just allows google to control hubitat. Haven't found any way to let hubitat control a device connected to Google Home.
But then again, I'm new to the smart world. Any help greatly appreciated.
1 Like
I have the same issue. Or challenge to put a positive spin on it 
My Honeywell system is also registers with international site as well. I didnāt have the gumption to try and move it to the US site ti try it out.
Any thoughts.
Cheers.
If Iām looking at the right driver then changing line 69
public static String tccSite() { return "mytotalconnectcomfort.com" }
to the international site should fix your issue.
3 Likes
I'll try that. I had given up on it.... Thanks !
It doesn't work as far as I can tell, to just change the tccSite. Honeywell does not document this API. It's all been 'reverse engineered' and the same will have to be done for the international site.
I don't want to get too deep in munutia but as an example, the minimum number of cookies received from Honeywell US, is 8. For International, it's 4. In other words, the split is likely to get larger, not smaller. How to handle that falls to me, but without an international Thermostat to test, I can't get far.
Until this week, I only had one Thermostat. 
I certainly don't have more than one HVAC system, so a 2nd Thermostat couldn't be used. However, this week I upgraded my Thermostat to a RTH9585 and now have two registered Thermostats in the US. My thought is to take the old one and get it registered to International. (I tried it, but Honeywell's site rejected it saying it's already registered.) At this point it's not powered and I'll have to build a test jig to get it powered. Which is another way of saying, I can't fix it in a day.
If I make progress, I'll probably add to the existing topic which is more TCC (cloud) related than where this thread started (9000 series)
4 Likes
Whatever you manage to do, just know that your efforts are very much appreciated. Thanks !
