Skip to content

Validate with hassfest #300

Validate with hassfest

Validate with hassfest #300

Triggered via schedule November 2, 2023 00:09
Status Failure
Total duration 1m 18s
Artifacts

hassfest.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 1 warning
validate
[SERVICES] Service set_box_mode has a field Mode with no name and is not in the translations file
validate
[SERVICES] Service set_box_mode has a field Acknowledgement with no name and is not in the translations file
validate
[SERVICES] Service set_grid_delivery has a field Mode with no name and is not in the translations file
validate
[SERVICES] Service set_grid_delivery has a field Limit with no name and is not in the translations file
validate
[SERVICES] Service set_grid_delivery has a field Acknowledgement with no name and is not in the translations file
validate
[SERVICES] Service set_grid_delivery has a field Upozornění with 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.