I have a Dome motion sensor (DMMS1 Dome Z-Wave Plus Motion Detector) that sends an alarm report but does not successfully process the alarm_burglar channel. Here is the debug log view for a motion event and a two-minute motion timeout:
You can see that the alarm_burglar channel is not handled for the motion detect ALARM_REPORT at 21:13:29, but is handled for the motion end ALARM_REPORT at 21:15:30. Any idea why the motion detect is not setting alarm_burglar to ON?
Which version of OH (and the zwave binding, if different) are you using? Also, it helps a lot to include logs in code fences, and to include a link to the device database entry.
Please can you also provide logs as they are logged. It looks like you are filtering the data and processing in some way which makes it hard for me to use.
I used your ZWave Log Viewer and filtered on the motion detector node. Do you want the raw log entries or just the ZWave Log Viewer without the filtering?
Ah - ok, I’ve not seen that done like that before (ie pasting in the text).
It’s normally best to provide the raw logs - the log viewer shows what is happening at the ZWave level, but the raw logs also show what the binding is doing - both are really needed to understand what is happening…
However, that said, now that I know what this log is, I know what to look for, and I can see that the database does not have the motion channel added for the ALARM command class so I will add that now.
Thank you for the quick response! Once you’ve updated the database, is there an easy way to provide the XML through an override or would I need an updated JAR file?
In general, it’s easiest to update the JAR. In theory, you can export the XML from the database and update your current JAR, but personally I would not recommend this although @5iver has written a tutorial on this if you prefer -: