-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
MiElHVAC Power Toggle and Power cmnd over MQTT won't work. #18923
Comments
Same issue when I upgraded from 12.4.0 to 13.0.0. Flashed back down to 12.4.0 and power commands are sent successfully. |
I don't have the device, not know how the driver works. But I don't see any significant change that would explain the bug. Do you know which version broke it? |
Here is what we know so far |
Try latest change in dev branch and report back. |
@arendst it looks like it works. I've tested the webui and mqtt, both will start and stop the airconditioner correct. Thank you for your help! |
No problem. Was my fault anyway ;-) |
Fix miel_hvac (arendst#18923)
PROBLEM DESCRIPTION
The air conditioner cannot be switched on via MQTT or the power toggle. The power cmnd is interpreted correctly according to the log, but the serial output to the air conditioner is not sent correctly.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Backlog Rule1; Rule2; Rule3
:Status 0
:weblog
to 4 and then, when you experience your issue, provide the output of the Console log:TO REPRODUCE
AC is set OFF
Send over MQTT power/on
OR
Toggle Switch in Webui
EXPECTED BEHAVIOUR
AC should start
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
In my opinion the Line
07:39:05.250 MiElHVAC: sending FC41013010 01010000000000000000000000000000 7c
isn't correct.
I think the 8th byte should be 0x01 instead of 0x00
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: