Skip to content

Validate with hassfest #13

Validate with hassfest

Validate with hassfest #13

Triggered via schedule February 8, 2025 00:18
Status Failure
Total duration 22s
Artifacts

hassfest.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
validate
[MANIFEST] Domain is missing an IoT Class
validate
[TRANSLATIONS] Invalid translations/en.json: extra keys not allowed @ data['config']['success']. Got {'discovery_complete': 'All devices discovered successfully.'}
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.
validate
[TRANSLATIONS] config.title key has been moved out of config and into the root of strings.json. Starting Home Assistant 0.109 you only need to define this key in the root if the title needs to be different than the name of your integration in the manifest.