I have a handful of Motion Lighting apps which aren't working the way I was hoping. I want the lights to turn off when motion stops no matter what, but I only want motion to turn the lights on during Evening mode. This is a sample configuration, all the apps are configured similarly.
The lights turn on and off as expected during Evening mode. However, the lights do not turn off during other modes when motion stops. I thought that setting the "Switches to activate on" setting would cause the motion app to turn the lights off as expected after the switch was used to turn the lights on, but it doesn't appear to be doing it. Any ideas?
Nothing looks odd to me there, but I have a guess: does it work as expected if you specify a delay for every mode, not just evening? (I'd try something like 1 rather than 0 if you want a small delay, just to rule values that might be "Groovy false" out as a possible problem here, but you can try it if you have success with non-zero numbers.) I wonder if it's just totally ignoring the off options in that case instead of simply using no delay. I might consider this a bug, but as far as I can tell, it's just undocumented behavior, so who knows. 
I set a delay of 1 for all other modes last week, following your reply. I just checked my dashboard, and it's still not shutting the lights off when the motion detectors go inactive though 
Hmm. Maybe try re-creating the app? I don't want to suggest "solutions" that are at best workarounds and might not actually work, but I don't see anything wrong with the setup above, so it's one thing you could try to see if it helps. (I'm assuming you've already just gone into this app and hit "Done," which can help in the rare event the app missed some device subscription it was supposed to create.)
