Discovery fails - Connection cannot be made - "Code: 3004, Message: value is illegal" #322
Comments
|
Could you provide debug logs? It's probably related to mill1000/midea-msmart#193 |
|
ah yes, might be related. Thanks for tagging it. Here is the log output from msmart-ng discover |
|
Same here. Regardless of the Cloud region I pick I get that for a newly installed AC device. |
|
I have the same problem here, the auto discovery shows me the two ACs I have, and their correct IPs, but can't connect to them, regardless of the region chosen. I also tried to input the IP directly, but I get the same result Here's the Home Assistant log: And the msmart-ng logs: The logs with the mismatched IPs are weird, I looked in the DHCP bindings and 192.168.100.5 and .3 are used by a phone and a watch, .7 and .9 are the correct IPs of the ACs. I can control them in the app, so at least I know their wifi is working haha |
|
Just installed a new Midea Smart AC and was trying to set this up to have better connection compared to the matter connection and received the "A connection could not be made" error. |
|
I am having the exact same issues. This integration previously work for me, but I had to start a clean installation of HA. This is in my logs but I never entered any login information. This error originated from a custom integration. Logger: msmart.discover Failed to login to cloud. Error: Code: 3144, Message: login failed, login ID is empty, please login again. |
|
I have the same problem, both of them can no longer be connected no matter what I do, I have already set up hay but it still doesn't work, one of the two was even added before but I accidentally removed it now I can't add it anymore
|
|
Bump! I have the exact same issue. Tried several time, tried to restore backup. Not connecting anymore, no matter the server. |
|
It used to work for me but I had stupidly removed the device, now I can no longer add the device, even new devices can no longer be connected |
|
Hi all, I'm getting the same issue. The first device sets up fine and then any additional devices fail |
|
hey @mill1000, have any clue what might be causing this? |
|
Same for me. Even changing regions in my account doesn't help. I have 4 units, recently one of the devices stopped working, so new one had to be installed. 3 are working properly, and unable to adopt the new one. |
|
Sorry I'm on a trip with limited access to internet. Most likely Midea changed their API, or has cracked down on its usage outside of their app. Once I return I'll look into the API again and see if anything can be done. Users who already have their token & key should be able to manually add their devices. If you previously added the device to HA, it's possible the token & key could be found in an HA backup if you have one. |
|
@mill1000 Unfortunately no, there is an error that the token is not known it was the case that you could no longer operate the devices even though they were online, so you usually remove the device and simply add it again, but you can't add any devices at the moment |
|
When using tokens, the errors occur (Unknown error occurred)( A connection could not be established with these settings. )
|
You'll have to provide full debugs then because no cloud access is required if you already have a key and token. |
I know that, I had already added the devices with tokens, but now it doesn't work anymore, the devices can no longer be addressed |
|
Ok, please provide full debug logs after rebooting HA so I can help. |
|
I have yet to dig in too far, but I likewise have lost HA access to my units. (Existing configs, manually added from key and token!) |
|
Thanks. The only midea_ac error in this log is the following. Which implies you've entered the token incorrectly. I should improve the reported error in this situation. |
|
Just for the sake of measuring the impact, the same happened for me. For 2 days I can't access my AC through HA anymore. But it works just fine through the SmartHome app |
I only have one token and it didn't work the last time but now all of a sudden The problem is not really the token but that I can no longer connect 4 devices |
|
I have the same problem, can't connect my midea AC anymore. Worked a year ago with a silent cool 26 pro wf, IP is correct and ID is correct. |
Self-update - mine may not be related after all, could be the connection time issue, or may not. I was able to re-add the devices and have them talk again. HOWEVER! |
|
@mill1000, I finally managed to get the logs when trying to add my two AC's (one was connected successfully before): Looks like some authentication in the back-end to the cloud environment failing. I assume it uses the credential from the MIdea app? |
|
I seem to be having the same issue as well. Removed one of my ACs due to IP address change and unable to add it back. At first I tried to add it then tried it again at it said adding was already in progress. After a few minutes I restarted HA and now I have the |
|
always comes to me ( Code: 3004, Message: value is illegal. ) 2025-03-10 09:06:13.267 ERROR (MainThread) [msmart.discover] Code: 3004, Message: value is illegal.
|
|
I have tried the last four versions. They all five the same error |
|
Just released 2025.3.0 which includes the fix for this. |
|
Midea Smart AC hi i still get this error even with the new update. will try get the logs |
|
"Cloud connection could not be made" :( |
|
|
i dont see any other errors in the logs juat this one |
|
i do see this in the debug logs so it does make a connection 2025-03-21 23:49:57.485 DEBUG (MainThread) [custom_components.midea_ac.coordinator] Finished fetching midea_ac data in 0.661 seconds (success: True) |
|
Worked just fine for me. You should restart the services to work.
|
|
Works perfectly now! Thanks again @mill1000 |
|
@dustin-auby |
|
I had also problems to add my new Midea PortaSplit. I had to create a NetHome Plus Account (SmartHome dosn't work) and use the "midea beautiful air cli" in the terminal to get the token and the key to configure the AC manual.
hope that helps |
|
Works perfectly now! Thank you so much for the effort you put in to get this to work again @mill1000 |
|
Sorry you're still having trouble. Did you try the region option as others suggested? I've found the EU area to be picky. |
Hi yes i have tried all 3 regions and it shows the same error. i have also restarted home assistant |
|
Region switch to US did the trick for me too, yay. But when I try to configure the air conditioner, I get a 500 Internal Server Error. To be honest, I have no idea whether it’s due to my setup or the integration—I would assume the former. |
|
Have you tried to restart your router? Update home assistant.
Em sáb., 22 de mar. de 2025, 16:36, NatyaSadella ***@***.***>
escreveu:
… Region switch to US did the trick for me too, yay.
But when I try to configure the air conditioner, I get a 500 Internal
Server Error. To be honest, I have no idea whether it’s due to my setup or
the integration—I would assume the former.
—
Reply to this email directly, view it on GitHub
<#322 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOYC63XSRFJN6VIME7JQJ32VW3UDAVCNFSM6AAAAABYLHFET2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBVGQZDSNRVHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
[image: NatyaSadella]*NatyaSadella* left a comment
(mill1000/midea-ac-py#322)
<#322 (comment)>
Region switch to US did the trick for me too, yay.
But when I try to configure the air conditioner, I get a 500 Internal
Server Error. To be honest, I have no idea whether it’s due to my setup or
the integration—I would assume the former.
—
Reply to this email directly, view it on GitHub
<#322 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOYC63XSRFJN6VIME7JQJ32VW3UDAVCNFSM6AAAAABYLHFET2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBVGQZDSNRVHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Yup I did multiple restarts on every device and everything is up to date. The translated error is: The configuration flow could not be loaded: 500 Internal Server Error - Server got itself in trouble. |
Yeah that doesn't sound like an issue from this integration. Unless of course the debug logs are showing lots of errors from midea :) |
|
@dustin-auby Can you enable debug logging and post them here after trying to add a device? Or can you run the |
Ok I can do that , will revert once I have the logs |
Ok so tried to test it again and this time it did work. not sure what changed. one thing that did happen is there was a trip on the db for the office and the AC lost power. the Home assistant was not affected though only the AC lost power |
|
Same issue here with the connection failure. Waited for these last two updates, still no good.
HA log: |
|
You don't appear to be using the latest version based on your screenshot. The error "a connection could not be made" was replaced with "device connection could not be made" or "cloud connection could not be made". |
|
I had to restart HA! I did several updates and thought I had restarted. It failed configuration several times after restarting, then eventually started working after a couple minutes. Now all seems perfect! By the way, I saw this comment: Let me say, I bought this brand specifically because of this integration which others have had success with, and I am immensely appreciative of your effort here. I recognize you do it for free and thank you so much! |
I don't know if this info is helpful but it looked like it was indeed an issue with the integration. Logs told me "AttributeError: MideaOptionFlow object has no attribute config_entry" I had to edit the config_flow.py file, now I can configure the AC |
|
What was the edit you made? And what version of HA are you running? |
This was the solution:
But I run HA in a docker on a RPI5 and I didn't knew I had to update HA core manually. I was on a older 2023 version so maybe updating to the latest core version would have fixed this too I guess. |
|
Yes the older HA release was likely the problem in this case |
and others
Has anyone experienced this issue:
Running on the 2.4Ghz network, adding Midea AC - it picks up the devices (shown in list after auto discovery) with correct ID and IP address. Once it goes to the next step, it pauses for 10 seconds and then comes back with error "A connection could not be made" (see screenshot).
Even manually adding does not work with same error.
I already have one Midea AC running on the same setup and works perfectly (added a couple of months ago), but new devices (exact same model) seems to have issues in being added.
The text was updated successfully, but these errors were encountered: