MS II behavior

[jkraus]

Upgraded to 5.x (went very well), added a MS II, but it does not seem to be acting the same way as the original MS.  The old one would send a new ON command each time it was triggered, but the new one does not seem to.  Hear's how I am using the old one, let me know some thought on how to duplicate it with the MS II

Old set up for a garage lite

• Had MS to send ON only
• had the MS in a a scene to control a light
• had a program to turn off the light IF certain time was met AND a min remote switch was in the OFF potion

I did it this way so that since it was in the scene the ON would be quick, but the OFF was determine by a program and the condition of a switch so that I could override the OFF because sometime if we are in the garage without much motion it would turn off.

The program would continue to reset the timer since each time it received a new ON command it would start over.  with the new MS does not seem to work so I assume that the new MS does not repeat ON commands each time it detects motion....or as very possibly, I am missing something

Thanks

Joe

 

Edited January 17, 2019 by jkraus

[mitchmitchell]

I have an MS II programmed exactly as you describe.  I think there is a timeout timer that can be configured to control how long it waits until it searches for new motion -- I think its the same time it would wait to turn a device off if it were programmed to send off commands.  Ours works fine, but I've never had a reason to research whether it was sending repeated on commands or not -- it just hasn't given us any trouble.

[jkraus]

OK, maybe your on to something, as have not quite got all of the settings yet (eg not sure what multiple nodes does), but you said you have your working, can your tell me how or copy the program here?

[kclenden]

Select the motion sensor and click "Options".  Under Motion there should be a setting for "Timeout".  That's how long the motion sensor will wait before it starts sensing motion again after it detects motion.  That value should be less than the length of time you set your program timer.  The lower you set the "Timeout" the more often the motion sensor will have to detect motion, but I presume that will also make it use battery quicker.

Another issue can be if you configure the motion sensor to turn on a light only at night.  Once the light comes on, the motion sensor no longer thinks it's night, so doesn't send any more "On" commands, even if it senses you moving, until the light goes out and it again thinks it's night.

Edited January 17, 2019 by kclenden
Add paragraph about "Only At Night"

[mitchmitchell]

I think I captured all the programs here.   Note that the condition on the Actions folder keeps the light from switching off if under manual control.  I don't have anything special set up to restart the timer.  Sorry, I originally grabbed the options tab from the old sensor.

Edited January 17, 2019 by mitchmitchell

[jkraus]

Thanks Mitch, really appreciate it.

I will have to digest this, but in practice, if the timer runs out and there is still motion, the light goes our for a while then back on after it can detect more motion?  My previous solution was so elegant because this never happened as it kept sending ON signals so the timer kept resetting.

Thnaks again, I really appreciate your extra effort!

Joe

[kclenden]

45 minutes ago, jkraus said:

I will have to digest this, but in practice, if the timer runs out and there is still motion, the light goes our for a while then back on after it can detect more motion? 

Configured with a short motion sensor "Timeout", say 10 seconds, and a longer program timer, say 2 minutes, the light should stay on if you continue to move around.  Assuming the MS sees you, it will send an ON command every 10 seconds, restarting the program timer.  That's how my MS II sensors functions.

[jkraus]

Yea, agree.  I tried that and it did not seem to work.  on my old MS that would certainly work, but the new MS  II it seems  that when the motion timer program times out the lite  the tuns off the lite even if more motion was seen, like the new motion did not restart the program timer.  Do you have this working with an MS II?

Thx

Joe

Edited January 17, 2019 by jkraus

[kclenden]

Yep.  The MS II works like a charm for me.  You should post your programs.  And maybe even a screen shot of your MS II options.

Edited January 17, 2019 by kclenden

[jkraus]

OK, let me rewrite it and see if works, if not will post.  Thnaks much

[jkraus]

Hmm...now works perfectly, just like original MS.  My only guess is when I was in testing modes I had the time difference between time out and program timer too small, with larger times works fine.  Thanks All!

[jec6613]

I'm just posting here so I can find this thread more easily this weekend.

[mitchmitchell]

With my programs, the light doesn't go out if there is motion - but if you've got it working with simpler code, please post your programs as I am always looking for better algorithms!

Sent from my SM-N950U using Tapatalk

[larryllix]

10 hours ago, jkraus said:

Yea, agree.  I tried that and it did not seem to work.  on my old MS that would certainly work, but the new MS  II it seems  that when the motion timer program times out the lite  the tuns off the lite even if more motion was seen, like the new motion did not restart the program timer.  Do you have this working with an MS II?

Thx

Joe

That sounds like you do not have the Report "On Only"" checked.. 

[jkraus]

here is my simple program note that the workbench lite is part of a scene so the "turn on" in this program is redundant

(and yes I do have the "on only" enabled)

Edited January 22, 2019 by jkraus