I’ve got exactly the same issue. I can add the devices, but as soon as I try to access the device or anything else, it cannot initialize the device. I tried to login again, but without result.
Edit: I wasn’t able to initialize the devices using the homey app on my phone. But when using the website/browser on my laptop, I was able to add the devices immediately. After that it seems to work on my mobile app too.
i solve mine. Delete every accont in msmarthome e create e new… pufff work perfecte.
I did follow your solution @Nuno_Alves but with 2 units from the 4 I still get this error:
I do get a message in the Smarthome app that my account has been used on a different device, but I can’t add two of the four devices. I removed all data from the Smarthome app. I did use the web browser to log in, but all the results were the same and I always get the error as shown above.
Anybody any idea?
Exactly the same, have been trial and erroring for hours trying to figure this out.
my dongle is an osk103,
but everything worked before upgrading from nethomeplus
Hi @mteutelink,
is it possible for you to add die Midea Porta Split airconditioner?
It is not found when adding a new device.
Thanks
Michael
I have created a test version of the Midea app. Please remove devices and try adding again. Then create a diagnostic report. This version gives me more debug logging and more logging during the discovery proces, which I need to investigate.
The test version is here:
I have done some investigations with my own airco devices. They doe not show up when not being added in the MSMartHome (iOS/Android) app. Please add them first in the MSmartHome app and then add them in de Homey app. Use the test version and create a diagnostic report, so I can investigate in the debug logs any further.
Okay, I succedded!
My PortaSplit used a different WLAN. After i changed it, it was found immidiately!
Thanks for your app!
Hi @mteutelink
I have a timeout problem that’s stopping me now. First I had to change to MSmartHome app, as I was using NetHomePlus. No problem, all my 3 AC units were added correctly and work. Thet I go to my Homey Pro 2023, add your Midea app, it finds the 3 AC devices, and when adding the first one I try to login but always get a “Timeout after 30000 ms”.
The MSmartHome sends a notification that a session has been started in another device (shown as some chinese name), and I have double checked user/login in the MSmartHome app and it works.
I have installed the test version and sent a diagnostincs report: ea92046b-66af-49ea-a582-16635aa2fee9
Thanks,
-Fran
I have exactly the same error.
Kaisai Pro Plus
I have encountered the same problem over and over. I added the airco to the app in which everything works fine. But can’t seem to connect them to homey. Homey finds all three but I get the same message as AlexaH. Diagnostic rapport code: f0f6a1c8-0d5d-4d2b-9128-c66b333f55e2. Are you able to look into this? Thx!!
For me the test version sadly didn’t work. I added my Midea ACs to the MSmartHome app. But login was still not possible. So I downloaded the code and created a rough proof of concept version where instead of entering a username password, I refactored the login screen to add the needed token/key combination manually. Because I could not get the token/key combination from MSmartHome, I did the following:
Both ACs are working perfectly in homey using the proof of concept code.
If there is any interest in a token/key version of the app, it would be a nice feature to let the user decide if they want to use the login method or the token/key method.
I am struggling with the fact that I can’t test and debug the ACs that have problems. I will check this out and incorporate the code in my app.
Thanks
If you need the POC code, just let me know. As said, it’s rough and was only intended for me to test the token/key option.
Yes, please. I will test it against my ACs and will put it in the code. I am working on more features, bur this needs to be fixed first
It is working with token and key internally, but i want to know what the problem is. This helps hopefully
A new test version (1.0.13) has been released. In this version logging in into the cloud is not necessary anymore if token and key are known. It remains possible by leaving the field token and key and empty and press continue to enter the login screen. this should not only speed up the inner working, but hopefully gets rid of the timeout during pairing.
Please test and let me know.
Sieto, I checked your code and based on that I made adjustments to my code that eventually resulted in version 1.0.13. I can’t test myself if this also works for your ACs. Could you check this version to see if it works for you?
It’s working perfectly at the moment. I thought it didn’t but I messed up the key and token 
