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

[Verguldebarman]

Current dev build of HA shows this warning:

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

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.

[DavidFFerreira]

this development is dead man...

[chillkiller]

@Verguldebarman https://github.com/jomwells/ambihue/issues/11#issuecomment-830707697

[chillkiller]

@Verguldebarman

https://github.com/valexi7/ambilights