You can pair using the test version, but the parameters for this device (4150) are completely different than the parameters it will be using. The developer added 4150 to PIR v2, but those parameters are different
“productTypeId”: [3, 512],
“productId”: [4145, 4150],
so, about the delay. My supplier just confirmed to me that the delay is due to hardware problems and can not be fixed. The delay is due to them having changed to what he calls the zwave 500series chipset. He also said they will updating to what he calls the zwave 700series chipset which should not have the delay.
Unfortunately we refuses to send me replacement devices that do actualle work
I also have a delay of about 10 seconds with some newly bought sensors. All the other sensors I have are instantly responding, is there already a fix for this?
I have made an updated driver specific for the 4150-version so you can actually change the advanced settings and minimize the delay, but a delay is inevitable. This driver works quite well with the 4150-version. The updated driver can be found as an pull request with the source code but i can’t update the app.
On the downside, after a few months having this PIR working, the comunication with Homey is so bad that I’m going to remove this device. For me it’s simply not reliable.
I’ve upgraded the Homey z-wave antenna with an external antenna (see homey modifications). Now it’s working perfect. Also tweaked the driver further to also report on humidity (undocumented feature of this sensor). Works fine.
