meross-homeassistant: Merros IOT Cloud Fails to load on 2025.3.0

Describe the bug Merros IOT Cloud Fails to load on 2025.3.0

Your environment HomeAssistant version: 2025.3.0 Hassio Version (if applicable): Latest Hardware environment: HA Greene Logs taken when the issue happened

Logger: homeassistant.setup
Source: setup.py:275
First occurred: 6:46:58 PM (1 occurrences)
Last logged: 6:46:58 PM

Setup failed for custom integration 'meross_cloud': Requirements for meross_cloud not found: ['meross_iot==0.4.7.3'].

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 69
  • Comments: 132 (4 by maintainers)

Commits related to this issue

Most upvoted comments

cc https://github.com/albertogeniola/meross-homeassistant/issues/541, https://github.com/albertogeniola/meross-homeassistant/issues/539

This is indeed a problem of dependency resolution on paho-mqtt referened in meross-iot. It already exists a PR updating it to 2.x https://github.com/albertogeniola/MerossIot/pull/413 .

So, if you want a hotfix, waiting new releases, you can edit manifest.json and replace this line:

  "requirements": ["meross_iot==0.4.7.3"],

with

  "requirements": ["git+https://github.com/mmatuska/MerossIot.git@paho-mqtt-2.x"],

@roberttco Your not dumb it is not obvious to anyone not technical.

My first comment would be to go into Settings / Add-Ons and go into the add-ons store and get “studio code server”

https://github.com/hassio-addons/addon-vscode

That add-on will allow you to edit any file on your Home Assistant.

Once that add-on is installed you can navigate to /config/custom_components/merros_cloud folder. In that folder if you click on the manifest.json file.

In that file you will find a line that says…

"requirements": ["meross_iot==0.4.7.3"],

You need to replace that file with …

"requirements": ["git+https://github.com/mmatuska/MerossIot.git@paho-mqtt-2.x"],

Then restart you home assistant and all should work.

+1

Also, the workaround mentioned above worked for me too.

Although, I can propose one edit regarding security.

"requirements": ["git+https://github.com/mmatuska/MerossIot.git@paho-mqtt-2.x"] - This pulls directly whatever code is present on that paho-mqtt-2.x branch. So if a malicious commit is added to it, we can probably all pull it on our systems without even realizing. (I have nothing against the author of this fork, I’m just slightly cautious.)

"requirements": ["git+https://github.com/mmatuska/MerossIot.git@f3e0a223457f04a7ac2663d5ffea06c1fb46978d"] - So this might be a better idea since it directly pulls the commit that contains the fix and nothing more than that.

cc #541, #539

This is indeed a problem of dependency resolution on paho-mqtt referened in meross-iot. It already exists a PR updating it to 2.x albertogeniola/MerossIot#413 .

So, if you want a hotfix, waiting new releases, you can edit manifest.json and replace this line:

  "requirements": ["meross_iot==0.4.7.3"],

with

  "requirements": ["git+https://github.com/mmatuska/MerossIot.git@paho-mqtt-2.x"],

Gracias

Duplicate of #544 . Please update to v1.3.4, which solves the issue. Thanks to everyone and sorry for the late fix!

And thanks to everyone for being so nice. Don’t worry I’m just fine. I’m only getting busier (moved to a new apartment, getting married and so on 😃 )

cc #541, #539 This is indeed a problem of dependency resolution on paho-mqtt referened in meross-iot. It already exists a PR updating it to 2.x albertogeniola/MerossIot#413 . So, if you want a hotfix, waiting new releases, you can edit manifest.json and replace this line:

  "requirements": ["meross_iot==0.4.7.3"],

with

  "requirements": ["git+https://github.com/mmatuska/MerossIot.git@paho-mqtt-2.x"],

Invalid requirement 'git+https://github.com/mmatuska/MerossIot.git@paho-mqtt-2.x' Im getting the following error when trying the hot fix.

