Cron actions #1483
Annotations
10 errors and 3 warnings
|
Hassfest validation
[SERVICES] Service yearly has a field currency with no name and is not in the translations file
|
|
Hassfest validation
[SERVICES] Service yearly has a field year with no name and is not in the translations file
|
|
Hassfest validation
[SERVICES] Service yearly has a field area with no name and is not in the translations file
|
|
Hassfest validation
[SERVICES] Service daily has a field currency with no name and is not in the translations file
|
|
Hassfest validation
[SERVICES] Service daily has a field year with no name and is not in the translations file
|
|
Hassfest validation
[SERVICES] Service daily has a field area with no name and is not in the translations file
|
|
Hassfest validation
[SERVICES] Service monthly has a field currency with no name and is not in the translations file
|
|
Hassfest validation
[SERVICES] Service monthly has a field year with no name and is not in the translations file
|
|
Hassfest validation
[SERVICES] Service monthly has a field area with no name and is not in the translations file
|
|
Hassfest validation
[SERVICES] Service hourly has a field currency with no name and is not in the translations file
|
|
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.
|
|
Hassfest validation
[MANIFEST] Domain collides with built-in core integration
|
|
Hassfest validation
[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.
|
Loading