Fix mqtt_basic_async example conf handling (#69) #1690
MartinHjelmareAnnotations
7 errors and 3 warnings
|
validate
[SERVICES] Service demo has no name and is not in the translations file
|
|
validate
[SERVICES] Service demo has no name and is not in the translations file
|
|
validate
[SERVICES] Service set_state has no name and is not in the translations file
|
|
validate
[SERVICES] Service set_state has a field new_state with no name and is not in the translations file
|
|
validate
[SERVICES] Service set_state has no name and is not in the translations file
|
|
validate
[SERVICES] Service set_state has a field new_state with no name and is not in the translations file
|
|
validate
Process completed with exit code 1.
|
|
validate
[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.
|
|
validate
[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.
|
|
validate
[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.
|