Handling zwave notifications - Need Help

[chris (Chris Jackson)]

@FRamos

I’ve read CC_ALARM (0x71) is deprecated. CC_NOTIFICATION (0x71) is the successor.

You’ll note that both of these are the same - 0x71.

@FRamos

CC_NOTIFICATION_REPORT_V4 (0x05) uses notification type
Instead, the deprecated CC_ALARM (0x71) uses alarm type

The binding uses the appropriate type depending on the version. NOTIFICATION is the same as ALARM - as I mentioned above, they are both the same command class - just the version changes.

@FRamos

My conclusion is that DCH-Z120 should uses CC_NOTIFICATION (0x71) (instead of CC_ALARM)

As above - they are the same, and the binding does process your notifications correctly I think.

@FRamos

So, lets adapt the DB in order to replace CC_ALARM by CC_NOTIFICATION_V4

We can’t have both types in the database since they are the same. It doesn’t matter what we call it - ALARM, NOTIFICATION, ALARM_NOTIFICATION, or anything else - this is simply a human readable name. What matters is the class number (0x71). ZWave ensures backward comparability with these classes.

@FRamos

replace alarmType_BURGLAR by alarmType_HOME_SECURITY

Again, this is just a name - it doesn’t matter to the operation of the protocol. For historical reasons the binding uses names that aren’t 100% consistent with the standard since the standard was only released recently, but it’s only the human readable name - it still processes the data exactly the same.

@FRamos

for event 3 on both DCH-Z110 and DCH-Z120 and events 7 and 8

As I’ve said a earlier in this thread, this is configured in the database. Simply setting the filter in the configuration will make the binding react to the correct events - so long as you are using a recent snapshot of the binding and not the released version.

The following configuration is used for the door open event -:

type=ACCESS_CONTROL, event=22

The following configuration is used for the motion event -:

type=BURGLAR, event=8

Note that the event could also be 7 - depending on the device.

The following configuration is used for the tamper event -:

type=BURGLAR, event=3

Note that the event could also be 4 - depending on the device.

I hope this helps explain this further. I’ve added some of this to the database already but I would strongly urge you to try and do it yourself. I know you said you weren’t confident to change the database, but you clearly have an understanding of things here, and you at least should be able to copy from other entries in the database, or just copy in what I’ve said earlier in post 7 of this thread.

If you’re really stuck, then let me know and I’ll do the changes, but it would be really appreciated if you can try yourself - with around 420 devices in the database, it would be a full time job for me to keep up with everyones requests (which is why I wrote the online database editor - to make it easier for people than having to edit XML files and manage this in Git).

Thanks.
Chris