Validate with hassfest #1323
Annotations
10 errors and 3 warnings
validate
[MANIFEST] Manifest keys are not sorted correctly: domain, name, then alphabetical order
|
validate
[SERVICES] Service speak_text has no name and is not in the translations file
|
validate
[SERVICES] Service speak_text has a field entity_id with no name and is not in the translations file
|
validate
[SERVICES] Service speak_text has a field text with no name and is not in the translations file
|
validate
[SERVICES] Service execute_text has no name and is not in the translations file
|
validate
[SERVICES] Service execute_text has a field entity_id with no name and is not in the translations file
|
validate
[SERVICES] Service execute_text has a field text with no name and is not in the translations file
|
validate
[SERVICES] Service execute_text has a field silent with no name and is not in the translations file
|
validate
[SERVICES] Service call_action has no name and is not in the translations file
|
validate
[SERVICES] Service call_action has a field entity_id with no name and is not in the translations file
|
validate
[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.
|
validate
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
validate
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|