Closed pixiandreas closed 3 years ago
Thanks. I'll fix it
On Tue, Mar 16, 2021 at 10:21 PM pixiandreas @.***> wrote:
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.
home-assistant/core#45919 https://github.com/home-assistant/core/pull/45919
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/joggs/home_assistant_ebeco/issues/4, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACLJXL42JLAAJJNW3XBZ3TTD7DTZANCNFSM4ZJK6H5A .
--
/Jörgen Bergström
Fixed
home-assistant/core#45919