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

Fix failing climate.turn_on issue introduced in version 1.5.0-beta6 #1323

Merged
merged 1 commit into from
Mar 24, 2024

Conversation

LeoCal
Copy link
Contributor

@LeoCal LeoCal commented Mar 22, 2024

The commit b53b564 that went into BT version 1.5.0-beta6 introduced an issue causing the climate.turn_on operation to consistently fail.

The problem is due to the fact that HVACMode.HEATING is used in the call of self.async_set_hvac_mode() inside async_turn_on() function instead of HVACMode.HEAT.

Motivation: climate.turn_on operation called on BT fails because of a recent commit (b53b564) to 1.5.0-beta6.

Changes: HVACMode.HEAT is now used in the call of self.async_set_hvac_mode() inside async_turn_on() function, instead of the wrong HVACMode.HEATING.

Related issue (check one): #1295

  • fixes #
  • there is no related issue ticket

Checklist (check one):

  • I did not change any code (e.g. documentation changes)
  • The code change is tested and works locally.

Test-Hardware list (for code changes)

HA Version: 2024.3.2
Zigbee2MQTT Version: 1.36.0
TRV Hardware: Aqara Smart radiator thermostat E1

New device mappings

  • I avoided any changes to other device mappings
  • There are no changes in climate.py

The commit b53b564 that went into BT version 1.5.0-beta6 introduced an issue causing the climate.turn_on operation to consistently fail.

The problem is due to the fact that HVACMode.HEATING is used in the call of self.async_set_hvac_mode() inside async_turn_on() function instead of HVACMode.HEATING().
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

Successfully merging this pull request may close these issues.

2 participants