Skip to content

Validate with hassfest #1409

Validate with hassfest

Validate with hassfest #1409

Triggered via schedule October 9, 2023 00:07
Status Failure
Total duration 1m 37s
Artifacts

hassfest.yaml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
validate
[SERVICES] Service call_method has no name and is not in the translations file
validate
[SERVICES] Service call_method has a field entity_id with no name and is not in the translations file
validate
[SERVICES] Service call_method has a field command with no name and is not in the translations file
validate
[SERVICES] Service call_method has a field parameters with no name and is not in the translations file
validate
[SERVICES] Service search has no name and is not in the translations file
validate
[SERVICES] Service search has a field entity_id with no name and is not in the translations file
validate
[SERVICES] Service search has a field query with no name and is not in the translations file
validate
[SERVICES] Service search has a field filter with no name and is not in the translations file
validate
[SERVICES] Service search has a field limit with no name and is not in the translations file
validate
[SERVICES] Service add_to_playlist has no name and is not in the translations file
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.
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/