I’ve tried for 2 solid weeks trying every method and suggestion to get a motion sensor to turn light on when entering room, and turn off when no activity detected.
I have a new Vera 3 with latest firmware, and the sensor is an EZ Motion 3 in 1
I’ve tried a scene to turn lights on, with trigger using motion sensor tripped, and scene to turn off when motion señor is not tripped
I’ve tried the lump code method on these forums
HELP - does anyone have a fool proof way to get such a scenarios to work?
This is the sole reason I bought all this gear, to have lights come on in office when I walk in, and turn off after about 10 minutes when no motion is detected
The scene that was created to turn the light on when there is motion, it does not turn the light on at all? Is any part of it working? I have my motion sensors setup similar to this and have no issues. When I get home today, I’ll try and get some screen shots of how my scene is setup for one of my motion sensors. Does the EZ Motion 3 in 1 work in Vera? Meaning that it will show that it is tripped if motion is detected?
One way of setting that up is to have the sensor do the timing: set parameter [tt]2-On time[/tt] (on the [tt]Device Options[/tt] tab) to a value of 10 (minutes). Make sure [tt]4-Light Threshold[/tt] is set to 100 for now.
You should then be able to create the two scenes as you describe (using [tt]An armed sensor is tripped[/tt]/[tt]Device armed is tripped[/tt] and [tt]An armed sensor is tripped[/tt]/[tt]Device armed is not tripped[/tt]) to turn the light on or off.
I’m pretty sure I was getting things right - maybe I have a dodgy sensor. It does seem to turn the lights on in most cases I’ve tried, but not off, or turns them off in a few seconds no matter what settings I have in the scenes…
garretwp, the motion sensor shows up in vera and I can trip it and see the commands sent. I’d really appreciate the screen shots…
I’m not ramped up on MCV specifics however you might want to ensure that old triggers get killed properly when another movement is triggered via the motion detector.
Vera might do this kind of housekeeping for you automagicly, however one HA product I used a few years ago ddn’t and not clearing them out was truly a bad thing lights would turn off at seemingly random times till I figured it out my mistake.
In the end no matter what the system is… LOGS are your key… Always, period, end of sentence. ;D
If you have them turned off or to quiet mode then turn the logging up to the most verbose setting possible and perform a single test and quickly check the logs to see if it’s reporting what you’d expect. Then test a step further rinse and repeat until you find where things go off the track.
[quote=“DaveGee, post:6, topic:171515”][…] you might want to ensure that old triggers get killed properly when another movement is triggered via the motion detector.
Vera might do this kind of housekeeping for you automagicly, however one HA product I used a few years ago ddn’t and not clearing them out was truly a bad thing lights would turn off at seemingly random times till I figured it out my mistake.[/quote]
Vera doesn’t do this housekeeping. That’s what the Countdown Timer plugin attempts to solve by doing its own timer instead of using the one in the MiOS UI.
Gotcha … Good. Into to know for when I get my Vera and dive into plugin development. My problem is just coming up with the funds and more to the point getting the manditory BHA so I can proceed. The problem is (as most married folks will tell you) BHA’s are often mired inred tape and quid pro quo’s and direct payoffs are standard operating procedures before getting a BHA aka “Better Half Approval”.
Lol
Best Home Automation shopping experience. Shop at Ezlo!