Error spam for sensor

Configuration
1

I see lots of log related posts but haven’t discerned a solution. Periodically I’ll get a log file completely filled with sensor report errors. Is there a way to set all sensor warnings to only send a few then a final “haven’t heard from” message then stop spamming? Here’s an excerpt an error every 5-6 seconds forever:

2018-11-11 22:52:03 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05

2018-11-11 22:52:09 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05
2018-11-11 22:52:15 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05
2018-11-11 22:52:21 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05
2018-11-11 22:52:27 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05
2018-11-11 22:52:33 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05
2018-11-11 22:52:39 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05
2018-11-11 22:52:45 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05
2018-11-11 22:52:51 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05
2018-11-11 22:52:57 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05
2018-11-11 22:53:03 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05
2018-11-11 22:53:09 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05
2018-11-11 22:53:15 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05
2018-11-11 22:53:21 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05
2018-11-11 22:53:27 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05
2018-11-11 22:53:33 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05
2018-11-11 22:53:39 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05

2

Not that I’m aware of. I’ve implemented such a function in a couple of custom components I’ve written, but I’m not aware of a generic feature that does something like this for any type of error.