How long does it normally take for someone to respond to "Investigate Issue"?

[nmpu]

I reported a broken configuration on December 2. It's hard to believe this device configuration was ever tested. It appears to be listening for motion on the wrong endpoint. I know how to create a custom config file, but this problem occurs at a lower level. I'm willing to pursue the fix, but I need to know where to look.

[kpine]

Posting again #6521

[kpine]

It's hard to believe this device configuration was ever tested.

Keep in mind that there are thousands of Z-Wave devices on the market, and there are a couple thousand in the Z-Wave JS database.
In addition, some devices are only sold in certain regions, e.g. your Jasco devices are only in the US, while the maintainer of this project is in the EU, so obtaining and testing US devices is harder (feel free to donate devices!). So yes, some devices and their device files are likely to be completely unvalidated in the real world. Often they are often just imported from other sources (OZW, OpenHAB, ZWA DB).

So realistically, you cannot expect the maintainer of this project to test all Z-Wave devices in all regions. Luckily Z-Wave certification makes a lot of that unnecessary, but there are some edge cases to workaround, such as endpoints.

[AlCalzone]

You might want to use Z-Wave JS UI for that, which let's you access the config files and test custom ones.

[nmpu]

Thanks for stopping by! I've reviewed the documentation and already have some custom config files. However, I don't see a way to change the endpoint used for motion detection. That's got to be buried somewhere lower?

[AlCalzone]

You'll likely need to use the preserveEndpoints or preserveRootApplicationCCValueIDs compat flags, maybe mapRootReportsToEndpoint. Which one it is really depends on the behavior of the device and I'll have to look at the logs to verify.
https://zwave-js.github.io/node-zwave-js/#/config-files/file-format?id=compat

[nmpu]

Z-Wave JS UI shows the motion updates coming in for endpoint 1. My other Jasco motion devices use endpoint 2. I don't think this is a case of reports to the root device are silently ignored. I don't think it's a mapping problem at all. It's a listening problem. Once the first motion update arrives, a second _motion_detection entity appears. I can even create an automation trigger. However, that new entity will not exist on restart and the associated automation will be disabled. I need more than the existing compat flags to solve this problem. It's probably yet another poorly-behaved Jasco product that passed "certification".

[AlCalzone]

Do you have a driver log capturing an interview plus this report?

[nmpu]

The interview and .json are in my original inquiry. I just added sample reports for 24770 (broken) and 26931 (working).

For reference, the date code on the 24770 is 1641. These appear to be Jasco's very first Z-Wave motion switch.

Thanks again.

[AlCalzone]

Continuing in the original discussion