In the settings of “dashboard > myModes > What to do if an armed sensor trips?” you can choose “on” or “off” for sirens and cams. This simple logic is not suitabele for my many sensors and several sirens in separate security zones. I use scene logics for these devices. For my cams the same applies.
So I setted “off” for all sirens and cams in “What to do if an armed sensor trips?”.
Since some days I watched inexplicible noises of the sirens and strange behaviour of some devices and processes. Today I found out, that for all sirens and cams "What to do if an armed sensor trips? was set to “yes”. Surely I didn’t do that.
These changes caused hight workload on the network and on vera because during the day every few minutes and partly more frequently the cam transfered large pics and and the sirens were switched on.
Fortunately only the sirens setted with a simple “pip” worked. The aeotec DSD31 sirens with long signals remained silent (maybe caused by the netzwork overload). However these sirens showed inexplicible reachability problems.
Any idea what reason could have changed the “What to do if an armed sensor trips?” settings? I do not remember there was a firmware update in this period.
Any idea what’s to do to avoid such a change of settings in future, because the consequences could be much more evil?