Devices with `supportedThermostatModes` off and heat shouldn't have `thermostatCoolingSetpoint.coolingSetpoint`

[ldeora]

My thermostat radiator valves (former profile thermostat-heating-only) look like this now:

Devices with supportedThermostatModes off and heat shouldn't have thermostatCoolingSetpoint.coolingSetpoint, right?

Originally posted by @ldeora in #2084 (comment)

[ctowns]

Thank you for reporting this! Could you confirm for me real quick:

1. Can you confirm if your hub is using FW version 57+?
2. Can you confirm if the device is now using the thermostat-modular profile?
3. Was this device recently re-onboarded? Or did you perform a driver switch recently?
4. Has this device recently received a FW update for the device?

Thank you!

[ldeora]

Hub FW is 56.x

Profile of identical working device is thermostat-heating-only-nostate-nobattery, affected device profile is thermostat.

Re-onboarded today. Matter thermostat driver version: 2025-06-02T20:43

The device hasn't received an update. It's a Kasa KE100, connected via a Matter bridge (Tapo H110).

Anyway: as long as there's no cool in supportedThermostatModes, there shouldn't be any cooling capabilities.

I've read through the Matter thermostat driver a dozen times before the switch to modular profiles and I think I have PTSD now and I won't do that again any time soon.