#Multiple Motion Detection automation sometimes sends a LOT of notification.

1 messages · Page 1 of 1 (latest)

silent imp
#

Hello Community,

Please give me some good idea for my automation.

I created 4 automation.

  • Human detected by reolink camera: Send notification with Human emoji
  • Vehice detected by reolink camera: Send notification with Car emoji
  • Animal detected by reolink camera: Send notification with Cat emoji
  • Object detected by reolink camera: Send notification with Box emoji

My problem is if we go out with my girlfriend to the entrance with the dog and our cat and take them to the clinic lets say, we get about 50 notification.

2 people + 2 animal + 1 car / second for 20 second until we leave, nearly like this.

What is the most professional solution to prevent this and only get the first notification, its not a problem if I get also a human and an animal but do not get multiple in the next 1-2 minute.

Thank you very much guys as always 🙂
Best regards,
Gery

normal bay
#

you could start a timer when the automation fires and check that the timer is 0 as a condition

silent imp
#

Oh you are totally, right I does not even know why I didnt did this yet and why it was not in my thoughts. I did this multiple times earlier... too much pause in home assistant looks like.

normal bay
#

use one common timer or one for each class

#

i use it for motion detectors instead of relying on their unoccupied state. every time they fire within the cooldown period they restart the timer. should work for your camera as well. as long as it keeps detecting you it will not re-arm

silent imp
#

its like this but still sending, but I cannot test in live ,so I used Run automation.

normal bay
#

that should trigger the run but still check the condition i think

#

i made the timer as a helper manually

#

and then used that timer

gray drum
#

Another option is just put a delay on the end of the automation, rather than having a separate timer and condition

#

If the automation is in single mode it won't run again during the delay

#

Alternatively, you could give the notification an id, so they just override each other and you only see one compared to a stack of 20 notifications

normal bay
#

i have seen before someone having problem with a delay at the end of their automation not being honored. as if it was optimized away somehow. but in theory it should work.

the timer method gives the extra ability to choose if you want one timer per automation or one shared.

gray drum
#

If you want it shared, just make multiple triggers for a single automation