Can't add Midea dishwasher MFD60S510Wi

[nikhomekgn]

Versions
Midea AC LAN 0.3.23
HA with latest updates

Description
Sorry for my bad English. I have Midea dishwasher MFD60S510Wi (static IP), when adding a device to HA it is automatically found, but when confirming I see a message in the form "The configuration is incorrect". If changing model to correct - same message.
Log in configuration.yaml enabled, but there's nothing in it.
If use Protocol V1 or V2 device is adding to HA, but all sensors are unavailable. Log attached below.
P.S. Integration update to alfa version available in HA, but it won't download.

[wuwentao]

Thank you for youre issue report, as most of us just take it and we may need time to check and fix it later.

[nikhomekgn]

Thanks for your work. If any information is needed on this issue, I will try to provide as much information as possible.

[nikhomekgn]

HA core version
2024.5.5

Integration version
v0.4.1

Device type and model
Dishwasher Midea MFD60S510Wi (latest firmware)

Used App
Midea SmartHome and Home Assistant

The description of problem
Upgrade integration to 0.4.1 and clear config in /.storage/midea_ac_lan
Try to connect:

Same if use "auto"

Use SmartHome account

In Midea SmartHome app I see a message "Account logged in somewhere else"
In /.storage folder midea_ac_lan is not created

In home-assistant.log is nothing about midea_ac_lan. Debug is enabled in configuration.yaml.

If I try to connect manually:

Maybe I do something wrong?

[wuwentao]

no debug log should be an issue....

you can remove this integration and reboot HA, remove all the /configs/.storage/mides_ac_lan/

then reinstall it, after install, please confirm you have enabled debug log for midea_ac_lan from /configs/configuration.yaml file.

enable command can be found in readm.md file

once debug log can works, you can attack the debug log file, then we can check the detail error

[nikhomekgn]

Reinstall integration, reboot HA
In configuration.yaml add

logger:
default: warning
  logs:
    custom_components.midea_ac_lan: debug
    midea_local: info

Log, that repeats every time I try to add a device
homeassistant.log

[nikhomekgn]

Remove integration. Install 0.4.2
Debug log:
homeassistant.log

[chemelli74]

Thx, I debugged the issue and login fails because of

{'msg': 'user route does not exist', 'code': 10004}

I think there is a change in MSSmartCloud change

[nikhomekgn]

Thanks for your feedback!
Is the problem on my side or do I need to wait for some changes in the code?

[ttrueten]

Hello,
Same problem here with a Midea SU 5.35X14CS.

I hope you can find a solution.
Best regards,
T.

[chemelli74]

I think I got it, probably we release a new version in a few days

[chemelli74]

Please check with v0.4.3 and if still experience the issue, add the following to configuration.yaml , restart HA, and post the log:

logger:
  default: warning
  logs:
    custom_components.midea_ac_lan: debug
    midealocal: debug

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.

[nikhomekgn]

Update to 0.4.3
homeassistant.log

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Update to 0.4.3
homeassistant.log

[chemelli74]

2024-07-03 08:56:14.649 DEBUG (MainThread) [midealocal.device] [153931628223465] Authentication failed

Please double check with SmartHome mobile app that you can login.

[nikhomekgn]

In SmartHome in that time (translated):
09:11
Account logged in somewhere else
Your account has been registered on another device in Other. If you do
not do this yourself, please sign out of this device by visiting Manage
Sign-In Devices.

[ttrueten]

Hi there,
thank you for your work, unfortunately no noticeable change. Log attached, username anonymized, login with the real data via the SmartHome app works.

HTH,
T.
homeass.log

[chemelli74]

Unfortunately I don't think we can do something if authorization fails.

[rokam]

@wuwentao and @chemelli74 I think this is a case that the 2nd key retrieval type might work. If this is true, midea-lan/midea-local#200 should solve it.

[rokam]

Can you please try v.0.5.0?

[ttrueten]

"Can't get available token for this device"
homeass.log

[nikhomekgn]

Install 0.5.0
"Can't get available token for this device"
homeassistant.log

[ttrueten]

Same behaviour: Can't get available token for this device

homeass.log

[chemelli74]

@nikhomekgn , @ttrueten which mobile app are you using to control your devices ?
We need exact name (and maybe a screenshot of the icon just to be sure ).

[nikhomekgn]

Screen from "About"

[wuwentao]

all the token can't work for these 0xE1 device.
the same error as 0xDB device

[nikhomekgn]

Is this solvable?
Maybe you need some additional information from me?

[ttrueten]

@nikhomekgn , @ttrueten which mobile app are you using to control your devices ? We need exact name (and maybe a screenshot of the icon just to be sure ).

[nikhomekgn]

I understand that update 0.5.3 does not solve our problem, but I'm attach the log just in case
homeassistant.log

[rokam]

0.5.4 should fix your issue

[nikhomekgn]

@rokam updating to 0.5.4 did not help
homeassistant.log

[wuwentao]

由于github当前存在大量同样duplicate的issue，因此先关闭当前issue，统一使用 #275 来跟踪和处理，避免大量重复问题的跟踪和处理。
当然，当前issue仍然可以继续更新和发送其他消息