Conversation
|
Hi @switschel, It seems you haven't yet signed a CLA. Please do so here. Once you do that we will be able to review and accept this pull request. Thanks! |
|
Hey there @michaelarnauts, mind taking a look at this pull request as it has been labeled with an integration ( |
|
@switschel You are right that the current behaviour is confusing, however, I think that the right way to fix this, is to implement When the preset mode is manual, there is no timeout and a speed change doesn't fallback. When the preset mode is auto, you can change the speed, but it will fall back after 2 hours. |
|
I've did this change in #55652. @switschel you might want to try out that branch. |
|
Hi @michaelarnauts , Otherwise turning on and off the fan will result in strange behaviors like it is now. E.g. if you set it off, it will go again on after 2 hours which is only desired when you keep the preset_mode manually on Auto. |
Hmm, I don't follow. In case the preset is manual and the speed is off, it will stay off (off=away), when you change the speed to low, you want it to stay like that. If you automatically switch to auto then, depending on the configuration of the ventilation, it will move to normal after two hours, and since you've put the preset in manual before, this is not what you want. Turning on and off is consistent now, when in manual, it will stay like it is, when in auto, it will fallback after a hours to the default mode (decided by the schedule and sensors of the device). |
|
It's a usability thing. As a "normal" HA User you just go to your Dashboard and turn off/on the fan via the toggle switch (basically you don't change the preset mode in that case). With the current implementation you have to do two things: Preset Mode to manual and fan off (persistent away mode as no schedule can be provided) and vice versa preset mode to auto and turn on. I don't like this line (177-178): And also here the preset mode should be changed not only the set_percentage: |
|
Your usability remark also happens in the mobile app then. When in auto mode, and you switch the fan speed, it will revert back. This even happens when you use the remote of the unit and switches to a different fan speed. If you want to use manual control, the preset mode should be on manual, otherwise, the fan will always revert back to the schedule after two hours. In your use-case, you'll want to have the preset mode to manual, and then it will behave as you describe. Note that even in manual mode, you can still configure the sensors to override this and increase the fan speed when high humidity is detected. You can configure this in the app. The whole purpose of auto mode and manual mode is enable this fallback or not, we should not switch this mode when changing the fan speed. It defeats the purpose. Regarding this if statement: I guess it has been added when the change from distinct speeds to percentages has been done in the whole codebase. I'm not sure when we don't get a percentage actually. I just left it there to be sure. |
|
See #55652 |
|
I agree with you according to change of fan speed. No change in preset modes here needed.
As written, it will be executed when you use the toggle button "on" in the Dashboard which might be used by the most users. |
|
I'll take a look at it further, since it's described here that
(https://developers.home-assistant.io/docs/core/entity/fan#preset-modes) |


Proposed change
comfoconnect module currently set fan speed mode temporary for 2 hrs by default. Afterwards the unit will switch back to auto.
Also it was not possible to to switch back to auto which is the most desired mode.
For example if you turn off the unit it will go to away mode for a specific time only. If you turn it on it will go to fan speed "low" for a specific time (which is not the desired state in most cases).
In this pull request I did two things:
Type of change
Additional information
-Feature request: https://community.home-assistant.io/t/add-auto-manual-mode-switch-for-comfoconnect/143437
Checklist
black --fast homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all..coveragerc.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: