I’m running Home Assistant on Ubuntu linux. I’ve recently noticed that when I’m casting to one of my chromecast audio devices, I’m seeing multiple updates per second to my system’s /var/log/syslog file that look like this:
Jul 15 10:59:42 [hostname] [username][2107]: 2018-07-15 10:59:42 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.kitchen_speaker, new_state=<state media_player.kitchen_speaker=playing; media_title=The Sunday Edition (CBC), app_name=TuneIn Free, supported_features=21437, friendly_name=Kitchen Speaker, is_volume_muted=False, media_position_updated_at=2018-07-15T10:59:42.803897-03:00, app_id=12F05308, media_position=7373.665712, media_content_id=http://cbc_r1_hfx.akacast.akamaistream.net/7/981/451661/v1/rc.akacast.akamaistream.net/cbc_r1_hfx, volume_level=0.30000001192092896, entity_picture=/api/media_player_proxy/media_player.kitchen_speaker?token=64ab52fc9591d3e7fee0895bada24d9a969d7a7af0e667b0b4b35ea3ed4bb068&cache=5aae637f2dce99a8 @ 2018-07-15T08:56:47.252448-03:00>, old_state=<state media_player.kitchen_speaker=playing; media_title=The Sunday Edition (CBC), app_name=TuneIn Free, supported_features=21437, friendly_name=Kitchen Speaker, is_volume_muted=False, media_position_updated_at=2018-07-15T10:59:42.544400-03:00, app_id=12F05308, media_position=7373.406054, media_content_id=http://cbc_r1_hfx.akacast.akamaistream.net/7/981/451661/v1/rc.akacast.akamaistream.net/cbc_r1_hfx, volume_level=0.30000001192092896, entity_picture=/api/media_player_proxy/media_player.kitchen_speaker?token=64ab52fc9591d3e7fee0895bada24d9a969d7a7af0e667b0b4b35ea3ed4bb068&cache=5aae637f2dce99a8 @ 2018-07-15T08:56:47.252448-03:00>>
I don’t know whether it’s Home Assistant itself, or the android app I’m using to cast that’s causing so many updates, but I’d like them to stop being logged. The only updates are changes to “media_position” and “media_position_updated_at”. I could do without logs for this minutia, and I can imagine that somebody running on a Raspberry Pi with limited disk space would appreciate this sort of thing not being logged as well.
Are there any settings to be able to ignore such changes in status, as least as far as logs are concerned?