Nexia DB100Z Doorbell Sensor - Does not work in 5.x

[lion]

I have a Nexia DBZ100Z Doorbell Sensor ... it worked well under 4.x, but after the upgrade to 5.x, it no longer has the features I used in 4.x to trigger events. 

In 4.x, it had items for power monitoring, like "Over voltage" or something similar (I don't know, since I don't have 4.x installed anymore)  There was a number of them and they were all power related.  These events could be used in programs as If conditions, to which I used it to kick off Thens.  These were under a Power Management device.

In 5.x, there are 3 devices (a Notification Sensor, an Energy Meter, and Power Management).  The selections in Programs no longer have the power management options that can used used .. all I can cue off of are Status-> Responding, Battery Level, and number of watts.  None of these change when the device is triggered.

Can anyone help?

(Manual Attached)

Thanks!

Doorbell-Sensor-Installation-Guide.pdf

[Michel Kohanim]

@lion,

I am so very sorry to hear. We'll take a look and get back to you. In the meantime, have you tried exclude/include?

With kind regards,
Michel

[lion]

Yes, I excluded/included as part of the 5.x upgrade.

[Chris Jahn]

Hi Lion,

Can you please do the following and post the results:

1) In Admin Console, right+click on the device and select Z-Wave -> Show Information in Event Viewer -> Node Details

2) For each of the 3 nodes from a web browser:      http://<yourIsy>/rest/zwave/node/<isyNodeAddress>/def/get

     e.g.  http://192.168.0.11/rest/zwave/node/ZW023_1/def/get

Thanks

[lion]

1) Attached are screenshot since I can't cut-n-paste out of the log.

2)

/rest/zwave/node/ZW051_1/def/get

<nodeDefs><nodedef id="UZW0040" nls="185"><sts><st id="BATLVL" editor="_51_0_R_0_100"/><st id="ERR" editor="ZW_ERR" hide="T"/></sts><cmds><sends/><accepts><cmd id="QUERY"/><cmd id="WAKEOPTS"><p id="INTERVAL" editor="ZW_WAKE_INTERVAL"/></cmd><cmd id="CONFIG"><p id="NUM" editor="_107_0_R_0_255"/><p id="VAL" editor="ZW_CONFIG"/></cmd><cmd id="WDU"/></accepts></cmds><links><ctl/><rsp><link linkdef="ASSOC_MC"/><link linkdef="ASSOC_CMD"/><link linkdef="ASSOC"/></rsp></links></nodedef></nodeDefs>

/rest/zwave/node/ZW051_143/def/get

<nodeDefs><nodedef id="UZW0063" nls="143"><sts><st id="ST" editor="_73_3"/></sts><cmds><sends/><accepts><cmd id="QUERY"/></accepts></cmds><links><ctl/><rsp><link linkdef="ASSOC_MC"/><link linkdef="ASSOC_CMD"/><link linkdef="ASSOC"/></rsp></links></nodedef></nodeDefs>

/rest/zwave/node/ZW051_181/def/get

<nodeDefs><nodedef id="UZW0064" nls="181"><sts/><cmds><sends/><accepts><cmd id="QUERY"/></accepts></cmds><links><ctl/><rsp><link linkdef="ASSOC_MC"/><link linkdef="ASSOC_CMD"/><link linkdef="ASSOC"/></rsp></links></nodedef></nodeDefs>

 

Sorry for the XML spam.

 

Thanks!

[Chris Jahn]

Thanks Lion,

It looks like either this device doesn't report its Notification capabilities correctly, or the query attempting to get them failed.  Can you please try querying the device again with the Admin Console Event Viewer at level 3 and sending me the output (DM would be fine).

[lion]

dm sent with data

[lion]

Any update?  Requested data has been sent.

[Chris Jahn]

Hi Lion,

Thanks, I received the DM a few days ago.  Based on that output, we are still trying to determine if the device is sending the wrong information or if we are interpreting it incorrectly.

[lion]

Great, thanks.  I seem to remember the way I used the device was with some kind of alarm event ... if I'm interpreting it right.