-
Notifications
You must be signed in to change notification settings - Fork 442
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
card_thermostat gives error when stepping temp up or down manually #1530
Comments
I'm also having this issue! |
I am also having this issue with the following error: Provided temperature -17.77777777777778 is not valid. Accepted range is 10 to 32. |
I've got the same issue after an update to 2024.8. Seems the issue is only with UI Minimalist. |
have the same issue |
Downgrading HA to 2024.7.4 fixed this issue for me |
Same for me, except it shows that 0.0 is not valid |
same here, it shows that 0.0 is not valid. |
Upgraded to 2024.8.3 and have same issue. |
Found a fix, this seems to be an issue with climate's service_data. My hvac does not support
Lines 228 to 248 in c4079cc
Lines 298 to 315 in c4079cc
By removing the above lines from
now am able to adjust temperature without an issue. |
@iganeshk Thank you for this. It's been driving me nuts for a while. For anyone else that comes across this post.... You can't update the card in the exact location listed above. You have to place the card into /config/ui_lovelace_minimalist/custom_cards/card_thermostat/card_thermostat.yaml, edit it here, and then reload Minimalist from Developer Tools -> YAML -> UI LoveLace Minimalist and it will ingest the custom card. |
Describe the bug
card_thermostat gives error when stepping temp up or down manually. First noticed after upgrade to HA 2024.8.1. Error message appears a bottom of screen. See screenshot for error message.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Temp should increase by defined step - or default of 1.
Screenshots
Additional context
I attempted to remove variable
ulm_card_thermostat_temp_step:
, as well as set it as 1 vs 1.0. Same result.The text was updated successfully, but these errors were encountered: