[MANIFEST] Manifest keys are not sorted correctly: domain, name, then alphabetical order

[SERVICES] Service set_known_position has a field entity_id with no name and is not in the translations file

[SERVICES] Service set_known_position has a field position with no name and is not in the translations file

[SERVICES] Service set_known_tilt_position has a field entity_id with no name and is not in the translations file

[SERVICES] Service set_known_tilt_position has a field position with no name and is not in the translations file

[TRANSLATIONS] Invalid strings.json: extra keys not allowed @ data['services']['set_known_position']['entity_id']. Got {'name': 'Entity ID', 'description': 'The ID of the blinds entity'}

[TRANSLATIONS] Invalid translations/en.json: extra keys not allowed @ data['services']['set_known_position']['entity_id']. Got {'name': 'Entity ID', 'description': 'The ID of the blinds entity'}

Process completed with exit code 1.

[CONFIG_SCHEMA] Integrations which implement 'async_setup' or 'setup' must define either 'CONFIG_SCHEMA', 'PLATFORM_SCHEMA' or 'PLATFORM_SCHEMA_BASE'. If the integration has no configuration parameters, can only be set up from platforms or can only be set up from config entries, one of the helpers cv.empty_config_schema, cv.platform_only_config_schema or cv.config_entry_only_config_schema can be used.

[TRANSLATIONS] config.title key has been moved out of config and into the root of strings.json. Starting Home Assistant 0.109 you only need to define this key in the root if the title needs to be different than the name of your integration in the manifest.

[TRANSLATIONS] config.title key has been moved out of config and into the root of strings.json. Starting Home Assistant 0.109 you only need to define this key in the root if the title needs to be different than the name of your integration in the manifest.