No 'version' key in the manifest file for custom integration

[Verguldebarman]

Current dev build of HA shows this warning:

2021-03-04 15:28:40 WARNING (MainThread) [homeassistant.loader] No 'version' key in the manifest file for custom integration 'eufy_vacuum'. This will not be allowed in a future version of Home Assistant. Please report this to the maintainer of 'eufy_vacuum'

More info can be found here: https://www.home-assistant.io/blog/2021/03/03/release-20213/#breaking-changes see Custom integrations: Version warning:

Custom integrations now require a version key in their manifest file, this also means that all custom integrations now require a manifest file.

If you are using a legacy custom integration like custom_components/awesome.py this now needs to move to custom_components/awesome/init.py so you can add custom_components/awesome/manifest.json to it.

For more information about integration, manifests have a look here: https://developers.home-assistant.io/docs/creating_integration_manifest

For now, this will create a warning on startup. But this will eventually be blocked from loading if it’s missing a version in the manifest.

[HumanSkunk]

I fixed this myself by adding my own manifest file as it looks like this is no longer being maintained. If you haven't done it yet just go into the File Editor add-on and navigate into the custom_components folder for this integration.

Create a new file and call it manifest.json

Once added paste the below text into the file and restart home assistant. This should stop the error and stop it from breaking next month.

{
  "domain": "eufy_vacuum",
  "name": "EufyVacuum",
  "version": "1.1.0",
  "documentation": "https://www.home-assistant.io/integrations/blah",
  "codeowners": []
}

[3ative]

I did something similar ... https://github.com/mitchellrj/eufy_robovac/issues/29#issuecomment-860109877