I just added a new Aeon siren to my Veralite running UI7 and it can be directly triggered by any armed motion sensor without any scene or setup. It is kind of annoying because I have geo fencing and ping sensor to detect my phones to switch between home mode and away mode, but due to the inaccuracy, often it will trigger the motion sensor or door sensor before it switches to home mode and disarm all the sensors. But even one armed sensor will trigger the siren and make big noise…
Is there any way to disable this default setting? I’m planning to make my own siren trigger logic. I still want to keep the armed sensors because it will send cell phone notification even though some false alarms, it is still OK just to double check and sweep it away. But every time to turn off a siren by a false alarm is a totally different story.
Here is the manual for the Aeon Sire: http://www.vesternet.com/downloads/dl/file/id/426/z_wave_aeon_labs_siren_engineering_specification.pdf
I don’t see a way to configure it to ignore motion sensor broad cast alarms.
What motion sensors are you using? You might need to configure them to not broad cast an alarm state to other nodes in the network (and instead use a Triggered Scene on the Vera to trip the Siren).
The motion sensor is also a Aeon, the 4 in 1 sensor not the latest gen6 one. I’m thinking don’t arm any sensor and make a scene which check mode, if in away mode then notify when sensors are triggered no matter armed or not. And write a separate logic for the siren to fire alarm like if tripped sensor number exceeds 3 within 10 minutes or something like that. It will avoid false alarm and real breakin will definitely trigger multiple security sensors in a short period of time.
Yep that should do it. The only sensors I arm in my setup are the water sensor, everything else I use scenes and modes as you have stated.
The siren now has an issue that keeps saying “setting user configuration”. But it can fire alarm no problem just annoying red error message. Any idea of fixing this?
I think this is a common issue with several devices after the last update that came out 2 weeks ago ish. I have more then one vera doing this to different devices at random also after update.