Yes,
It seemed to complain about most (if not all) custom components,
but it was always in that config/custom_components folder,
and they have been working before updating HA.
Does the new HA no longer supports custom components?
Or does it expecting them to be updated somehow?
Updated:
there is a brand new requirement that all custom_components need to provide a version e.g.:
2021-06-29 07:38:13 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration circadian_lighting which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-06-29 07:38:13 ERROR (SyncWorker_1) [homeassistant.loader] The custom integration 'circadian_lighting' does not have a valid version key (None) 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
2021-06-29 07:38:13 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration humidex which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-06-29 07:38:13 ERROR (SyncWorker_2) [homeassistant.loader] The custom integration 'humidex' does not have a valid version key (None) 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
2021-06-29 07:38:13 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration lutron_caseta_pro which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-06-29 07:38:13 ERROR (SyncWorker_3) [homeassistant.loader] The custom integration 'lutron_caseta_pro' does not have a valid version key (None) 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
2021-06-29 07:38:13 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-06-29 07:38:13 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration localtuya which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-06-29 07:38:13 ERROR (SyncWorker_4) [homeassistant.loader] The custom integration 'localtuya' does not have a valid version key (None) 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
2021-06-29 07:38:13 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration flux which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-06-29 07:38:13 ERROR (SyncWorker_1) [homeassistant.loader] The custom integration 'flux' does not have a valid version key (None) 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
Just go check the git repo for the circadian_lighting,
it does contains an updated manifest that provides the version.
So trying to update the manifest and the init.py,
hopefully will resolve this issue.
It’s been a requirement since a couple releases, and a message was logged maybe as early as 2021.3, but indeed, as of 2121.6 (?), HA does not load the custom_component at all if a version key is not in the manifest.