Validate with hassfest #1189
Annotations
9 errors and 1 warning
|
Run home-assistant/actions/hassfest@master
[MANIFEST] Manifest keys are not sorted correctly: domain, name, then alphabetical order
|
|
Run home-assistant/actions/hassfest@master
[SERVICES] Service set_angle has no name and is not in the translations file
|
|
Run home-assistant/actions/hassfest@master
[SERVICES] Service set_angle has a field entity_id with no name and is not in the translations file
|
|
Run home-assistant/actions/hassfest@master
[SERVICES] Service set_angle has a field angle_low with no name and is not in the translations file
|
|
Run home-assistant/actions/hassfest@master
[SERVICES] Service set_angle has a field angle_high with no name and is not in the translations file
|
|
Run home-assistant/actions/hassfest@master
[SERVICES] Service set_timer has no name and is not in the translations file
|
|
Run home-assistant/actions/hassfest@master
[SERVICES] Service set_timer has a field entity_id with no name and is not in the translations file
|
|
Run home-assistant/actions/hassfest@master
[SERVICES] Service set_timer has a field timer with no name and is not in the translations file
|
|
Run home-assistant/actions/hassfest@master
Process completed with exit code 1.
|
|
Run home-assistant/actions/hassfest@master
[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.
|
Loading