Zwave JS - How to contribute information about devices not working correctly?

I have a “DCH-Z120 by D-Link Firmware: 1.18” that is a motion/temperature/Illumination sensor.

It is detected and setup completely. It reports temperature and Illumination, but the motion is not reported.

Looking at zwave js log I see the following:
Received a command that contains multiple CommandClasses. This is not supported yet! Discarding the message...

I assume this is the motion detection failing ? How can I contribute information so it’s detected correctly ?

EDIT:
I actually found out that the motion detection was working. There was actually 2 motion detection entities and the one that was working was disabled by default.

I saw the same thing. Some devices show up with a few entities, but the important ones (like a binary sensor for a motion detector) is sometimes disabled by default for some reason. Or some have two binary sensors, but the hidden one is the one that actually works.

1 Like

I am attempting to move from OpenZWave to Zwave JS. I have managed to get one device in a state that looks OK. I have several DCH-Z110 and a DCH-Z510, none of these work and do eventually give similar messages to yours.

I am concentrating on the DCH-Z510 as this is a mains powered device and so reports more easily. What I have when I start the addon:

23:20:25.407 CNTRLR   [Node 002] Beginning interview - last completed stage: RestartFromCache
23:20:25.410 CNTRLR » [Node 002] pinging the node...
23:20:25.447 CNTRLR   [Node 003] Beginning interview - last completed stage: ProtocolInfo
23:20:25.450 CNTRLR » [Node 003] querying node info...
23:20:25.730 CNTRLR   [Node 002] The node is alive.
23:20:25.733 CNTRLR   [Node 002] The node is ready to be used
23:20:25.734 CNTRLR « [Node 002] ping successful
23:20:25.741 CNTRLR   [Node 002] ManufacturerSpecificCC: doing a partial interview...
23:20:25.744 CNTRLR   [Node 002] VersionCC: doing a partial interview...
23:20:25.751 CNTRLR   [Node 002] AssociationGroupInfoCC: doing a partial interview...
23:20:25.758 CNTRLR   [Node 002] ZWavePlusCC: doing a partial interview...
23:20:25.764 CNTRLR   [Node 002] BinarySwitchCC: doing a partial interview...
23:20:25.766 CNTRLR » [Node 002] querying Binary Switch state...
23:20:43.854 CNTRLR   [Node 002] Timed out while waiting for a response from the node
23:20:43.955 CNTRLR   [Node 002] Interview stage completed: CommandClasses
23:20:43.958 CNTRLR   [Node 002] Interview stage completed: OverwriteConfig
23:20:43.959 CNTRLR » [Node 002] requesting node neighbors...
23:20:44.337 CNTRLR « [Node 002]   node neighbors received: 1, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 
                      15, 16
23:20:44.338 CNTRLR   [Node 002] Interview stage completed: Neighbors
23:20:44.339 CNTRLR   [Node 002] Interview completed

I hope this helps you with your issue. I have no evidence that our issues are the same at present nor do I have a fix for my problems I just thought that the extra information may help.

Just to let you know this is not an issue with D-Link sensors either. I am seeing this on all my other sensors, Aeotec and Heiman in the main. The only one that is working is my Aeotec Doorbell.

I got mine working, check the edit in first post. Maybe you have same issue ?

Thanks but no. After 24 hours still only one additional entity available, all the devices are there but none have even a manufacturer available as the interview is not complete. I am still trying to find out what I am doing wrong, everything works like a dream on OpenZwave. But waiting for a while before I post anything as it has to be something I am going, most devices are on the supported list.

So after updating to 0.1.13 and 2021.3.4 - bad things start to happen.

Motion status is not updating stable, sometimes no detection, sometimes stuck in detected never turning off.