W200 temperature swing
The temperature swing (not deadband) is not adjustable and set to a 1 degree swing. With that, the thermostat will run until it is 1 degree above/below the set point. However, what is occurring with the HomeKit connection is that the target temperature is set to 74.3(example value), which also sets the cooling/heating threshold to the same…once the temp is below (if cooling) or above (if heating) the target has been exceeded so it then changes the “current heating cooling state” to off, but the system is actually still running until it meets the swing value (73.3 or lower). Any automation that uses that as a trigger will then fail to work correctly. No other thermostat (Honeywell, Sensi, Meross, Ecobee) I have used does this. The way all of those work, once it reaches the target temp, the system runs their set dissipation before setting the current heating cooling state to off. I am ok with it running that 1 degree difference but it should not change the current heating cooling state to off until the system actually turns off. I know there is a new firmware this last week, but I no longer have my thermostat installed waiting for this to be corrected. Can anyone tell me if the new firmware release has changed this?