Not able to add a Front Load Washer

[renatothome]

HA core version

2024.10.4

Current integration version

0.6.5

Last known working integration version

0.6.5

Device type and model

Front Load Washer 150633093905063

Working mobile app

SmartHome

The detail description of bug/problem

1. description the device type and name（you may have multiple devices）

Error when adding new device. Front Load Whasher

150633093905063

The logs

2024-10-30 15:16:25.883 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] user input login matched
2024-10-30 15:16:26.587 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] Using account [email protected] login to SmartHome cloud pass
2024-10-30 15:16:28.883 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] connect device using method 1 token/key failed
2024-10-30 15:16:29.043 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] connect device using method 2 token/key failed
2024-10-30 15:16:29.044 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] Unable to connect device with all the token/key
2024-10-30 15:16:29.045 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] Can't get valid token with input account in SmartHome server
2024-10-30 15:16:29.714 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] Using account [email protected] login to SmartHome cloud pass
2024-10-30 15:16:30.288 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] connect device using method 1 token/key failed
2024-10-30 15:16:30.443 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] connect device using method 2 token/key failed
2024-10-30 15:16:30.443 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] Unable to connect device with all the token/key
2024-10-30 15:16:30.444 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] Can't get any available token with device 150633093905063
...

[wuwentao]

you don't provide the full debug log, but from the part log, it should be the same issue as #275
there is still no any new progress with this fix or solution.

as we will use #275 issue to track all these related issue, so I will close this issue, sorry.
once we have solution with it in future, we will update you with this closed issue or new issue in #275.
as this issue will be connected with our exist #275 issue.