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

Z-Wave climate entities use an incorrect default min and max temperature value for HW heating thermostats #135439

Open
Nick-Sills opened this issue Jan 12, 2025 · 4 comments

Comments

@Nick-Sills
Copy link

Nick-Sills commented Jan 12, 2025

The problem

Z-Wave devices that support up to Thermostat Setpoint CC V2 do not provide a maximum and minimum setpoint temperature range. This results in the use of default values in Home Assistant.

An upper limit of 50 degrees Celsius, which validates against valid input, was introduced here: #118649

This change breaks hot water heating thermostats, such as the Qubino ZMNHID, rendering them unable to adjust the setpoint temperature above 50 degrees Celsius. This also affects other thermostats.

I am in 100% agreement with the premise of this discussion that defaults should be user-configurable: home-assistant/architecture#1152

However, an effective and simple workaround would be to increase the default maximum temperature to 100 degrees Celsius. This adjustment should allow all thermostats supporting Setpoint CC V2 to operate within an effective range.

What version of Home Assistant Core has the issue?

2024.12.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Z-Wave

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

#118649
home-assistant/architecture#1152
zwave-js/node-zwave-js#7472

@Nick-Sills
Copy link
Author

PR here:
#135442

@home-assistant
Copy link

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zwave_js can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign zwave_js Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


zwave_js documentation
zwave_js source
(message by IssueLinks)

@alex3305
Copy link
Contributor

Duplicate of #123612.

However I would suggest to increase the limit to 100 degrees C which is the temperature of boiling water at sea level. Other limits seem pretty trivial to me. Because what would happen if someone owns a water heater that goes to 85? Do we get another issue and another PR again?

A boiling water limit would probably cover 99.99999% of the actual real world use cases.

@Nick-Sills
Copy link
Author

Duplicate of #123612.

However I would suggest to increase the limit to 100 degrees C which is the temperature of boiling water at sea level. Other limits seem pretty trivial to me. Because what would happen if someone owns a water heater that goes to 85? Do we get another issue and another PR again?

A boiling water limit would probably cover 99.99999% of the actual real world use cases.

Fair enough, updated to100 degrees C.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants