Zwave Door windo senser MP HKZW-DWS01

orc_trial · October 14, 2019, 10:03pm

Hi,

i have a new door sensor as described in the link below.

https://downloads.monoprice.com/files/manuals/24259_Manual_170612.pdf

I have it securely associated with the controller (running Zwave ver 3.3.0). I have attached the zwave logs and the node file for more information.

Everything looks like it has completed the association. I am also seeing the battery value come in so looks like the sensor is communicating with the controller.

However i am not seeing any status change (open / close) when i move the magnet away from / close to the sensor. The led is blinking indicating it is send the messages. No errors seen in the log.

I am using standard “Status” command.

I have a custom sensor and a switch senor using this command just to see what values it is sending. Both of them stay at “N/A” on the panel.

any ideas what could be wrong?

I am noticing in the user manual something about multiple groups which i have not seen before

In the node file do i need to manually add the association information for Group 2 like it is pointing to node 1 for Group 1?

1

Thanks in advance.

node 53 Z wave log.txt (182 KB)

Node 53 config.txt (4.11 KB)

orc_trial · October 19, 2019, 1:32am

I tried excluding the node and including it without security. I have attached all the log entries below. It appears that it is using COMMAND_CLASS_ALARM::ALARM_REPORT with ‘EVENT_DOOR_WINDOW_OPEN’ and ‘EVENT_DOOR_WINDOW_CLOSE’

I am guessing it is using ALARM_TYPE_ACCESS_CONTROL

is this supported in zwave 3.3.0 version of openremote? if yes what command should i use in openramote?

Currently i am using “status” when building command in the designer

node file shows:

ALARM_TYPE_ACCESS_CONTROL

ALARM_TYPE_HOME_SECURITY

i also looked at the manual and it states the following:

Parameter 14 Enable/Disable BASIC SET Command

The sensor can send the BASIC SET command to nodes associated with group 2.

0 = Disable

1 = Enable

Parameter Size: 1 byte

Default Setting: 0

Parameter 15 Value of the BASIC SET

The BASIC SET value sent by the sensor when the magnet is triggered can be reversed

from its default state.

0 = Sends the BASIC SET VALUE 255 to nodes associated with group 2 when the

door/window is opened and sends the BASIC SET VALUE 0 to nodes associated

with group 2 when the door/window is closed.

1 = Sends the BASIC SET VALUE 0 to nodes associated with group 2 when the

door/window is opened and sends the BASIC SET VALUE 255 to nodes

associated with group 2 when the door/window is closed.

Parameter Size: 1 byte

Default Setting: 0

if i want to use the basic set, how do i change the parameter 14 from 0 to 1?

DEBUG 2019-10-18
19:46:14,337 (Z-Wave): RX_Session_Layer : Node ‘54’ :
[APP_CMD_HANDLER_FRAME : NodeID=‘54’, Status=[RECEIVE_STATUS_TYPE_SINGLE],
CommandClass=‘COMMAND_CLASS_ALARM’, Command=‘0x05’, Parameters: [0x00, 0x00,
0x00, 0xFF, 0x06, 0x16, 0x00, 0x00]]

DEBUG 2019-10-18 19:46:14,338 (Z-Wave):
CCAlarmV2 : Node
‘54:0’ : [COMMAND_CLASS_ALARM::ALARM_REPORT, AlarmTypeV1=[Dec:‘0’
Hex:‘0x00’], AlarmLevelV1=[Dec:‘0’ Hex:‘0x00’], AlarmStatus=‘UNSOLICITED_ALARMS_ENABLED’,
AlarmType=[‘ALARM_TYPE_ACCESS_CONTROL’, Dec:‘6’, Hex:‘0x06’],
EventType=[‘EVENT_DOOR_WINDOW_OPEN’, Dec:‘22’, Hex: ‘0x16’]].

DEBUG 2019-10-18 19:46:15,239 (Z-Wave):
RX_Session_Layer : Node ‘54’
: [APP_CMD_HANDLER_FRAME : NodeID=‘54’, Status=[RECEIVE_STATUS_TYPE_SINGLE],
CommandClass=‘COMMAND_CLASS_BATTERY’, Command=‘0x03’, Parameters: [0x64]]

DEBUG 2019-10-18 19:46:15,239 (Z-Wave):
CCBattery : Node
‘54:0’ : [COMMAND_CLASS_BATTERY::BATTERY_REPORT, BatteryLevel=‘100’].

DEBUG 2019-10-18 19:46:19,189 (Z-Wave):
RX_Session_Layer : Node ‘54’
: [APP_CMD_HANDLER_FRAME : NodeID=‘54’, Status=[RECEIVE_STATUS_TYPE_SINGLE],
CommandClass=‘COMMAND_CLASS_ALARM’, Command=‘0x05’, Parameters: [0x00, 0x00,
0x00, 0xFF, 0x06, 0x17, 0x00, 0x00]]

