Those should have decent response times unless there’s something going on with the platform.
Let’s start with some details. Has the response time changed since moving to edge? Was it better previously with a groovy DTH? If so, it’s probably a platform issue. It may have to do with how many edge drivers you are using, for example. 
Next, what do you consider non-responsive? Are you using the motion sensors to trigger a light? If so, are you expecting the light to come on in one second? two seconds? what’s the specific response rate you’re looking for?
Third, have you had a chance to look at the FAQ on this issue? You may already know everything there, but there may be something that helps.
FAQ: Where to locate motion sensor for fastest response?
Forth, in most cases, if the motion sensor is designed to be battery powered, it will be less responsive than if it’s designed to be mains powered. Is mains powered an option where you want to use this?
Fifth, as far as the most responsive batterypowered motion sensor, you can configure the Fibaro multisensor for a very quick response time, but doing so will greatly reduce the battery life. So one of those set at the fastest possible response time is an option for some people, but it’s not usually the solution that most people are looking for.