Ghost yaml?

Hi all!

Recently i wanted to add todoist but ran in some strange issue.

In the past i had a xiamio plant sensor but later removed it. After editing the configuration.yaml through the front end i went to check if it is correct and i ran into the following:

Platform error sensor.miflora - Integration ‘miflora’ not found.

After checking the logs i found this:

[546927494848] Cannot quick reload all YAML configurations because the configuration is not valid:
Platform error sensor.miflora - Integration ‘miflora’ not found.
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py”, line 226, in handle_call_service
await hass.services.async_call(
File “/usr/src/homeassistant/homeassistant/core.py”, line 1974, in async_call
response_data = await coro
^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/core.py”, line 2011, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/helpers/service.py”, line 980, in admin_handler
await result
File “/usr/src/homeassistant/homeassistant/components/homeassistant/init.py”, line 316, in async_handle_reload_all
raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: Cannot quick reload all YAML configurations because the configuration is not valid: Platform error sensor.miflora - Integration ‘miflora’ not found.

Where and how can i find this so i can remove it and check my yaml and restart my home assistant?

The configuration.yaml is editable under /config

Thanks, that fixed it.

However poses the following question: what is the difference with the frontend configuration.yaml??

What frontend configuration.yaml?

The frontpagine of my automations → three dots → configure UI → Three dots upper right corner → raw config editor.

Does are two different config yamls?

I feel you guys are about to teach me an epifany moment after years of using home assistant…

That’s only your automation configuration, it’s one section of your entire configuration. And you’re specifically editing automations.yaml in that situation, not configuration.yaml.

1 Like

This my good sir is new information and thereby tackles the problem. In my mind i was editing the configuration.yaml… That explains the errors and it is now fixed!

Thanks guys!

1 Like