meross-homeassistant: After update loading blocked - 'meross_cloud' does not have a version key in the manifest file

Describe the bug After updating today, integration is blocked from loading on restart. Was working fine prior to update. On inspection, it looks like part of the manifest.json is missing.

Your environment Home Assistant Core 2022.5.3 Home Assistant Supervisor 2022.05.0 Home Assistant OS 7.6 HAOS running in VM on Virtualbox - hosted on Win10 Meross Cloud version: 20200412.2, installed via HACS

Logs taken when the issue happened

2022-05-09 08:23:02 ERROR (SyncWorker_6) [homeassistant.loader] The custom integration 'meross_cloud' does not have a version key in the manifest file and was blocked from loading. See https://developers.home-assistant.io/blog/2021/01/29/custom-integration-changes#versions for more details

manifest.json in my local custom_components\meross_cloud

{
  "domain": "meross_cloud",
  "name": "Meross Cloud IoT",
  "documentation": "https://www.home-assistant.io/components/meross_cloud",
  "dependencies": ["persistent_notification"],
  "codeowners": ["@albertogeniola"],
  "requirements": ["meross_iot==0.3.3.0"],
  "config_flow": true,
  "meross_cloud_version": "unknown"
}

This doesn’t match the one in the repo at all, so I tried redownloading the integration in HACS but got the same manifest.json (refreshed dir just to make sure). While I’m sure I could resolve this by manually installing, I’m holding off on that in case that obfuscates the cause of problem.

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 1
Comments: 16 (1 by maintainers)

Most upvoted comments

@rpitera yes. mine says v1.2.1 correctly. i would recommend removing it completely through HACS. shut down HA, then make sure the directory is actually gone out of your custom_components directory. restart and there should be no trace of it remaining. HACS should say v1.2.1 is available to install then, that’s what it did for me. i installed, restarted, and all was well. it seems to me like yours wasn’t completely wiped out.

scottjl on May 11, 2022

@rpitera i uninstalled it completely, restarted HA, installed the ‘current’ 1.2.1 version, restarted HA again, and then it was working for me.

scottjl on May 10, 2022