Looks like this condition at the beginning of Detector.collisions is preventing static-on-sleeping collisions from being recognized:

I changed that to the following:

-  if ((bodyA.isStatic || bodyA.isSleeping) && (bodyB.isStatic || bodyB.isSleeping))
+  if ((bodyA.isSleeping && bodyB.isSleeping) || (bodyA.isStatic && bodyB.isStatic))

and that was enough to allow collision events to fire between a programmatically-moved static body and a dynamic sleeping body, though it doesn't wake the sleeping body (but at that point it's easy to wake it in the collision event). It didn't seem to cause any spurious events if a body comes to rest against, say, a static floor and falls asleep, though I didn't test much more thoroughly. Happy to submit a PR if this is a desirable fix!

Hey @liabru, I proposed (what I think is) a relatively non-disruptive solution to this issue in #877 -- any chance you could give feedback on that?

Is there a final solution to this problem？

Recently I developed a project with creating multiple bodies, they are not static. And after each few seconds there will be a new body(isStatic) was manipulated to hit those non-static bodies, you know, like a snooker game.

But because I created a lot of bodies and they keep colliding each others，so I was thinking to improve performance by using enableSleeping, then I have the same problem that when a new body start to hit those sleeping bodies，it just stoped and overlapped on them. It seems that setting different collision filter on them.

how can i solve this problem?