Is it possible to add a 3 state enum to home assistant to control the bypass on zehnder q450 using the comfoconnect library. My goal is to automate the state of the bypass in the ventilation unit based on the internal room temperature (using a extrenal temperature sensor) To do this i need a sensor/control to send the required state from the automation platfrom to the comfoconnect library
The control or enum state should have 3 states: auto, open, close.
The commands in the comfoconnect library are:
bypass open: comfoconnect.cmd_rmi_request CMD_BYPASS_ON
bypass close: comfoconnect.cmd_rmi_request CMD_BYPASS_OFF
bypass auto: comfoconnect.cmd_rmi_request CMD_BYPASS_AUTO
Sending these command using the example provided by michealarnauts will set the bypass in the required state. Many thanks to him for creating these functions.
So the commands are already in the comfoconnect library, its just a matter of creating the right sensor/control on the home assistant side.
Comfoconnect library:
Home assistant integration:
I really hope that someone can help we with this, or point me in the right direction.
Many thanks,
Frank
Can anyone point me in the direction how to add these commands to home assistant?
Hi Frank,
I am also interested to control the bypass but also dont know how to do that.
Do you have a solution to execute these commands in home assistant?
Maybe you can help me. Thanks.
there is already a PR for controlling the bypass in the comfo unit:
See here:
home-assistant:dev
← dkossako:dev
opened 10:51AM - 16 Sep 21 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## 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.
-->
Updated pycomfoconnect library, with improved support of Zehnder ComfoAir. Added control of bypass.
## 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.
-->
- [x] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Example entry for `configuration.yaml`:
<!--
Supplying a configuration snippet, makes it easier for a maintainer to test
your PR. Furthermore, for new integrations, it gives an impression of how
the configuration would look like.
Note: Remove this section if this PR does not have an example entry.
-->
```yaml
# Example configuration.yaml
comfoconnect:
host: IP_ADDRESS
```
## 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: N/A
- This PR is related to issue: N/A
- Link to documentation pull request: N/A
## 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`)
- [ ] 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`.
- [ ] 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
<!--
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
I dont know when this will merged in HA.
2 Likes
Test123
(Will)
July 3, 2022, 9:04pm
5
Is there any news on this ?
I’ve spend some time in rewriting the integration and the underlying library to communicate with the Comfoconnect LAN C (it’s asyncio now).
This integration supports the following additional features over the existing integration:
Configurable through the UI.
Allows to modify the balance mode, bypass mode, temperature profile and ventilation mode.
Changes to fan speed won’t be reverted after 2 hours.
Support to clear alarms.
But since it’s a big change, it could use some testing before I can submit this to Home Assistant.
If you want, you can install the update trough HACS.
See GitHub - michaelarnauts/home-assistant-comfoconnect: Home Assistant integration for Zehnder ComfoAir trough a Zehnder ComfoConnect LAN C. for more information.
You can discuss this at the topic here: Zehnder ComfoConnect component - #82 by michaelarnauts
1 Like
Cool!, will check it out!
sumnerboy
(Ben Jones)
July 12, 2023, 11:08pm
8
Just installed and so far it is looking great. I just added a feature request to your repo to enable a switch for controlling boost mode - that is pretty much the main reason I wanted to integrate my ComfoAir Q450 with HA - to automatically boost when someone is in the shower :).
Thanks for providing this great integration!!
1 Like
Hi @sumnerboy , instead of activating boost mode you could set the fan speed to 100%. This is my automation for activating 100% fan speed when the humidity is too high:
alias: "VD2 | Als douche/bad aan: Dan ventilator aan"
description: ""
trigger:
- type: humidity
platform: device
device_id: X
entity_id: Y
domain: sensor
above: 70
for:
hours: 0
minutes: 0
seconds: 5
condition: []
action:
- service: fan.set_percentage
metadata: {}
data:
percentage: 100
target:
entity_id: fan.comfoairq
- service: fan.set_preset_mode
metadata: {}
data: {}
target:
entity_id: fan.comfoairq
mode: single
@michaelarnauts Thank you for making and sharing this updated home-assistant-comfoconnect
integration! On first glance it looks beautiful. If I have any feedback, I’ll share it with you. It’s great to be able to se the ComfoAir Q temperature profile using Home Assistant.
sumnerboy
(Ben Jones)
May 19, 2024, 8:19pm
11
Thanks @elidamaise . I already have an automation which looks very similar. I have added a delay and another action to put the ComfoAir Q back into ‘auto’ mode.
However I still think it would be cleaner if we could use the built-in “Boost” function of the unit, rather than trying to synthesize it in our automation. Removes the need for the delay and changing mode (which I found was necessary).
alias: "Climate: Boost MHRV when showering"
description: ""
trigger:
- platform: numeric_state
entity_id: sensor.bathroom_humidity
above: 70
condition: []
action:
- service: fan.set_preset_mode
metadata: {}
data:
preset_mode: manual
target:
entity_id: fan.comfoairq
- service: fan.set_percentage
metadata: {}
data:
percentage: 100
target:
entity_id: fan.comfoairq
- delay:
hours: 0
minutes: 15
seconds: 0
milliseconds: 0
- service: fan.set_preset_mode
metadata: {}
data:
preset_mode: auto
target:
entity_id: fan.comfoairq
mode: single
1 Like