logger_filters.yaml

# When database file becomes unavailable, Home Assistant quickly runs itself
# into the ground (OOM-killer gets involved 😉) reporting the below two errors
# over and over again — the hope is that by not logging these, Home Assistant
# will at least keep running (which is better than crashing, restarting and
# coming backup in safe mode without anything working).
# This might cause some more benign errors to be filtered out too, for now
# that's an acceptable trade off...
homeassistant.components.recorder.core:
  - ^Error while processing event EventTask\(
  - >-
    ^Unrecoverable sqlite3 database corruption detected: (.*) unable to open
    database file
homeassistant.helpers.entity:
  # Neato
  - >-
    ^Update of (sensor|switch|vacuum)\.d7_[a-z0-9_]+ is taking over
    [0-9]+ seconds$
  # Xiaomi MIoT
  - >-
    ^Update of sensor\.qingping_air_monitor_lite_[a-z0-9_]+ is taking over
    [0-9]+ seconds$
  - >-
    ^Update of sensor\.xiaomi_miot_[a-z0-9_]+ is taking over [0-9]+ seconds$
  # Mopidy
  - >-
    ^Update of media_player\.[a-z0-9_]+ is taking over [0-9]+ seconds$
# The Neato integration generates *a lot* of warnings and errors; most of them
# are of temporary nature – the ones that aren't, are picked up by the general
# "device failure" automation...
homeassistant.components.switch:
  - ^Updating neato [a-z]+ took longer than the scheduled update interval
homeassistant.components.sensor:
  - ^Updating neato [a-z]+ took longer than the scheduled update interval
  # Xiaomi MIoT
  - >-
    ^Updating xiaomi_miot sensor took longer than the scheduled update
    interval
homeassistant.components.vacuum:
  - ^Updating neato [a-z]+ took longer than the scheduled update interval
homeassistant.components.neato.vacuum:
  - >-
    ^Neato [a-z]+ connection error for '.+': Unable to communicate with robot$
  - >-
    ^Could not fetch map boundaries for '.+': Unable to communicate with
    robot$
homeassistant.components.neato.sensor:
  - >-
    ^Neato [a-z]+ connection error for '.+': Unable to communicate with robot$
homeassistant.components.neato.switch:
  - >-
    ^Neato [a-z]+ connection error for '.+': Unable to communicate with robot$
# Xiaomi MIoT is somewhat verbose – these warnings/errors trigger multiple
# times daily, but don't appear to influence functionality...
custom_components.xiaomi_miot.sensor:
  - >-
    Got MiioException while fetching the state: ?(Unable to discover the
    device |No response from the device)?[a-zA-Z0-9_\-]*, mapping:
# Mopidy
homeassistant.components.media_player:
  - ^Updating mpd .+ took longer than the scheduled update interval
# Meater servers go offline *a lot*
homeassistant.components.meater:
  - >-
    ^Unexpected error fetching meater_api data: Error connecting to Meater
  - >-
    ^Error requesting meater_api data: Cannot connect to host
  - >-
    ^Timeout fetching meater_api data
# Testing the "Eufy Security" custom-component; works, but keeps throwing these
# when the camera-stream is not active – ignore this for now...
homeassistant.components.stream.stream.camera.bonus_room:
  - >-
    HTTP_NOT_FOUND.+rtsp:\/\/ha-yellow\.sgraastra:8554\/