Jump to content

Nexia DB100Z Doorbell Sensor


sampas

Recommended Posts

I have a Nexia DB100Z hooked up to my doorbell chime. The device is linked, and when it senses current, it sends an event. (Log below)

 

However, the only option I have for the two devices is if it's responding (or battery status is x% on the battery one.) There's no alarm option, and even though I have it set to send an email when it responds, nothing happens. (Test emails work, though)

 

Do I need to wait until this particular device is supported? All I want to do is alert on a doorbell press. (For now)

 

Thu 08/04/2016 10:44:10 PM : [ZWAVE-RX ZW006_1] [0110000400060A71]...
Thu 08/04/2016 10:44:10 PM : [ZWAVE-TX        ] ACK
Thu 08/04/2016 10:44:10 PM : [D2D EVENT   ] Event [ZW006_181] [ALARM] [1] uom=93 prec=0
Thu 08/04/2016 10:44:10 PM : [   ZW006_181]    ALARM   1 (uom=93 prec=0)
Thu 08/04/2016 10:44:11 PM : [ZWAVE-RX ZW006_1] [0110000400060A71]...
Thu 08/04/2016 10:44:11 PM : [ZWAVE-TX        ] ACK
Thu 08/04/2016 10:44:11 PM : [D2D EVENT   ] Event [ZW006_181] [ALARM] [0] uom=93 prec=0
Thu 08/04/2016 10:44:11 PM : [   ZW006_181]    ALARM   0 (uom=93 prec=0)
Thu 08/04/2016 10:45:10 PM : [        Time] 22:45:10 0(0)
Thu 08/04/2016 10:45:10 PM : [D2D-CMP 0013] INI [ZW006_1] ERR op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true
Thu 08/04/2016 10:45:10 PM : [        Time] 22:45:10 0(0)
Link to comment
Share on other sites

Hi Sampas,

 

Its possible one of the command classes in the device is not yet supported in ISY.  Can you please post the Z-Wave node details by doing the following:

 

- Open event viewer

- right+click on node  Z-Wave -> Show Information in Event Viewer -> Node Details

 

Thanks

Link to comment
Share on other sites

Do you mean the below?

 

When I go here:  Z-Wave -> Show Information in Event Viewer -> Node Details, it thinks, but nothing comes up. If I go to 

Tools -> Diagnostics -> Event Viewer, I can get the below.

 

Thanks,

Larry

 

 

