-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Comments
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 |
I think I found the logic: when i turn off the light with the hacs integration, bot zones were set to 5° (= bubbels program) |
Discovered this weird issue today too with an HWS42GDAU1 In addition the current temperature reported are wrong, equal to |
Otherwise the settings command will retain the default value instead of the real ones in attributes Fixes Andre0512/hon#238
Otherwise the settings command will retain the default value instead of the real ones in attributes. Fixes Andre0512/hon#238
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
The text was updated successfully, but these errors were encountered: