That's an Attribute in the Parent/Child version and has a value that is inherent to the changes made from the conversion. I have chosen to focus all development on the Parent/Child version. I have backported most benefits to the Single code.
I have both versions installed on a couple of hubs and use the disable feature to dictate which runs. 
Well, now please if you can help and explain how to create this Parent and Child device, because the drive I'm using I don't know if it's the right one. Where can I find more information and download it correctly?
It's in HPM and you can have them both installed, as long as only one of them is active at a time.
Thanks for your help, I've now managed to install the drive to control parent/child.
But my connection problem continues.
To secure the login/password/id, I had already tried it directly on the website.
But in the logo I see:
dev:48322024-07-02 12:33:33.965 PMinfoAC Master Thermostat TCC transaction: failed
dev:48322024-07-02 12:33:33.957 PMinfoAC Master Thermostat TCC transaction: retry login
dev:48322024-07-02 12:33:26.976 PMinfoAC Master Thermostat TCC transaction: retry login
dev:48322024-07-02 12:33:25.373 PMinforeceived Poll request from AC Master Thermostat (Poll Interval: 10 mins)
dev:48322024-07-02 12:33:24.799 PMwarndescription logging is: true
dev:48322024-07-02 12:33:24.797 PMinfoUpdated AC Master Thermostat (4831-Thermostat_0)
dev:48322024-07-02 12:31:44.286 PMinfoAC Master Thermostat TCC transaction: failed
dev:48322024-07-02 12:31:44.278 PMinfoAC Master Thermostat TCC transaction: retry login
dev:48322024-07-02 12:31:37.177 PMinfoAC Master Thermostat TCC transaction: retry login
And if I now try to connect again via the website, I get this screen.
Hola @csteele,
I'm going to adopt the new drive that works with children, because I want to add more thermostat and I think it's smarter.
I still have the problem of not connecting, and I've increased the time now to 15 minutes to see if that solves it.
Now something that catches my eye is that the temperature is in fahrenheit and my system is set to celsus.
In the previous drive this correction had already been made.
Thanks.
I'm wishing my memory was as strong as yours
Can you turn on debug logs and then hit refresh, please? You should get a log line like this:
dev:2471 2024-07-08 03:48:59.682 PM debug received Refresh request from Honeywell Thermo Downstairs to Honeywell TCC 'refresh', unit: = °F, fromUnauth = false
The "unit" will display what the driver is getting from the Platform. That value is stored in "location.temperatureScale" and that is tested in about 20 places in the driver. In other words, the screen cap you provided is what it looks like in the GUI, and is read by apps and drivers as "location.temperatureScale" as just a single letter, either C or F
It's used like:
float val = (location.temperatureScale == "F") ? cd.currentValue("heatingSetpoint") - 1 : cd.currentValue("heatingSetpoint") - 0.5
[Which is checking and if it's F then reduce the heat setpoint by 1 whole degree but if it's Not (because it's a C) then reduce the setpoint by half a degree.]
I think you are saying that ONE of the 20 or so places it's checking isn't right or that there should be one more check.
Problem has just been solved, I had to increase the time to 30 minutes, I finally got a connection, and then the temperature updated to C, and I can control the AC. Sorry for the inconvenience, but with such a long time I'm going to have to rethink some of the AC management rules.
Honeywell puts you in a condition where they 'deny' everything for some time period. Once you've backed off for long enough, you can go back to a more rapid polling. This hits me all the time during development. I'm testing something and clicking refresh at a rate that gets me "banned". I have to go get a drink, get rid of a previous drink, or something similar, then I can resume my testing.
Well, next time call me to have a drink together, oops, test it out together 
sorry.
csteele .. any chance the driver can be updated to work with easy dashboard? I get the not supported error when I try to add it
I don't use Easy Dashboard BUT I did create one when it was introduced just so I'd know what people were talking about. Turns out I included my Honeywell Thermostat in that experiment, oh so many months ago
Is your Honeywell T-stat connected through Total Connect Comfort a single standalone t-stat, or a child device?
I just removed my three child devices from Easy Dashboard, saved and then tried to re-add them, and I get the following:
Mine is working fine on EZ dash.
Ok, Well then parent/child structure is not the variable that is causing the issue.
One other idea: In Hubitat, my fan mode reports as Unknown because the TCC site does not pull that data from my T-stats, so that data is not available on the TCC site for Hubitat to get.
Could that be what is causing the issue for this tile in EZ dashboard?
It works fine in the original dashboard. Looks like this:
Usually EZ dash prompts you with the missing value.
That said, there was (are?) issues with EZ dash and missing things like fan, or heat/cool modes. I would have to go back and search to see if Victor ever added a workaround for these missing items like I remember he said he would at one point in time.
Thanks, that would be great. I'm not getting any prompts from EZ dash...
so here is my dilemma.. I have csteele's "Honeywell Thermo Parent and WIFI Thermo Compnent" installed as well as the "API C" version. API C allows easy dashboard, but the setting of fan mode give me this..
2024-10-23 11:13:33.545 AM[error]java.lang.NullPointerException: Cannot set property 'FanMode' on null object on line 253 (method setThermostatFanMode)
[2024-10-23 11:13:33.499 AM[debug]setThermostatFanMode: circulate
The Wifi version works but can't be used on EZ Dashboard.. when you try and set that one up I get the "Missing Attributes:
supportedThermostatFanModes, supportedThermostatModes" error.
what am I missing?
Initially I thought it was a platform issue that crept in related to the NPE (NullPointerException) because it's complaining about something that has worked for 5-6 years. I downgraded my Hub to 2.3.8. and checked. No NPE. Upgraded back to 2.3.9.196 and no NPE. It was a quick test and I could have overlooked something but it was easy enough to find before
Returning to v2.3.9 and the EZ Dash I had before is gone, I had to recreate it. Not unexpected.
Download the Hubitat app
