Skip to content
Validate with hassfest

raise issue if units mismatch #395

Sign in to view logs

raise issue if units mismatch

raise issue if units mismatch #395

Triggered via push August 20, 2023 00:33
@dgomesdgomes
pushed bf5b433
master
Status Failure
Total duration 1m 8s
Artifacts –

hassfest.yaml

on: push
validate
59s
validate
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
validate
[MANIFEST] Manifest keys have been sorted: domain, name, then alphabetical order
validate
[SERVICES] Invalid services.yaml: expected str @ data['simular']['fields']['installed_power']['selector']['options'][0]. Got None
validate
[TRANSLATIONS] Invalid translations/en.json: extra keys not allowed @ data['options']['title']. Got 'Define new costs'
validate
Process completed with exit code 1.
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.
validate
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/