Skip to content

Update const.py

Update const.py #44

Triggered via push March 19, 2026 21:35
Status Failure
Total duration 23s
Artifacts

hassfest.yaml

on: push
Hassfest Validation
21s
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 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. 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.