Fri 08/05/2016 03:19:25 PM : [ZW-SHOW         ] ----------------------------------------------
Fri 08/05/2016 03:19:36 PM : [ZWAVE-NODE-SYNC] ---- Start Processing Z-Wave Node 6 (0x06) ---- 
Fri 08/05/2016 03:19:51 PM : [ZWAVE-NODE-SYNC] Cannot get info from existing Z-Wave Node 6 (0x06), not sync'ed
Fri 08/05/2016 03:19:51 PM : [ZWAVE-NODE-SYNC] -- Finished -- ISY/Z-Wave Node Sync --
Fri 08/05/2016 03:19:58 PM : [ZW-SHOW         ] ----------------------------------------------
Fri 08/05/2016 03:19:58 PM : [ZW-SHOW         ] ZW006_1 uid=6 type=4.7.1 mid=376 tid=17474 pid=12592 model=0
Fri 08/05/2016 03:19:58 PM : [ZW-SHOW         ]    -  x5E  V0  ZWAVEPLUS_INFO
Fri 08/05/2016 03:19:58 PM : [ZW-SHOW         ]    -  x86  V0  VERSION
Fri 08/05/2016 03:19:58 PM : [ZW-SHOW         ]    -  x72  V1  MANUFACTURER_SPECIFIC
Fri 08/05/2016 03:19:58 PM : [ZW-SHOW         ]    -  x5A  V0  DEVICE_RESET_LOCALLY
Fri 08/05/2016 03:19:58 PM : [ZW-SHOW         ]    -  x73  V0  POWERLEVEL
Fri 08/05/2016 03:19:58 PM : [ZW-SHOW         ]    -  x80  V0  BATTERY
Fri 08/05/2016 03:19:58 PM : [ZW-SHOW         ]    -  x70  V1  CONFIGURATION
Fri 08/05/2016 03:19:58 PM : [ZW-SHOW         ]    -  x71  V4  NOTIFICATION
Fri 08/05/2016 03:19:58 PM : [ZW-SHOW         ]    -  x85  V2  ASSOCIATION
Fri 08/05/2016 03:19:58 PM : [ZW-SHOW         ]    -  x59  V0  ASSOCIATION_GRP_INFO
Fri 08/05/2016 03:19:58 PM : [ZW-SHOW         ]    -  x84  V2  WAKE_UP
Fri 08/05/2016 03:19:58 PM : [ZW-SHOW         ]    -  x7A  V2  FIRMWARE_UPDATE_MD
Fri 08/05/2016 03:19:58 PM : [ZW-SHOW         ] 
Fri 08/05/2016 03:19:58 PM : [ZW-SHOW         ] ----------------------------------------------
Fri 08/05/2016 03:20:16 PM : [ZWAVE-WAKEUP   6] Query device when awake ZW006_1
Fri 08/05/2016 03:20:22 PM : [ZW-SHOW         ] ----------------------------------------------
Fri 08/05/2016 03:20:22 PM : [ZW-SHOW         ] ZW006_1 uid=6 type=4.7.1 mid=376 tid=17474 pid=12592 model=0
Fri 08/05/2016 03:20:22 PM : [ZW-SHOW         ]    -  x5E  V0  ZWAVEPLUS_INFO
Fri 08/05/2016 03:20:22 PM : [ZW-SHOW         ]    -  x86  V0  VERSION
Fri 08/05/2016 03:20:22 PM : [ZW-SHOW         ]    -  x72  V1  MANUFACTURER_SPECIFIC
Fri 08/05/2016 03:20:22 PM : [ZW-SHOW         ]    -  x5A  V0  DEVICE_RESET_LOCALLY
Fri 08/05/2016 03:20:22 PM : [ZW-SHOW         ]    -  x73  V0  POWERLEVEL
Fri 08/05/2016 03:20:22 PM : [ZW-SHOW         ]    -  x80  V0  BATTERY
Fri 08/05/2016 03:20:22 PM : [ZW-SHOW         ]    -  x70  V1  CONFIGURATION
Fri 08/05/2016 03:20:22 PM : [ZW-SHOW         ]    -  x71  V4  NOTIFICATION
Fri 08/05/2016 03:20:22 PM : [ZW-SHOW         ]    -  x85  V2  ASSOCIATION
Fri 08/05/2016 03:20:22 PM : [ZW-SHOW         ]    -  x59  V0  ASSOCIATION_GRP_INFO
Fri 08/05/2016 03:20:22 PM : [ZW-SHOW         ]    -  x84  V2  WAKE_UP
Fri 08/05/2016 03:20:22 PM : [ZW-SHOW         ]    -  x7A  V2  FIRMWARE_UPDATE_MD
Fri 08/05/2016 03:20:22 PM : [ZW-SHOW         ] 
Fri 08/05/2016 03:20:22 PM : [ZW-SHOW         ] ----------------------------------------------
Link to comment
Share on other sites

Thanks Larry,

 

It looks like we support the command classes that affect your alarm conditions, what version of the ISY firmware are you running?

 

If you are running one of the 5.0.X ISY Firmware versions, please do the folliowing from a browser and post the output:

 

     http:///rest/zwave/node/ZW006_1/def/get

 

The output should be similar to the following format (the following example output is from a thermostat)t:

 

 id="UZW0003" nls="140">
 id="ST" editor="_17_0"/>
 id="CLISPH" editor="_17_0_R_0_120"/>
 id="CLISPC" editor="_17_0_R_0_120"/>
 id="CLIMD" editor="_67_0_S_001F"/>
 id="CLIFS" editor="_68_0_S_0003"/>
 id="CLIFSO" editor="_81_0_R_0_1"/>
 id="CLIFRS" editor="_80_0_S_01FF"/>
 id="CLIHCS" editor="_66_0_S_0FFF"/>
 id="ERR" editor="ZW_ERR" hide="T"/>
 id="CLISPH">

 id=""

 editor="_17_0_R_0_120" init="CLISPH"/>
 id="CLISPC">

 id=""

 editor="_17_0_R_0_120" init="CLISPC"/>
 id="CLIMD">

 id=""

 editor="_67_0_S_001F" init="CLIMD"/>
 id="CLIFS">

 id=""

 editor="_68_0_S_0003" init="CLIFS"/>
 id="QUERY"/>
 id="SETTIME"/>
 id="CONFIG">

 id="NUM"

 editor="_107_0_R_0_255"/>

 id="VAL"

 editor="ZW_CONFIG"/>
Link to comment
Share on other sites

 

Thanks Larry,

 

It looks like we support the command classes that affect your alarm conditions, what version of the ISY firmware are you running?

 

