Why does one armed sensor being triggered arm other sensors?

Other Devices & Integrations Door Locks & Sensors
1

I have 4 motion sensors in the house. Two are armed, two are not. The problem I am having is that when one of the armed sensors is tripped, it then arms the two bypassed sensors. This happened after I ran a repair and a heal on my network.

Help would be GREATLY appreciated as my girlfriend is starting to think I have wasted money on MCV.

2

I have about 6 motion sensors, various brands, some armed some not, and I never seen this behavior. What’s the sensor brand? Are you sure you don’t have a scene somewhere that arms the sensors? Did you configure any direct associations?

3

Firstly, thank you very much for responding so quickly, Capjay. I love MCV but I am not a programmer/developer and I don’t mind experimenting but the lack of information available can be frustrating. I am especially frustrated with the lack of information about all the fields under the Advanced tab and what they do. So, again, THANK YOU!

I didn’t have this problem until I ran a Heal and a Repair on my system. I am not positive but I believe it changed the Advanced>Controlled Via field to “Zwave” from something else, possibly “No Parent.” I didn’t pay much attention before because it worked fine. All 4 sensors are Schlage RS200HC. I don’t think it’s a problem with the scenes I have running because I haven’t changed them since they were working OK. I am unfamiliar with direct associations. How would I tell if I have somehow enacted them?

4

I have had similar behaviour, so eg I was testing my watersensor and got a notification from my smoke detector. But this is more occasionaly then frequent, eg my doorsensor trips very often, but never sets off another one

5

Yes, the documentation can be better. You need to understand that the advanced tab is for advanced use only and should only be touched if you know what you are doing. Also the advanced tab will vary across device and plugin and will be different. I would highly check all of your scenes and the devices they control. Never assume they are all ok.

  • Garrett
6

Thanks for responding.

My problem seems to be very consistent. Once an armed sensor is tripped, all of the bypassed sensors will switch to armed.

7

First check to see if there are any clues in the log as to what is happening at the time your sensors change to armed. If it is happening through Vera rather than by association, there should be some record of some device or scene calling for the action.

To see the log in your browser: [url=http://yourveraipaddress/cgi-bin/cmh/log.sh?Device=LuaUPnP]http://yourveraipaddress/cgi-bin/cmh/log.sh?Device=LuaUPnP[/url]

To review your log locally … edit the log and delete the line near the top that says: pageScroll(); That will stop the auto scrolling to the bottom … allowing you time to review the log.

The above tip was stolen from RichardTSchaefer.

8

I think I have solved the problem thanks to Capjay and garrettwp. I had one scene that was triggering the other sensors to be armed. Dumb mistake on my part but thanks for all the help.

One additional question: why does one of my sensors send a notification as soon as the scene tells it to switch to armed? How do I disable this?

THANKS!

9

if you go into your sensor settings (the wrench), to the far right you see notifications. click on that, and see if yopu have any notifications set up, and if yes, if they are ticked. If they are, simply delete or untick