Skip to content

Fix hassfest issues #99

Fix hassfest issues

Fix hassfest issues #99

Triggered via push July 4, 2024 17:16
Status Failure
Total duration 1m 13s
Artifacts

validate.yaml

on: push
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 water_plant has a field device_id with no name and is not in the translations file
validate
[SERVICES] Service water_plant has a field device_id with no description and is not in the translations file
validate
[SERVICES] Service set_smart_watering has a field device_id with no name and is not in the translations file
validate
[SERVICES] Service set_smart_watering has a field device_id with no description and is not in the translations file
validate
[SERVICES] Service set_scheduled_watering has a field device_id with no name and is not in the translations file
validate
[SERVICES] Service set_scheduled_watering has a field device_id with no description and is not in the translations file
validate
[SERVICES] Service delete_watering has a field device_id with no name and is not in the translations file
validate
[SERVICES] Service delete_watering has a field device_id with no description and is not in the translations file
validate
Process completed with exit code 1.
validate-hacs
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/