I recently made the switch from ZHA to Zigbee2MQTT and noticed a significant increase in my database size. Initially, I thought it was due to more frequent state changes, but after some research and tweaking, I found a few solutions that might help others facing the same issue.
First, I adjusted my recorder settings to ensure only necessary entities were being tracked. This involved reviewing the entities table and removing any redundant entries. I also made sure that the auto_purge settings were optimized to keep my database from ballooning too quickly.
Another thing I discovered was the importance of regular database maintenance. I started monitoring the size of my events, states, and state_attributes tables and set up a script to alert me if they exceeded a certain threshold. This proactive approach has helped me stay on top of things and prevent any unexpected growth.
I’d love to hear from others who have successfully managed their database sizes with Zigbee2MQTT. What strategies have worked for you? Any tips or tricks you’d like to share? Let’s keep the conversation going and help each other make the most of this fantastic integration!