Skip to content

Validate with hassfest #1347

Validate with hassfest

Validate with hassfest #1347

Triggered via schedule November 28, 2024 00:56
Status Failure
Total duration 25s
Artifacts

hassfest.yaml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
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.