How to ensure ML turns lights off when manually turned on

[toy4rick]

Hello all

I have a ML Rule to turn on the master bathroom light with motion and when Lux < X, then off with no motion, works fine

There are times where the light level is enough to not turn on the light yet I want the bathroom light on... so I manually turn on the light and go full brightness.

The ML app won't turn off the light as written if I manually turn on the light

Is there a workaround for this?

[bertabcd1234]

I don't see anything in your configuration that should prevent that; the lux restriction is only for the "on" half of the automation. As long as the hub isn't in sleep mode and motion was actually generated on the motion sensor, it looks like that should work (or maybe there's one of the multitude of Motion Lighing options I also don't understand...). Have you started by verifying that both of those were the case?

I've also seen people claim that setting they originally set and then changed to something else (e.g., disabling that option but not removing the values from the UI inputs before doing that) were still being obeyed. I haven't tested this or seen it confirmed as a bug by staff, but if you think that might apply to you, re-creating this automation from scratch and choosing only the desired options (or going back and re-selecting those options and removing any inputs that might get hidden when those options are no longer selected, probably) would be another thing you could try--though I'm not sure it will help. Just speculation here.

[toy4rick]

Hello

I have confirmed not in sleep mode and motion is working very reliably

Recreated the ML Rule this morning and will see how it goes

[toy4rick]

@bravenel

I rebuilt the rule, same results, the light will not go off after motion stops when it was originally turned on by the switch

It's a Z-Wave Plus dimmer, guessing it's a GE, however I can't be sure ATM

What am I missing?