Validate #1031
Annotations
10 errors and 2 warnings
|
Run hassfest validation
[SERVICES] Service navigation_sc_request has a field id with no description and is not in the translations file
|
|
Run hassfest validation
[SERVICES] Service navigation_request has a field type with no name and is not in the translations file
|
|
Run hassfest validation
[SERVICES] Service navigation_request has a field type with no description and is not in the translations file
|
|
Run hassfest validation
[SERVICES] Service navigation_request has a field value with no name and is not in the translations file
|
|
Run hassfest validation
[SERVICES] Service navigation_request has a field value with no description and is not in the translations file
|
|
Run hassfest validation
[SERVICES] Service navigation_request has a field locale with no name and is not in the translations file
|
|
Run hassfest validation
[SERVICES] Service navigation_request has a field locale with no description and is not in the translations file
|
|
Run hassfest validation
[SERVICES] Service navigation_request has a field timestamp_ms with no name and is not in the translations file
|
|
Run hassfest validation
[SERVICES] Service navigation_request has a field timestamp_ms with no description and is not in the translations file
|
|
Run hassfest validation
[TRANSLATIONS] Invalid translations/en.json: expected a dictionary for dictionary value @ data['entity']['sensor']['vin']['state_attributes']['model']. Got 'Model'
|
|
Run 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.
|
|
Run hassfest validation
[MANIFEST] Domain collides with built-in core integration
|
Loading