Another zigbee2mqtt related thing.
The new release starts warning against attributes in selects defined by mqtt discovery as being too large in size and will not be recorded.
I cannot imagine why anyone would want to log these selects at all. Or why these entries have so many attributes.
To get rid of that warning (and make your logs a little smaller) you can add this to configuration.yaml
recorder:
exclude:
entities:
- select.zigbee2mqtt_bridge_log_level
- switch.zigbee2mqtt_bridge_permit_join
- sensor.zigbee2mqtt_bridge_permit_join_timeout
- sensor.zigbee2mqtt_bridge_version
There are some nice threads on this forum about how to limit the log sizes. If you do not already do this search for the topics (there are several topics)
improvements were implemented, so we may be moving in the right direction.
This write-up is about possible actions you can …
Preamble: @tom_l is the original author of this community guide. He proposed an analytical approach to decide for each entity_id whether to include or exclude it from the underlying database. @mbuscher suggested to go after the entities most often updated in the database, and exclude only those. Both approaches are now included in this community guide.
Target audience: anyone who uses an installation on flash memory like a Raspberry Pi with an SD card or an SSD drive, or anyone who wishes to re…
3 Likes