Skip to content

Update config_flow.py #19

Update config_flow.py

Update config_flow.py #19

Triggered via push April 14, 2024 21:07
Status Failure
Total duration 1m 14s
Artifacts

validate.yml

on: push
validate-hassfest
1m 6s
validate-hassfest
validate-hacs
24s
validate-hacs
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 1 warning
validate-hacs
<Validation topics> failed: The repository has no valid topics (More info: https://hacs.xyz/docs/publish/include#check-repository )
validate-hacs
<Validation brands> failed: The repository has not been added as a custom domain to the brands repo (More info: https://hacs.xyz/docs/publish/include#check-brands )
validate-hacs
<Integration cdnninja/yoto_ha> 2/8 checks failed
validate-hassfest
[SERVICES] Service update has no name and is not in the translations file
validate-hassfest
[SERVICES] Service update has no description and is not in the translations file
validate-hassfest
[SERVICES] Service update has a field device_id with no name and is not in the translations file
validate-hassfest
[SERVICES] Service update has a field device_id with no description and is not in the translations file
validate-hassfest
Process completed with exit code 1.
validate-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.