I'm using soundmeter running on a raspberry pi to monitor my smoke detector and so need to set up the trigger to distinguish the loud intermittent noise of the smoke detector. It is working well and much more stable than my previous attempts attaching a sound sensor to the GPIO. However, I haven't got the triggering parameters optimised yet.
If I set up something to detect a few consecutive events with a suitable threshold and audio_segment_length it will work but it will also be triggered by a similar intensity (or louder) short noise above the threshold (eg a door slamming).
It I set it up to detect a longer run of consecutive events it will not be triggered by the door slam but will not be triggered by the smoke alarm (due to the intermittent beeping)
If I set up something to detect a few consecutive events with a lower threshold and a longer segment it will work but it will also be triggered by a continuous noise above the threshold (eg the spin cycle on my washer)
I can't get a compromise between the two to work that avoids the false triggers.
What would be ideal would be if the trigger logic could be set to determine x out of y events that were above the threshold. Would that be easy to implement within soundmeter?
I'm using soundmeter running on a raspberry pi to monitor my smoke detector and so need to set up the trigger to distinguish the loud intermittent noise of the smoke detector. It is working well and much more stable than my previous attempts attaching a sound sensor to the GPIO. However, I haven't got the triggering parameters optimised yet.
If I set up something to detect a few consecutive events with a suitable threshold and audio_segment_length it will work but it will also be triggered by a similar intensity (or louder) short noise above the threshold (eg a door slamming).
It I set it up to detect a longer run of consecutive events it will not be triggered by the door slam but will not be triggered by the smoke alarm (due to the intermittent beeping)
If I set up something to detect a few consecutive events with a lower threshold and a longer segment it will work but it will also be triggered by a continuous noise above the threshold (eg the spin cycle on my washer)
I can't get a compromise between the two to work that avoids the false triggers.
What would be ideal would be if the trigger logic could be set to determine x out of y events that were above the threshold. Would that be easy to implement within soundmeter?
with thanks