If you are running one of the 5.0.X ISY Firmware versions, please do the folliowing from a browser and post the output:

 

     http://<your_isy>/rest/zwave/node/ZW006_1/def/get

 

...

 

Oooh!!  Is there a similar URL to fetch that same information for Node Server nodes?  (I've been experimenting but haven't found such a thing yet...)

Link to comment
Share on other sites

Oooh!!  Is there a similar URL to fetch that same information for Node Server nodes?  (I've been experimenting but haven't found such a thing yet...)

 

Hi mwester,

 

The Z-Wave implementation uses dynamically created node definitions, but node servers are still limited to pre-defined node definitions stored in files.  We don't currently have an API for downloading individual node definitions for node servers, but you can access the files containing all of them using the current node server APIs.

Link to comment
Share on other sites

So I was on 4.5.1 and tried upgrading to 5.0.2. Now my user/pass doesn't work, and neither does the default, so I'm locked out. (Tried both java applet after clearing the cache and telnet to the IP address.)

 

Also, factory reset didn't work, either. I'm still locked out.

 

Larry

Link to comment
Share on other sites

So I have Insteon devices, but no z-wave devices any more, nor can the z-wave dongle communicate with any z-wave devices. It doesn't seem to hear any new z-wave devices, either.

 

Hi Larry,

 

I wasn't going to suggest you move right away from the 4.5.x version to 5.0.x, I was just asking if you were running 5.0.x.

 

First thing to try is to restart the ISY by turning off the power for a few seconds (this is important).

 

If you do not see any of your Z-Wave nodes then from the top menu in the Admin Console try

 

     Z-Wave -> Tools -> Synchronize Nodes -> All

 

If your Z-Wave nodes still exist in the Z-Wave dongle then they will start to appear in the ISY device tree.  If after doing this you still have no nodes, you will likely have to reinstall your Z-Wave devices.  Hopefully you don't have to reinstall them, but if you do:

  1) Factory reset the Z-Wave dongle

  2) Exclude you existing devices

  3) Add your devices back again.

Link to comment
Share on other sites

Thanks. I tried another upgrade and another restore. The z-wave is seeing devices again, although they may need to be removed and added. On the other hand, my PLM has disappeared, along with the programs, which I assume are in the PLM.

 

I'll try re-setting the PLM when I'm back on site tonight.

Link to comment
Share on other sites

PLM and z-wave dongle recovered, all insteon devices were there. I had to add a few z-wave devices back, but it was relatively painless.

 

However, when I go to http://10.x.x.x/rest/zwave/node/ZW006_1/def/get it returns this:

<RestResponse succeeded="false">
<status>404</status>
</RestResponse>
 
As do all the other devices I've tried with that REST pattern.
 
Is there someting else I need to do to get the device to sync with the REST?
Link to comment
Share on other sites

 

PLM and z-wave dongle recovered, all insteon devices were there. I had to add a few z-wave devices back, but it was relatively painless.

 

However, when I go to http://10.x.x.x/rest/zwave/node/ZW006_1/def/get it returns this:

404
 
As do all the other devices I've tried with that REST pattern.
 
Is there someting else I need to do to get the device to sync with the REST?

 

 

Hi Larry,

 

Ok, I think you must be running version 5.0.2.   In version 5.0.4 we moved Z-Wave to the new framework (i.e. allowing variables to used as command parameters in programs etc.), and that is where that new URL was first implemented.

Link to comment
Share on other sites

So I'm on 5.0.4 now, and getting the z-wave devices removed and re-added. (Most of my relays are still insteon.)

 

However, when I run the admin java applet (5.0.4), it often says z-wave dongle not responding. I "fixed" it by doing an upgrade firmware (4.55), but now it's doing it again. I can still get a z-wave alert by triggering the one z-wave motion sensor I've re-added, and I can see that event in the logs. Re-removing and re-adding all the z-wave devices is getting tiring. Is there a way to get the isy to recognize the z-wave dongle without upgrade/reset? I've tried rebooting, and powering down for a couple of minutes.

 

In the meantime, here's the XML from the motion sensor. I'll add the doorbell if I can get z-wave dongle control back.

 

<nodeDefs>
<nodedef id="UZW0002" nls="104">
<sts>
<st id="ST" editor="_78_0"/>
<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>
</accepts>
</cmds>
</nodedef>
</nodeDefs>
Link to comment
Share on other sites

I upgraded the z-wave dongle firmware, and got the admin panel contro for z-wavel back. The doorbell sensor is back after a remove/re-add. However, for program options, the only options I have for status are battery level and online. I also did a z-wave normal backup to see if that helps the next time I need to re-firmware-update the dongle.

 

