Skip to content

Validate with hassfest #1152

Validate with hassfest

Validate with hassfest #1152

Triggered via schedule January 16, 2025 01:08
Status Failure
Total duration 22s
Artifacts

hassfest.yaml

on: schedule
Validate with hassfest
14s
Validate with hassfest
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 1 warning
Validate with hassfest
[MANIFEST] Manifest keys are not sorted correctly: 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 reset_pid has a field entity_id with 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
[SERVICES] Service autotune_pid has a field entity_id with 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.