Just out of curiosity, is that a wall switch? Individual bulb? Or Light group? (If it's a group, you might have the work around of turning off optimization for the group. I know I have had some issues with group optimization on even the prior builds due to a few switches that talk directly to the bulbs and do not update the hub on changed status. )
It's a light switch. Seems to happen randomly to various light switches around the house. Fix is to simply switch it on and off again either via dashboard or physically. Doesn't happen often, but when it happens you're standing in darkness waving your arms about in a desperate attempt to switch the lights on! LOL
Feels similar to using smartthings again.... hahaha
One more clue as to where the problem lies....
I noticed that the Alexa skill similarly is unable to control the same lights when the fault occurs. Dashboard or RM has no issues.
Alexa skill and motion lighting share a similar way of optimising switch state?
Does this platform issue explain why I've had trouble using the Zone Motion Controller w/the Motion Lighting app in 2.2.4? I get no response w/montion zones created with Zone Motion Controller app, but using the same motion sensors normally in the app works.
This problem seems to have disappeared, at least for now. @gopher.ny are you able to confirm which release this bug was addressed in? If so I will start reverting back to using the motion app for lighting automations rather than RM.
Yes, I've been installing the latest builds as soon as they are available. I just experienced this same issue this afternoon where the he motion lighting logs said it thought the lights were already on when they weren't. Again temporarily fixed by switching on directly through dashboard.