Errors & warnings in case of any failures are flooding DB.
They may be generated really fast → DB is flooded → DB is growing → no space left on a device
These messages could be like:
{“name”:“homeassistant.helpers.entity”,“message”:[“Update for sensor.htpc_asus_z170_a_nuvoton_nct6793d_temperatures_temperature_6 fails”],“level”:“ERROR”,“source”:[“helpers/entity.py”,942],“timestamp”:1708058055.8718996,“exception”:“Traceback (most recent call last):\n File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 942, in async_update_ha_state\n await self.async_device_update()\n File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1261, in async_device_update\n await hass.async_add_executor_job(self.update)\n File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run\n result = self.fn(*self.args, **self.kwargs)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/usr/src/homeassistant/homeassistant/components/openhardwaremonitor/sensor.py", line 104, in update\n values = array[path_number]\n ~~~~~^^^^^^^^^^^^^\nIndexError: list index out of range\n”,“count”:1,“first_occurred”:1708058055.8718996}
and I see no use for them in DB.
And these old records are not purged on HA reboot.
That particular message was about OpenHardwareMonitor.
The integration is updated every 30 sec (by default), this message comes for every sensor (let it be 20 sensors).
When smth bad happen with HA/setup - amount of records within a minute could be very much higher, other integrations, other components of HA, …
Is there any way to block these messages from being recorded into DB?
I guess someone may start saying here “you should find out a reason of these errors/warnings instead of asking silly question”. Thank you, Cap, this kind of advice not needed. Finding reasons is another task.
1 post - 1 participant
Read full topic