Dishwasher can't be started anymore #125
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe the bug
My dishwasher can't be started from the Homeassistant integration anymore.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Dishwasher starts with selected program
Screenshots
https://github.com/Andre0512/hon/assets/19236891/3ba92f89-e214-4ec8-948a-a3ec0707770a
Environment (please complete the following information):
2023.11.0
0.10.0
0.15.8
Home Assistant Logs
Device Log
Data Archive

I am seeing the same behaviour with my washing machine, HWB 410AMC/1-80
I Can set the program etc in HA and the Time remaining, and Current Program are all correct i just cant start the process.
Same issue with my tumble dryer, when i press the start button i will see the error : can't send command
Same issue with my Tumble Dryer (HD90-A2959S firmware 5.1.5) - if I reload the integration and do not change any settings it will start but changing the program first results in the same error.
My Haier washing machine on the same account continues to work as expected. (HW90-B14959S8U1 firmware 4.1.0)
Please let me know if I can help at all - happy to provide any logs/config or wotnot if it helps track down the issue.
Same issue for me uising Wash machine HWE 49AMBS/1-S with Firmware: 5.14.0 and tumble dryer HLE H8A2TE-S. I can see status choose progrma etc but when iI want to launch I've message
Failed to call service switch/turn_on. Can't send command
Hi all, I updated to the beta release (v0.10.1-beta.1) via HACS, reloaded the integration, restarted home assistant (possibly not in that order) and mine started working again if that helps anyone else. Bennie
This worked for me, i've downloaded the v 0.10.1-beta1) via hacs ,restarted home assistant and it start work! thank you
I have updated also and all seems to be working now.
Hi, sorry for the delay. The problem should be the same as #117 and should be fixed with the latest beta. I have now published it as a normal release, check it out 🙂