Same error to me. I am using Home Assistant OS.

Finally the workaround worked for me in 2025.3.1. Thank you.

Please re-download via HACS and restart HA after that. Let me know if that solves!

Yep… why did that happen? Never seen that before? Did you forget to update the version number in 1.3.6 at first or was it a HACS bug?

My fault, code has been updated and tagged correctly, but version value in info.json was still wrong.

So it seems it’s now working as expected, so I am closing this issue. Thanks everyone!

cc #541, #539

This is indeed a problem of dependency resolution on paho-mqtt referened in meross-iot. It already exists a PR updating it to 2.x albertogeniola/MerossIot#413 .

So, if you want a hotfix, waiting new releases, you can edit manifest.json and replace this line:

  "requirements": ["meross_iot==0.4.7.3"],

with

  "requirements": ["git+https://github.com/mmatuska/MerossIot.git@paho-mqtt-2.x"],

Confirmed works for me as well. Thanks @b0l0k!

Thanks to everyone involved in the hotfix, and also to @towerrh for the Studio Code Server recommendation that allowed me to repair a remote instance.

I am glad you got that working… I suggested @towerrh use “Studio Code Server”… But I only did that because a friend told me about it 1.5 years ago when I got into HA. Studio Code Server is wonderful it has allowed me to do many things with HA I wouldn’t have been able to do without.

I am so glad you have been able to fix your issue. I am getting to the point where I am concerned for @albertogeniola it is rare he is away from github this long without making any comments on a thread. Hopefully he is just on vacation somewhere enjoying life and not ill.

My bigger question is @albertogeniola still working on this project? I haven’t seen him comment on any issues on this project for a while. I am wondering if this project needs a new fork? The Merros Lan project is slowly not working on newer firmware so this Merros Iot project is critical. Hopefully someone can support this project going forward because their hasn’t been any new releases for over 4 months.

Sorry guys, v1.3.4 had a bug referencing a old meross-iot version. V1.3.6 should finally solve the issue. Sorry for that!

I just installed on to of the modified version and it worked.

I did the same thing, but the new version overwrote the modded manifest change.

Likewise, initially I used HACS to “redownload” the 1.3.4 version as it wasn’t showing as an update. Today, 1.3.6 showed as an update when I logged in - performed the “update” and still working as expected.

For me 1.3.4 on 2025.3.3 did’t fix the issue:

Setup failed for custom integration 'meross_cloud': Requirements for meross_cloud not found: ['meross_iot==0.4.8.0'].

I had to revert again the string in the manifest from meross_iot to MerossIot.git@paho-mqtt-2.x

1.3.4 look to work for me. I installed it no issues.

Duplicate of #544 . Please update to v1.3.4, which solves the issue. Thanks to everyone and sorry for the late fix!

And thanks to everyone for being so nice. Don’t worry I’m just fine. I’m only getting busier (moved to a new apartment, getting married and so on 😃 )

Congradulations…

I don’t see V1.3.4… It still shows 1.3.3 as the latest in HACS for me.

cc #541, #539

This is indeed a problem of dependency resolution on paho-mqtt referened in meross-iot. It already exists a PR updating it to 2.x albertogeniola/MerossIot#413 .

So, if you want a hotfix, waiting new releases, you can edit manifest.json and replace this line:

  "requirements": ["meross_iot==0.4.7.3"],

with

  "requirements": ["git+https://github.com/mmatuska/MerossIot.git@paho-mqtt-2.x"],

Superb! Worked for me, thank you!

thanks for the tips , even if now I know I must move to https://github.com/krahabb/meross_lan

Be aware that Merros_Lan is will not support all Meross devcies. I have a bunch of new wall plugs running the latest firmware and they are not supported under Meross LAN. I came to this add-on after having to abandon Meross land. I have been working with the developer of that add-on for a while to see if it can be resolved but I think the new firmware is doing some local encryption or something that he can’t support.

