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

Wine cellar HWS77GDAU1 double zone temperature setting #238

Open
websy06 opened this issue Aug 22, 2024 · 2 comments
Open

Wine cellar HWS77GDAU1 double zone temperature setting #238

websy06 opened this issue Aug 22, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@websy06
Copy link

websy06 commented Aug 22, 2024

Describe the bug
A clear and concise description of what the bug is.

Hi,
Thanks a lot for your great job with Haier. May I report the following bug ?
I have a HWS77GDAU1 wine cellar with a double zone.
When you change the temperature/program (sparkling, red wine, whitewine, ...) on one of the zones, the other parameters reset to the default parameter on the other zone.

Expected behavior
A clear and concise description of what you expected to happen.
When you change the temperature/programe of one zone, the other one should not change and should keep the values already set.

Home Assistant
Core 2024.8.2
Supervisor 2024.08.0
Operating System 13.1
Frontend 20240809.0 ⸱ legacy
-hOn Integration Version: 0.14.0

@websy06 websy06 added the bug Something isn't working label Aug 22, 2024
@tomazzive
Copy link

I have the same issue. I tried to find a logic, but couldnt find any. I do notice that the temp setting of one zone is duplicated to the other zone. It can also be the setting of a program. Its both Z1 that is set to the temp of Z2 and the way around. I had this issue for two weeks. 5 times now. Not good for my wine

@tomazzive
Copy link

I think I found the logic: when i turn off the light with the hacs integration, bot zones were set to 5° (= bubbels program)
In fact I added a automation that turns the light on at sunset and turns it off at 22h. So thats why I had the issue since 2 weeks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants