Closed lukakama closed 4 years ago
Actually, to avoid to wear to death the new SD card, I excluded all the cast media_players from the recorder component, but this is somewhat not ideal.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
As a household that has a lot of Twitch on, this has been an issue for me as well. This is swelling my log files to as much as 21GB over the course of a week as multiple chromecasts are in use. It would be nice to disable state updates for changes in "media_position".
The problem
I just had an SD card totally consumed after some months on a RPI. Trying to digging into the cause, I noticed that the home-assistant_v2.db was a bit too big (1GB with 7 days retention) for the HA load. Looking up into the events table, I got a huge amount of "state_changed" events on my chromecast while playing contents, one each 0.2 - 0.3 seconds, where the only changed attributes are "media_position" and "media_position_updated_at".
These are the records inside the events table while playing a Twitch video for some seconds:
I reported it in an improvement ticket https://github.com/home-assistant/architecture/issues/101#issuecomment-599068905 , and got a suggestion that at least these excessive position updates should be fixed in the originating component.
Environment
Problem-relevant
configuration.yaml
N/A
Traceback/Error logs
N/A
Additional information
N/A