Skip to content

Validate with hassfest #640

Validate with hassfest

Validate with hassfest #640

Triggered via schedule August 25, 2023 00:51
Status Failure
Total duration 1m 21s
Artifacts

hassfest.yaml

on: schedule
Validate with hassfest
1m 11s
Validate with hassfest
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
Validate with hassfest
[MANIFEST] Manifest keys have been sorted: domain, name, then alphabetical order
Validate with hassfest
[SERVICES] Service reset_pid has no name and is not in the translations file
Validate with hassfest
[SERVICES] Service autotune_pid has no name and is not in the translations file
Validate with hassfest
Process completed with exit code 1.
Validate with hassfest
[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.
Validate with hassfest
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/