Validate #53
rodpayneAnnotations
10 errors and 3 warnings
|
Hassfest
[MANIFEST] Manifest keys are not sorted correctly: domain, name, then alphabetical order
|
|
Hassfest
[SERVICES] Service reverse_geocode has no name and is not in the translations file
|
|
Hassfest
[SERVICES] Service reverse_geocode has a field entity_id with no name and is not in the translations file
|
|
Hassfest
[SERVICES] Service reverse_geocode has a field force_update with no name and is not in the translations file
|
|
Hassfest
[SERVICES] Service reverse_geocode has a field friendly_name_template with no name and is not in the translations file
|
|
Hassfest
[SERVICES] Service geocode_api_on has no name and is not in the translations file
|
|
Hassfest
[SERVICES] Service geocode_api_off has no name and is not in the translations file
|
|
Hassfest
[SERVICES] Service process_trigger has no name and is not in the translations file
|
|
Hassfest
[SERVICES] Service process_trigger has a field entity_id with no name and is not in the translations file
|
|
Hassfest
[SERVICES] Service process_trigger has a field from_state with no name and is not in the translations file
|
|
HACS
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/
|
|
Test + advice with flake8
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
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.
|