-
Notifications
You must be signed in to change notification settings - Fork 17
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
Feature(CD): Heat Pump Water Heater RSJRAC01 wrong temperature #347
Comments
Hi @Punisher01, please enable debug for Midea AC LAN integration, wait for this error, disable debug and attach the log. Note: it is better to drag the log into the comment (which will add it as an attachment) and not copy paste as it is hard to read logs in GitHub. Thanks |
home-assistant_midea_ac_lan_2024-10-08T06-46-15.589Z.log I also saw continuous on/off. The connection to the wifi should be OK because it's only 1 room away from the heater. |
As first step please disable "custom_components/hon" as it generate a ton of "Detected blocking call...." |
Seems all good from log, maybe you are referring to F instead of C ? |
No. It's Celsius. I raised this issue on older version also. Someone found a solution: georgezhao2010/midea_ac_lan#404 (comment) Maybe this helps |
@Punisher01 could you help to share your device SN for us? then we can confirm the finally solution with your device type. the error should be your device msg not match current code, we should add new type or new msg for your device to fix it. |
seems both mode should works for different device submodule. |
Hello, I'm having the same issue, Temperatures aren't showing correct values... Was there a fix? |
HA core version
2024.10
Current integration version
v0.6.1
Last known working integration version
Device type and model
RSJRAC01
Working mobile app
SmartHome
The description of problem
The temperatures values are wrong: 10 degrees instead of 50 and also the current temperature is wrong. This problem persists from old unmaintained version.
The logs
config_entry-midea_ac_lan-30c54274be3917a9b39bb6660eb613b1.json
The text was updated successfully, but these errors were encountered: