Skip to content

Validate with hassfest #1756

Validate with hassfest

Validate with hassfest #1756

Triggered via schedule November 1, 2024 00:50
Status Failure
Total duration 24s
Artifacts

hassfest.yaml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
validate
[SERVICES] Service collect_garbage has no name and is not in the translations file
validate
[SERVICES] Service collect_garbage has a field entity_id with no name and is not in the translations file
validate
[SERVICES] Service collect_garbage has a field last_collection with no name and is not in the translations file
validate
[SERVICES] Service add_date has no name and is not in the translations file
validate
[SERVICES] Service add_date has a field entity_id with no name and is not in the translations file
validate
[SERVICES] Service add_date has a field date with no name and is not in the translations file
validate
[SERVICES] Service offset_date has no name and is not in the translations file
validate
[SERVICES] Service offset_date has a field entity_id with no name and is not in the translations file
validate
[SERVICES] Service offset_date has a field date with no name and is not in the translations file
validate
[SERVICES] Service offset_date has a field offset with no name and is not in the translations file
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/