DEBUG 2019-10-18 19:46:19,190 (Z-Wave):
CCAlarmV2 : Node
‘54:0’ : [COMMAND_CLASS_ALARM::ALARM_REPORT, AlarmTypeV1=[Dec:‘0’
Hex:‘0x00’], AlarmLevelV1=[Dec:‘0’ Hex:‘0x00’], AlarmStatus=‘UNSOLICITED_ALARMS_ENABLED’,
AlarmType=[‘ALARM_TYPE_ACCESS_CONTROL’, Dec:‘6’, Hex:‘0x06’],
EventType=[‘EVENT_DOOR_WINDOW_CLOSE’, Dec:‘23’, Hex: ‘0x17’]].

DEBUG 2019-10-18 19:46:20,061 (Z-Wave):
RX_Session_Layer : Node ‘54’
: [APP_CMD_HANDLER_FRAME : NodeID=‘54’, Status=[RECEIVE_STATUS_TYPE_SINGLE],
CommandClass=‘COMMAND_CLASS_BATTERY’, Command=‘0x03’, Parameters: [0x64]]

DEBUG 2019-10-18 19:46:20,062 (Z-Wave):
CCBattery : Node
‘54:0’ : [COMMAND_CLASS_BATTERY::BATTERY_REPORT, BatteryLevel=‘100’].

orc_trial · October 19, 2019, 1:59am

this is what shows up in the log when i move the magnet away
DEBUG 2019-10-18 20:53:32,176 (Z-Wave): RX_Session_Layer : Node ‘54’ : [APP_CMD_HANDLER_FRAME : NodeID=‘54’, Status=[RECEIVE_STATUS_TYPE_SINGLE], CommandClass=‘COMMAND_CLASS_ALARM’, Command=‘0x05’, Parameters: [0x00, 0x00, 0x00, 0xFF, 0x06, 0x16, 0x00, 0x00]]

DEBUG 2019-10-18 20:53:32,178 (Z-Wave): CCAlarmV2 : Node ‘54:0’ : [COMMAND_CLASS_ALARM::ALARM_REPORT, AlarmTypeV1=[Dec:‘0’ Hex:‘0x00’], AlarmLevelV1=[Dec:‘0’ Hex:‘0x00’], AlarmStatus=‘UNSOLICITED_ALARMS_ENABLED’, AlarmType=[‘ALARM_TYPE_ACCESS_CONTROL’, Dec:‘6’, Hex:‘0x06’], EventType=[‘EVENT_DOOR_WINDOW_OPEN’, Dec:‘22’, Hex: ‘0x16’]].

when i move the magnet close:

DEBUG 2019-10-18 20:53:47,434 (Z-Wave): RX_Session_Layer : Node ‘54’ : [APP_CMD_HANDLER_FRAME : NodeID=‘54’, Status=[RECEIVE_STATUS_TYPE_SINGLE], CommandClass=‘COMMAND_CLASS_ALARM’, Command=‘0x05’, Parameters: [0x00, 0x00, 0x00, 0xFF, 0x06, 0x17, 0x00, 0x00]]

DEBUG 2019-10-18 20:53:47,436 (Z-Wave): CCAlarmV2 : Node ‘54:0’ : [COMMAND_CLASS_ALARM::ALARM_REPORT, AlarmTypeV1=[Dec:‘0’ Hex:‘0x00’], AlarmLevelV1=[Dec:‘0’ Hex:‘0x00’], AlarmStatus=‘UNSOLICITED_ALARMS_ENABLED’, AlarmType=[‘ALARM_TYPE_ACCESS_CONTROL’, Dec:‘6’, Hex:‘0x06’], EventType=[‘EVENT_DOOR_WINDOW_CLOSE’, Dec:‘23’, Hex: ‘0x17’]].

rainerhitz · October 19, 2019, 12:04pm

Please note that the following information is an undocumented feature of version 3.3.0 because there are issues related to COMMAND_CLASS_ALARM_V1 and COMMAND_CLASS_ALARM_V2 that haven’t been really resolved yet.

In order to detect the open/close status of the sensor create a command with the name ALARM_TYPE_ACCESS_CONTROL and link it with a range sensor (range: 0-100). You should see the values 22 for open and 23 for close.

In order to detect if someone has opened the device create a command with the name ALARM_TYPE_HOME_SECURITY and link it with a switch sensor or range sensor (range: 0-100).

You can also detect the open/close status with the STATUS command but it requires to configure the second association group like you did for the first association group. That means adding node 1 to the second association group. In addition you should configure parameter 14 with the value 1 which as a result enables the BASIC SET command.

orc_trial · October 21, 2019, 4:12am

Thanks Rainer. Those commands are working. I have setup a custom sensor and values 22 and 23 are getting displayed.

With respect to configuring parameter 14 with the value 1, how do I change that value on the sensor from default 0 to 1? Is this done thorough the node file?

I dont see any configuration parameters related to this setting in the node file (attached)

Node 53 config.txt (4.11 KB)

orc_trial · October 21, 2019, 4:33am

I found this syntax in another post. I will give this a try.

  <parameter>
    <number>80</number>
    <value>2</value>
    <size>1</size>
  </parameter>
</parameters>

https://github.com/openremote/Documentation/wiki/Z-Wave#manual-configuration-procedure

orc_trial · October 21, 2019, 2:58pm

Sensor is working now as expected after reconfiguring the association setting and parameter.
node settings

1

14

1