Skip to content

Validate

Validate #39

Triggered via schedule October 22, 2024 00:08
Status Failure
Total duration 43s
Artifacts

validate.yml

on: schedule
Hassfest Validation
16s
Hassfest Validation
HACS Validation
32s
HACS Validation
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 1 warning
Hassfest Validation
[TRANSLATIONS] Invalid translations/en.json: extra keys not allowed @ data['config']['step']['user']['host']. Got 'Host'
Hassfest Validation
Process completed with exit code 1.
HACS Validation
<Validation information> failed: The repository has no information file (More info: https://hacs.xyz/docs/publish/include#check-info )
HACS Validation
<Validation topics> failed: The repository has no valid topics (More info: https://hacs.xyz/docs/publish/include#check-repository )
HACS Validation
<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 )
HACS Validation
<Integration mukaschultze/ha-aquecedor-rinnai> 3/8 checks failed
Hassfest Validation
[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.