Skip to content
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

Temperature Control issue #714

Open
feradelectronics opened this issue Oct 8, 2024 · 2 comments
Open

Temperature Control issue #714

feradelectronics opened this issue Oct 8, 2024 · 2 comments

Comments

@feradelectronics
Copy link

Problem/Motivation

When I try to change temperatures on my thermostat i get the following out of range error.

Expected behavior

I am using Celsius for temperatures but looks like it is expecting Fahrenheit.

Actual behavior

Seems to expect set temperature in a Fahrenheit value which is too high for Celsius conversion

Steps to reproduce

z-wave device add temp card on lovelace page and try to increment or decrement change set value in Celsius. See home-assistant/core#123612

Proposed changes

Distinguish and convert min max values between Celsius and Fahrenheit temperature values. Limits may need to be adjusted for different applications.

Copy link

github-actions bot commented Nov 7, 2024

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Nov 7, 2024
@nconder
Copy link

nconder commented Nov 12, 2024

Same issue but my temperature units are reversed. I am using Fahrenheit for temperatures but looks like it is expecting Celsius.

@github-actions github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants