Hi to everybody.
With the 2022.9 update I get 5 warnings (one for each of my HVAC controller thermostat) and could not use them anymore.
The thermostat are all the same, just the name of topics is different, and I think the problem is the “hold” mode which my thermostat uses to understand if using internal scheduler or manual mode.
Hereafter are the configuration lines inside the configuration.yaml
climate:
- name: Corridoio
unique_id: 1gf43d
availability_topic: "corridoio/tele/LWT"
payload_available: "Online"
payload_not_available: "Offline"
action_topic: "corridoio/stat/things/thermostat/properties/action"
action_template: "{{value}}"
temperature_command_topic: "corridoio/cmnd/things/thermostat/properties/targetTemperature"
temperature_state_topic: "corridoio/stat/things/thermostat/properties/targetTemperature"
temperature_state_template: "{{value}}"
current_temperature_topic: "corridoio/stat/things/thermostat/properties/temperature"
current_temperature_template: "{{value}}"
mode_command_topic: "corridoio/cmnd/things/thermostat/properties/mode"
mode_state_topic: "corridoio/stat/things/thermostat/properties/systemMode"
mode_state_template: "{{value}}"
fan_mode_command_topic: "corridoio/cmnd/things/thermostat/properties/fanMode"
fan_mode_state_topic: "corridoio/stat/things/thermostat/properties/fanMode"
fan_mode_state_template: "{{value}}"
hold_command_topic: "corridoio/cmnd/things/thermostat/properties/holdState"
hold_state_topic: "corridoio/stat/things/thermostat/properties/holdState"
hold_state_template: "{{value}}"
hold_modes: [ "scheduler", "manual","eco" ]
payload_on: "ON"
payload_off: "OFF"
modes: [ "heat", "cool", "fan_only", "off" ]
min_temp: 10
max_temp: 35
temp_step: 1
precision: 0.5
Any help or suggestion will be VERY appreciated.
tmjpugh
(Tmjpugh)
September 9, 2022, 1:59pm
2
Breaking Change for MQTT
Hold and away are replaced with preset_mode
home-assistant:dev
← jbouwh:mqtt-climate-preset_modes
opened 09:50AM - 08 Feb 22 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
`hold` and `away` mode config settings will be deprecated and removed with release 2022.9. This will break existing integrations that make use of these config settings. Integrations should use the new `preset_mode` configuration options.
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
This PR simplifies the use of `preset_modes` with the MQTT climate platform.
This is a follow up on https://developers.home-assistant.io/blog/2019/07/03/climate-cleanup/.
It will introduce a `preset_mode_command_topic`, `preset_mode_command_template`, `preset_mode_state_topic` and `preset_mode_value_template` to replace the current hold and away mode settings.
The following configuration settings will be deprecated:
- `away_mode_command_topic`
- `away_mode_state_topic`
- `away_mode_state_template`
- `hold_mode_command_topic`
- `hold_mode_command_template`
- `hold_mode_state_topic`
- `hold_mode_state_template`
- `hold_mode_state_template`
- `hold_modes`
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [x] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/21547
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [x] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
@tmjpugh
Thanks for your reply.
Do I just have to substitute the word “hold” with the word “preset_mode” in my config.yaml for it to work?
I will translate
hold_command_topic: "corridoio/cmnd/things/thermostat/properties/holdState"
hold_state_topic: "corridoio/stat/things/thermostat/properties/holdState"
hold_state_template: "{{value}}"
hold_modes: [ "scheduler", "manual","eco" ]
into this:
preset_mode_command_topic: "salotto/cmnd/things/thermostat/properties/holdState"
preset_mode_state_topic: "salotto/stat/things/thermostat/properties/holdState"
preset_mode_command_template: "{{value}}"
preset_mode_value_template: [ "scheduler", "manual","eco" ]
What about the current hold_modes: [ "scheduler", "manual", "eco"]
?
They should be the possible values for the dropdown list of modes, is it the preset_mode_value_template assumption I made correct?
Thanks again for your help
looks like that should just be:
preset_modes:
1 Like
Thanks, with last addition of preset.modes
instead of preset_mode_value_template
everything went back on track!