Closed lmamakos closed 5 years ago
All of this info is within the attributes of the sensor but it is a hassle to break them out, which is why I added the events per detection. I agree the best solution is to fire events only above the confidence
threshold.
I was poking around at things, and noticed that my Home Assistant database was somewhat larger than I expected. While I have some cleaning up to do elsewhere, there's a very large number of events from this integration. Behold:
Most of these are detections with quite low confidence.
It might be nice to reduce the volume of these events that are generated and thrown through the Home Assistant state machine. What comes to my mind is some combination of these to reduce the overall volume of events generated:
I'm sure what's best in the spirit of things here, and the impact of other models that might work differently. Of course, I can also blacklist that service from the recorder database, but there remains a concern about the default behavior of shoving all the events into the database that we might want to consider?