Dome motion sensor ALARM_REPORT not processed successfully

zwave
binding
Tags: #<Tag:0x00007fe056f99000> #<Tag:0x00007fe056f98dd0>

(Tom Lendacky) #1

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:

21:13:29.027	4	RX REQ ApplicationCommandHandler ALARM_REPORT V1 UNKNOWN[00] V1LEVEL=0 HOME_SECURITY EVENT=8 0 /128
01 0F 00 04 00 04 09 71 05 00 00 00 FF 07 08 00 7D
21:13:29.044	4	RX REQ ApplicationCommandHandler SENSOR_BINARY_REPORT::255(12) = #NUM! 0 /128
01 0A 00 04 00 04 04 30 03 FF 0C 31
21:13:29.094	4	RX REQ ApplicationCommandHandler BASIC_SET 1 /128
01 09 00 04 00 04 03 20 01 FF 2B
21:13:29.115	4	STATE UPDATE zwave:device:fd5cfe13:node4:sensor_binary ON [OnOffType]
21:15:30.083	4	RX REQ ApplicationCommandHandler ALARM_REPORT V1 UNKNOWN[00] V1LEVEL=0 HOME_SECURITY EVENT=0 0 /128
01 10 00 04 00 04 0A 71 05 00 00 00 FF 07 00 01 08 60
21:15:30.104	4	RX REQ ApplicationCommandHandler SENSOR_BINARY_REPORT::UNKNOWN(12) = #NUM! 0 /128
01 0A 00 04 00 04 04 30 03 00 0C CE
21:15:30.127	4	STATE UPDATE zwave:device:fd5cfe13:node4:alarm_burglar OFF [OnOffType]
21:15:30.156	4	RX REQ ApplicationCommandHandler BASIC_SET 1 /128
01 09 00 04 00 04 03 20 01 00 D4
21:15:30.164	4	STATE UPDATE zwave:device:fd5cfe13:node4:sensor_binary OFF [OnOffType]

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?

Thanks,
Tom


(Scott Rushworth) #2

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.


(Tom Lendacky) #3

I’m using OH 2.4.0-1 with the included zwave binding. The Dome device link is here.

Sorry about the log format, I’ll be sure to use code fences next time.

Thanks,
Tom


(Chris Jackson) #4

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.


(Tom Lendacky) #5

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?

Thanks,
Tom


(Chris Jackson) #6

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.


(Tom Lendacky) #7

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?

Thanks,
Tom


(Chris Jackson) #8

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 -:


(Tom Lendacky) #9

Ok, followed the tutorial and validated that I’m seeing the alarm motion events now. Thank you very much!

I have another issue with a different device, but I’ll start a new topic on that when i get a chance.

Thanks,
Tom