Since today I have an issue with an integration but HA is not telling me which one it is.
Failed to restart Home Assistant
The system cannot restart because the configuration is not valid: Integration error: Sensors - Integration ‘Sensors’ not found. How can I see which is causing this?
Logger: homeassistant.components.websocket_api.http.connection
Source: components/hassio/init.py:705
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 5:14:35 PM (1 occurrences)
Last logged: 5:14:35 PM
[546836973888] The system cannot restart because the configuration is not valid: Integration error: Sensors - Integration ‘Sensors’ not found.
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py”, line 202, in handle_call_service
await hass.services.async_call(
File “/usr/src/homeassistant/homeassistant/core.py”, line 1738, in async_call
task.result()
File “/usr/src/homeassistant/homeassistant/core.py”, line 1775, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File “/usr/src/homeassistant/homeassistant/components/hassio/init.py”, line 705, in async_handle_core_service
raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: The system cannot restart because the configuration is not valid: Integration error: Sensors - Integration ‘Sensors’ not found.
I have only “sensor” in my configuration.yaml. I checked again and according to the system both configuration and automations.yaml are correct. The issue is new as I have been able to implement all kind of changes sofar.
When I try to reboot from the menu this is what I see
Failed to restart Home Assistant.
The system cannot restart because the configuration is not valid: Integration error: Sensor - Integration ‘Sensor’ not found.
The error message has not changed
Log Details (ERROR)
Logger: homeassistant.components.hassio
Source: components/hassio/init.py:694
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: October 8, 2022 at 7:45:39 PM (8 occurrences)
Last logged: 1:06:04 PM
The system cannot restart because the configuration is not valid: Integration error: Sensors - Integration ‘Sensors’ not found.
The system cannot restart because the configuration is not valid: Integration error: Sensor - Integration ‘Sensor’ not found.
The system cannot restart because the configuration is not valid: Invalid config for [sensor.template]: [sensor] is an invalid option for [sensor.template]. Check: sensor.template->sensor. (See ?, line ?). Integration error: Sensor - Integration ‘Sensor’ not found.
The system cannot restart because the configuration is not valid: Invalid config for [sensor.template]: [sensor] is an invalid option for [sensor.template]. Check: sensor.template->sensor. (See ?, line ?). Integration error: Sensors - Integration ‘Sensors’ not found.
I wonder if ‘template’ is a protected term for a sensor. Others may be able to confirm but you could try changing that entity id to something else. If you really want some help though, I suggest you share your config so we can see properly.
This is my configuration.yaml. I have remove passwords etc.
I rebooted my PI4 forcefully manually as I could not do that from within HA
Hopefully the 3 ticks will make things better legible
If you’re going to share YAML, please format it in a code block by including three backticks (```) above and below the YAML; otherwise, the YAML is basically unreadable.
Regardless, you have Sensor: a couple of lines below energy: in your config which needs to be sensor: (and actually, those should be moved to the mqtt: section anyway with the new format). It’s difficult to tell what the source of the other issues is without the YAML being formatted in a code block, so please edit your message accordingly.
I have added the 3 ticks. Hope you see something out of the ordinary. This did happen out of the blue. I have been updating HA without any further issues so far
everything from - platform: buienradar to right above utility_meter: needs to be put directly under sensor:
↓
- platform: template
sensor:
needs to be
- platform: template
sensors:
(but that format is now considered the legacy format, so you should consider changing them to the new format as shown here. To be fair though, I haven’t updated mine)
HAEdwin,
aplogies for the late response. I have indeed removed these settings.
What is new is that sometimes the solar data is not read during the day but somewhere at night the entire number shows up in one go. I’ve had this several times
This is an exmple where during the data nothing is received yet somewhere in the evening everything shows up in one go. This was October 30, 2022. It is doing the same for today. For the day nothing is shown…
Not sure what is causing this. I have the latest software, etc.
I could be network related. Is the EMA site also running behind on data? If the ECU can’t post it’s data to EMA it will try to repair data in the early morning flusing the ECU’s databuffer to EMA. So maybe there are some sort of connection issues going on during daytime like a duplicate IP-address or something.
There was apparently an update of hacs and apsystems waiting. Updated all and the numbers showed up. Weird but it seems to have been solved. Thanks for your help