[APP][Pro] Midea - Midea HVAC Solutions - Smart climate controls

Apps
, ,
104

Thanks the idea, I also installed the NetHome Plus, registered the AC there, after added in Homey - after I filled out the username and password, I got the key+token (automaticly), and on the end SUCCESS. :slight_smile:

105

This is my diagnostic code: e7076107-feda-48bb-86c5-fd12dfcc8bb0

I am trying to add a Midea MAP10HS1WBL. But it only says “Error while adding device”. Any more ideas? I would be happy to diagnose if I could see the log file.

I used the NetHome Plus app. It filled in my credentials automatically, it just errors at the last stage.

In the console, it says this: Connectivities: [‘lan’]

It tried it with both the default creds and my own credentials from NetHome Plus.

106

Hi Marc,

I have a Midea Cube dehumidifier that I would like to add to your Midea HVAC Solutions – Smart Climate Controls app.

Device details:

  • Model: Midea MAD20S1QWT

  • Device type in Midea SmartHome app: Dehumidifier

  • SN: available if needed

  • Plugin Version: 2.2.2604242

My setup:

  • Homey Pro 2026

  • Firmware: 13.4.0

  • Midea HVAC Solutions – Smart Climate Controls app: v1.0.18

The dehumidifier is fully functional in the Midea SmartHome app. I can read status and change settings without any issues.

When I try to add a device through your Homey app, the pairing process immediately only offers “Air Conditioner”. It does not discover or offer a dehumidifier device type.

Would it be possible to add support for Midea dehumidifiers, or is there any additional information you need from me to help with adding support?

Here is how the SmartHome shows the dehumidifier

IMG_5737
IMG_57371206×2622 109 KB

And here is what is shown when trying to add a device in the homey app.

IMG_5736.PNG
IMG_5736.PNG1206×2622 81.5 KB

Thanks for your work on the app!

107

Hello, this app previously worked for me back in January when I first set up my Homey 2026. However I am trying to re-add my Midea A/C. And it errors out adding the device.

I have added the device successfully to Midea App, NetHome Plus, and the migrated mSmartHome. But unable to add to Homey as none of them connect after it pulls token/key.

image
image553×177 3.95 KB

I am also using the python script to gather token info, which only seems to return data when in Midea/NetHome ecosystem. However there is now Token/Key data in the results.

image
image284×190 2.59 KB

Is there a way to pull the token data from mSmartHome app? I just get an error when trying to use the --app msmarthome argument.

108

I have problems adding my Midea Porta Split to Homey Pro 2026.

It can not be found while I try to add it as a new device.

The PortaSplit is already added to the MSmartHome app and can be controlled there without any problems.

I have verified that the issue is not network connectivity:

  • Homey Pro and the PortaSplit are on the same local network.

  • The PortaSplit has a reserved DHCP address.

  • I can successfully discover and communicate with the unit locally using msmart-ng.

  • The unit responds on TCP port 6444.

  • Local authentication succeeds and the device state/capabilities can be read successfully.

  • The local query shows that the unit is online and controllable.

In the Homey Midea pairing flow, I do not see any fields to enter the IP address, device ID, token, or key manually. I can only run the automatic discovery, which finds no devices.

Could you please advise:

  1. Is the Midea PortaSplit supported by the current Homey Midea app?

  2. Is there a manual pairing method for devices that are reachable locally but not detected by Homey discovery?

  3. Is there a beta/test version with manual IP / device ID / token / key entry?

  4. Would a diagnostics report help, and if so, where should I submit the report ID?

Thank you for your help.

109

I tried PR#19 as well, thank you for all the hard work, however it did not resolve my issue.

After some research it seems my problem is that I have older V2 wifi dongles for the 3 Midea AC units that were not recognized by the app which do not need token and key on the LAN. The newest one that worked initially returned both when checked via msmart-ng.

So I made some changes to the drivers.ts which helped with the discovery, however when I tried controlling them I was still getting errors so I also had to update the LanConnection.js to handle messages with no token and key.

I have not tried creating a NetHome-Plus account.