I think I've got a situation that I can document that has unexpected behavior, perhaps similar in nature to those above.
I have 2 motion sensors, 1 and 2, and 2 lights, controlled by 2 ML apps. The 1st app has Sensor 1 controlling Light A. The 2nd app has Sensor 2 controlling Light A and Light B.
These sensors and lights are on either side of a door. I want only 1 light on if sensed from 1 side of the door, but both lights on if sensed from the other side of the door. Frequently both sensors will be active at the same time as one passes through the doorway.
As of now, the rules don't work as expected. If I activate Sensor 1 Light A goes on as expected, If I then activate Sensor 2 after walking through the doorway, Light B does not come on. (Light A stays on, but due to the timing settings of the app controlling the first sensor).
If I look at the "on" variable of the Application State the ML app that uses the 2nd sensor to turn on both lights, I see the "on" state as true even if Sensor 2 has not been activated. If I had to guess, it's because the ML app is checking the state of any subscribed lights (or) instead of all (and) to determine the "on" variable state. Which is not what I would personally expect.