Skip to content

Validate using hassfest #507

Validate using hassfest

Validate using hassfest #507

Triggered via schedule July 2, 2024 01:18
Status Failure
Total duration 1m 18s
Artifacts

hassfest.yaml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 1 warning
validate
[MANIFEST] Manifest keys are not sorted correctly: domain, name, then alphabetical order
validate
[SERVICES] Service dump_cache has no name and is not in the translations file
validate
[SERVICES] Service get_cache has no name and is not in the translations file
validate
[SERVICES] Service sl_find_location has no name and is not in the translations file
validate
[SERVICES] Service rr_find_location has no name and is not in the translations file
validate
[SERVICES] Service sl_find_trip_id has no name and is not in the translations file
validate
[SERVICES] Service sl_find_trip_pos has no name and is not in the translations file
validate
Process completed with exit code 1.
validate
[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.