Repository navigation
Initial public release #1
Annotations
7 errors and 3 warnings
|
Hassfest
Process completed with exit code 1.
|
|
Hassfest
[TRANSLATIONS] Invalid translations/en.json: extra keys not allowed @ data['config']['selector']. Got {'control_mode': {'options': {'auto': 'Auto', 'read_only': 'Read only', 'full': 'Full control'}}}
|
|
Hassfest
[TRANSLATIONS] Invalid strings.json: extra keys not allowed @ data['config']['selector']. Got {'control_mode': {'options': {'auto': 'Auto', 'read_only': 'Read only', 'full': 'Full control'}}}
|
|
Hassfest
[MANIFEST] Manifest keys are not sorted correctly: domain, name, then alphabetical order
|
|
HACS Validation
<Integration groove-max/ha-eybond-local> 2/8 checks failed
|
|
HACS Validation
<Validation description> failed: The repository has no description (More info: https://hacs.xyz/docs/publish/include#check-repository )
|
|
HACS Validation
<Validation topics> failed: The repository has no valid topics (More info: https://hacs.xyz/docs/publish/include#check-repository )
|
|
Quality Gate
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/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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
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. Node.js 20 will be removed from the runner on September 16th, 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
[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.
|