You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When switching mode (t_work_mode) from off to heat, the setting "fan mute" (t_fan_mute) is reset back to off.
If I use the ConnectLife app, the value is retained.
Considering I'm only using the aircon units on fan mute constantly, this is slightly annoying for me as I turn on the aircon in HA, then have to wait until the integration updates the status, usually half a minute to a minute, and only then I can turn fan mute back on again.
If there's anything I can do to assist troubleshooting or testing this, please let me know.
The text was updated successfully, but these errors were encountered:
This seems similar to issues discussed in #195 where we need to send multiple fields in the same requests.
I guess that the integration in this case needs to send t_fan_mute with its current value in the same request as t_work_mode (at least if t_fan_mute is enabled).
Could you try to use the new Update device action/service to experiment sending both fields?
If it works, we need to figure out how to configure this in the mapping file(s).
Thank you for your investigation. I have been a bit indisposed the last couple of weeks, so I haven't had the time to think about how this can be leveraged into some kind of actions. Any ideas?
Minor annoyance rather than full on bug.
When switching mode (t_work_mode) from off to heat, the setting "fan mute" (t_fan_mute) is reset back to off.
If I use the ConnectLife app, the value is retained.
Considering I'm only using the aircon units on fan mute constantly, this is slightly annoying for me as I turn on the aircon in HA, then have to wait until the integration updates the status, usually half a minute to a minute, and only then I can turn fan mute back on again.
If there's anything I can do to assist troubleshooting or testing this, please let me know.
The text was updated successfully, but these errors were encountered: