This is likely a problem with your thermostat driver. If it's a community driver, the developer may need to fix this. If it's a built-in driver, they should have all been updated recently, but a"Configure" or just "Save Device" to get these attributes updated if they were not consistent with the expectations originally may help. Alternatively, you can try these steps yourself:
Substitute appropriate values for both if needed, depending on actual capabilities.