Alot of Motion ms13a best approach

[TeleFragger]

Ok so i have alot of motion sensors.. ms13a's...
bought 19 from ebay a while back.. i installed them up and had them going but never got around to doing anything with them..

now my garage has 1.. and it works now..

is there a rule of thumb..
i tried putting them on different house codes..

so is it best to put them on the same.. say M then use ac-rf 2 plugin to add 16 to the number?

this would give me M17-M33 (not touching any x10 usable codes)

or keep say.. foyer on F, hallway on H, garage on G, etc....

guess im trying to figure if there is any configuration that can hinder performance......

Im running pretty well after my reinstall (back to 2.4) and havent enabled any rf based items.. ms13a and ds10a are next....

[rmasonjr]

You also have to think about if you want the Dusk/Dawn/Light detection functionality. I only have one MS that I need the light detection. So, I put almost all my MS's on housecode M with odd numbers for motion and I just ignore the even numbers on all but one sensor.

[TeleFragger]

i have dusk dawn turned off... my kids turn the lights on during the day.. drives me nuts.. so i want it to turn the lights off after say 3 minutes...

with it off.. the ms13a doesnt use 2 house codes.. at least i didnt notice it doing so....

[chewie]

You are correct Telefragger, if you have Dusk/Dawn turned off you only use 1 house code on the MS13. If you turn it on it will use the code it is set too as well as the code directly following that one. That being said I set my MS up the same way rmasonjr described, M1 is motion and M2 is reserved in case I turn on the Dusk/Dawn sensor for that device. I leave it turned off on all the devices that I do not actively look for light on to conserve battery life.

[TeleFragger]

ok so then them all being on M is not a bad thing then... i tried hs 2.5.x.many and just had constant motion issues.... thinking it was too many on M... now im back on 2.4 world and going to set it all up and see if it all works good or if i see the same problems... i believe i have 19 motions to setup....forget the count now... some are ms10a

[RAM]

ok so then them all being on M is not a bad thing then... i tried hs 2.5.x.many and just had constant motion issues.... thinking it was too many on M... now im back on 2.4 world and going to set it all up and see if it all works good or if i see the same problems... i believe i have 19 motions to setup....forget the count now... some are ms10a

I have most of my motions on one or two house codes and then set ACRF2 to emulate but not re-transmit those house codes. That keeps all the motion sensor traffic off the power lines. I then have either events or BLRadar do any actions I want to do based on motion.

[TeleFragger]

I have most of my motions on one or two house codes and then set ACRF2 to emulate but not re-transmit those house codes. That keeps all the motion sensor traffic off the power lines. I then have either events or BLRadar do any actions I want to do based on motion.

that is the info im looking for.. good tip.. ill do that as es my logs get FULL of motion senses... as i dont have them in HS yet.. so i couldnt say.. dont log event... ill do that to keep that traffic off the power line all together... good tip!

[Uncle Michael]

FWIW, I've found that the dusk/dawn sensor is useful for monitoring the battery on my motion sensors. I run a script once a day that looks to see if each device has detected motion or a dark/light transition in the past 24 hours. If neither, then I flag the device for a battery check. That way, I can just ignore the batteries until they die. (Most last over 3 years, some have lasted for 5.)

I also run another recurring script that checks each motion device in HS to see if it is on. If it is, the script turns if off. That avoids having the motion sensor appear to be stuck on when an off signal gets missed, as they regularly do. (I run my script every minute, but less frequently would work just as well, I think.)