Also, if I leave off the /def/get, I get this:

<RestResponse succeeded="false">
<status>404</status>
</RestResponse>
 
With /def/get, I get the below:

 

<nodeDefs>
<nodedef id="UZW0002" 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>
</accepts>
</cmds>
</nodedef>
</nodeDefs>
Link to comment
Share on other sites

Hi Larry,

 

I just went through our code again and I see a bug where some alarms will not appear in programs, but in your case it may still work.

 

1) Open & clear the event viewer in Admin Console

2) Ring the doorbell and look for an "DON" or "ALARM" event to appear in the event viewer

3) Copy the contents of the event viewer (to post on the forum)

4) Close the Admin Console and start it again

5) From your browser, do http:///rest/zwave/node/ZW006_1/def/get

6) Post the output from the event viewer and the /def/get on the forum

 

If the event was a "DON", in most cases you should now see the alarm available as a control condition and a status condition in programs.

Link to comment
Share on other sites

Here's the ring event. I had to re-updated the zwave firmware in the admin panel. Then I restored from yesterday's backup. Do I need to remove it and add it again to get the node found?

 

Thu 08/11/2016 20:16:33 : [        Time] 20:16:35 1(0)
Thu 08/11/2016 20:16:47 : [ZWAVE-RX ZW002_1] [0110000400020A71]...
Thu 08/11/2016 20:16:47 : [ZWAVE-TX        ] ACK
Thu 08/11/2016 20:16:47 : processUpdate: node not found nt=181 valType=304 uom=93 val=1, event ignored
Thu 08/11/2016 20:16:48 : [ZWAVE-RX ZW002_1] [0110000400020A71]...
Thu 08/11/2016 20:16:48 : [ZWAVE-TX        ] ACK
Thu 08/11/2016 20:16:48 : processUpdate: node not found nt=181 valType=304 uom=93 val=0, event ignored
Thu 08/11/2016 20:19:32 : [        Time] 20:19:34 1(0)
Thu 08/11/2016 20:29:33 : [        Time] 20:29:33 1(0)
 
As soon as I close the admin panel and open it again, it says z-wave dongle not responding. Is there a way to get it back without re-updating the firmware?
 
Thanks,
Larry
Link to comment
Share on other sites

When you update the zwave firmware, you'll have to remove and re-enroll all devices, unless you shifted primary to another controller first (and can therefore shift primary back afterwards).

Link to comment
Share on other sites

As soon as I close the admin panel and open it again, it says z-wave dongle not responding. Is there a way to get it back without re-updating the firmware?

 
Thanks,
Larry

 

 

Hi Larry,

 

You should almost never have to update the Z-Wave firmware, or even factory reset the Z-Wave dongle.

 

If you see "Z-Wave dongle not responding", just wait a 30 seconds or so and check the menu again.  When you restart the ISY is takes about a minute or so for the Z-Wave module to brought online in the ISY.

 

Unfortunately, when you upgrade the Z-Wave firmware you lose your Z-Wave network unless you shifted primary to another controller first, but I don't think you did that.  Therefore, you will have to exclude and include your Z-Wave devices again.

 

>> Thu 08/11/2016 20:16:47 : processUpdate: node not found nt=181 valType=304 uom=93 val=1, event ignored

 

This indicates that we got the event, but the code did not create a node/status value for it.  This is a bug, very sorry for the inconvenience, but you won't be able to detect doorbell rings in programs with your device until we fix it.

Link to comment
Share on other sites

I understand I need to remove and re-enroll all devices. What I don't understand is how to re-enroll the zwave dongle itself. Each time I open the admin panel, it says "Z-wave dongle not responding."

 

Is there a way to poke the isy by logging in and doing something?

Link to comment
Share on other sites

  • 4 weeks later...

I recently picked one of these sensors and I did get it working with my ISY firmware 4.5.1.

 

When first enrolling, it will only appear as a "Notify Sensor" and only gives a battery level. After installing and ringing the bell, a new node called "Power Management" will appear. Then, I could create a program that used the "Power Applied" control condition as the if statement.

 

One other gotcha is the sensor won't register a Power Applied status unless the voltage is 14VAC or greater. This is noted on the install sheet, but it tripped me up until I read it. After installing, sometimes I would see an event, but most of the time I wouldn't. Only after giving my doorbell a good hard press would the sensor register. With a quick press, I could only measure 9 VAC with my multimeter. I guess I need to swap in a more powerful VAC transformer.

Link to comment
Share on other sites

  • 1 year later...

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...