Skip to content

Hassfest Validate

Hassfest Validate #143

Triggered via schedule June 18, 2026 03:50
Status Failure
Total duration 22s
Artifacts

hassfest.yaml

on: schedule
Hassfest Validation
19s
Hassfest Validation
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
Hassfest Validation
Process completed with exit code 1.
Hassfest Validation
[MANIFEST] Domain is missing an IoT Class
Hassfest Validation
[MANIFEST] Invalid manifest: extra keys not allowed @ data['bluetooth'][0]['scan_mode']. Got 'active'
Hassfest Validation
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
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.