Thanks to everyone involved in the hotfix, and also to @JosephRDawson for the Studio Code Server recommendation that allowed me to repair a remote instance.

manifest.json

This is the fill Manifest file that should work. I posted it to avoid people having typos or other issues. This is one that is working for me.

Manifest edit works like a charm. Edit as above post for those scrolling: https://github.com/albertogeniola/meross-homeassistant/issues/542#issuecomment-2707903116 Many thanks.

@towerrh I have no explanation for you… Unless it is somehow a bad character that is not being shown.

On the remote chance this is that I have dropped my file into dropbox here https://www.dropbox.com/scl/fi/aaig08rayrhpw6bejbidm/manifest.json?rlkey=v28mcumz21mb96pg07b01sqca&st=9dszlawc&dl=0

Your welcome to try my working file. The fact @DarylMc just got it working means the method should still be working for you today.

I can only guess you have somehow a bad character or bad spacing in your file.

@DarylMc is that working for you now?

yes

@towerrh how is it not working for you?

This is still working for me on 2025.3.1

Image

Also note spacing and indentation is critical.

Absolutely. Tried that and restarted. Im getting this error…

Logger: homeassistant.util.package
Source: util/package.py:63
First occurred: 7:09:11 PM (2 occurrences)
Last logged: 7:09:12 PM

Invalid requirement 'git+https://github.com/mmatuska/MerossIot.git@paho-mqtt-2.x'

cc #541, #539

This is indeed a problem of dependency resolution on paho-mqtt referened in meross-iot. It already exists a PR updating it to 2.x albertogeniola/MerossIot#413 .

So, if you want a hotfix, waiting new releases, you can edit manifest.json and replace this line:

  "requirements": ["meross_iot==0.4.7.3"],

with

  "requirements": ["git+https://github.com/mmatuska/MerossIot.git@paho-mqtt-2.x"],

Invalid requirement 'git+https://github.com/mmatuska/MerossIot.git@paho-mqtt-2.x' Im getting the following error when trying the hot fix.

Interesting. Not only did this fix the integration, but it may have also solved a problem I was having with authentication issues with fitbit and tuya. For awhile, every time I had to restart HA I have had to reauthenticate those two integrations. While they both authenticated quickly and correctly each time it was getting annoying and I started researching to see if anyone else was having this issue. I found this post:

https://community.home-assistant.io/t/every-reboot-authentication-expired-tuya-google-fit-fitbit/848894/6?u=rpitera

and in it the other user said that when he deleted the Merros IOT integration the authentication issues went away. I just applied your work-around and after restarting HA I didn’t get the authentication issues for the first time in weeks. I wonder if the two things are truly related?

Hi, I had the same issue. But affected Alarm.com and Google Calendar too, the calendar was disapearing after a reboot. I changed the requirement and it fixed the Calendar and Alarm.com integration.

cc #541, #539

This is indeed a problem of dependency resolution on paho-mqtt referened in meross-iot. It already exists a PR updating it to 2.x albertogeniola/MerossIot#413 .

So, if you want a hotfix, waiting new releases, you can edit manifest.json and replace this line:

  "requirements": ["meross_iot==0.4.7.3"],

with

  "requirements": ["git+https://github.com/mmatuska/MerossIot.git@paho-mqtt-2.x"],

Interesting. Not only did this fix the integration, but it may have also solved a problem I was having with authentication issues with fitbit and tuya. For awhile, every time I had to restart HA I have had to reauthenticate those two integrations. While they both authenticated quickly and correctly each time it was getting annoying and I started researching to see if anyone else was having this issue. I found this post:

https://community.home-assistant.io/t/every-reboot-authentication-expired-tuya-google-fit-fitbit/848894/6?u=rpitera

and in it the other user said that when he deleted the Merros IOT integration the authentication issues went away. I just applied your work-around and after restarting HA I didn’t get the authentication issues for the first time in weeks. I wonder if the two things are truly related?