Describe the bug
No 'version' key in the manifest file for custom integration 'jumbo'. This will not be allowed in a future version of Home Assistant. Please report this to the maintainer of 'jumbo'
Additional context
Since Release 2021.3:
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.
peternijssen
commented
3 years ago
Describe the bug No 'version' key in the manifest file for custom integration 'jumbo'. This will not be allowed in a future version of Home Assistant. Please report this to the maintainer of 'jumbo'
Additional context Since Release 2021.3: 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.
If you see these warnings, please report the issue with the author of that custom integration.
(@ludeeus - #45919)