Page 1 of 2

Nexia Z-Wave Doorbell Sensor, DB100Z

PostPosted: Fri Nov 25, 2016 12:30 pm
by aldera
I'm not showing this as an officially supported Z-Wave device on the Indigo website but was wondering if anyone has this up and running on their Indigo server? If not, what setup or device are people using to detect their door bell? TIA

Re: Nexia Z-Wave Doorbell Sensor, DB100Z

PostPosted: Fri Nov 25, 2016 3:20 pm
by mat
Just finished making this and will mount tomorrow for a doorbell.

Texts all the mobiles and grabs a camera image from the CCTV too.

It;s a Fabaro FGK 10x and uses the binary input - connected to a standard bell push. Push will be located on the front of the door with the Fabaro mounted on the rear.

Re: Nexia Z-Wave Doorbell Sensor, DB100Z

PostPosted: Sat Nov 26, 2016 7:31 pm
by rapamatic
I use a MIMOLite to do basically the same thing. Also gives you a few more I/o options if that's useful. Doesn't run on batteries, which is a plus for me.


Sent from my iPhone using Tapatalk

Re: Nexia Z-Wave Doorbell Sensor, DB100Z

PostPosted: Sat Nov 26, 2016 8:32 pm
by matt (support)
I checked and no one has reported using one to us yet, so I'm not sure if it works. If someone gets one then please copy/paste the Event Log result of a sync and let us know if it works.

Re: Nexia Z-Wave Doorbell Sensor, DB100Z

PostPosted: Sun Nov 27, 2016 4:13 pm
by aldera
rapamatic wrote:
I use a MIMOLite to do basically the same thing. Also gives you a few more I/o options if that's useful. Doesn't run on batteries, which is a plus for me.


Sent from my iPhone using Tapatalk


That would work. I use 2 MIMOLites for my garage doors but they need a power supply. They're great though. I may buy the Nexia and give it a try. Running on battery shouldn't be an issue since it won't get used that often.


Sent from my iPad using Tapatalk

Re: Nexia Z-Wave Doorbell Sensor, DB100Z

PostPosted: Sun Nov 27, 2016 4:14 pm
by aldera
matt (support) wrote:
I checked and no one has reported using one to us yet, so I'm not sure if it works. If someone gets one then please copy/paste the Event Log result of a sync and let us know if it works.


If I get one, I'll definitely do that.


Sent from my iPad using Tapatalk

Re: Nexia Z-Wave Doorbell Sensor, DB100Z

PostPosted: Sun Nov 27, 2016 4:46 pm
by RAID5
I used to use the Fibaro door/window sensor like mat, but it was problematic because every time it ran out of battery it needed to be excluded and included again. Instead I switched to the more versatile Fibaro Universal Sensor, it has two inputs and can also have 4 temp sensors installed. It's also very inexpensive and can use power supplied by the doorbell transformer (at least in my installation)


Skickat från min iPhone med Tapatalk

Re: Nexia Z-Wave Doorbell Sensor, DB100Z

PostPosted: Tue Nov 29, 2016 1:59 pm
by aldera
matt (support) wrote:
I checked and no one has reported using one to us yet, so I'm not sure if it works. If someone gets one then please copy/paste the Event Log result of a sync and let us know if it works.


I bought one and just hooked it up. Here's what I get when I do a sync:

Nov 29, 2016, 1:35:44 PM
Z-Wave Syncing - started for "031 - Notification Sensor"
Z-Wave Syncing - retrieved module neighbors list: 2, 3, 4, 9, 10, 11, 13, 14, 16, 25, 30
Z-Wave Syncing - assigning return route to "031 - Notification Sensor"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Unknown - 0178, Notification Sensor - 44423130
Z-Wave Syncing - retrieved protocol version 4.05, app version 1.44
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01, base 00)
Z-Wave Syncing - retrieved command classes: 20v1 80v1 84v2 85v1 86v1 70v1 71v1 72v1 73v1 59v1 5Av1 7Av1 5Ev1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, battery, beaming, waking
Z-Wave Syncing - retrieved wake interval of 420 minutes
Z-Wave Syncing - device "031 - Notification Sensor" wake interval changed to 60 minutes
Z-Wave Syncing - retrieved group 1 associations: []
Z-Wave Syncing - added group 1 association to interface
Z-Wave Syncing - retrieved battery level of 100%
Z-Wave Syncing - created device "031 - Notification Sensor"
Z-Wave Syncing - complete
Z-Wave sent "031 - Notification Sensor" status request
Z-Wave received "031 - Notification Sensor" status update battery level 100%


When I ring the doorbell, this is what comes up:

Nov 29, 2016, 2:45:16 PM
Z-Wave Lock Manager Unknown lock status received: 0 [Node: 31]
Z-Wave Lock Manager Unknown lock status received: 0 [Node: 31]

It's weird. My doorbell sensor is node 31 but the Z-Wave Lock Manager is responding to it. My doorlock (Kwikset) is on node 29. If I create a trigger for node 31, nothing happens.

Re: Nexia Z-Wave Doorbell Sensor, DB100Z

PostPosted: Tue Nov 29, 2016 7:56 pm
by matt (support)
Can you turn on debug Z-Wave logging (via the Interfaces->Z-Wave->Configure... menu item), then press the doorbell a few times and copy/paste the log results into a reply for me? Also press and hold it a few seconds before releasing it. Does it send different commands for being depressed versus released?

Re: Nexia Z-Wave Doorbell Sensor, DB100Z

PostPosted: Wed Nov 30, 2016 11:06 am
by aldera
matt (support) wrote:
Can you turn on debug Z-Wave logging (via the Interfaces->Z-Wave->Configure... menu item), then press the doorbell a few times and copy/paste the log results into a reply for me? Also press and hold it a few seconds before releasing it. Does it send different commands for being depressed versus released?


Here is the log:

Quick press and release
Nov 30, 2016, 12:00:37 PM
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 1F 0A 71 05 00 00 00 FF 08 01 00 00 7C
Z-Wave Debug . . requestAlarmSensorStatus: node 031, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 8, valueExt 1, classSubKeyExt 7100000801
Z-Wave Lock Manager Unknown lock status received: 0 [Node: 31]
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 1F 0A 71 05 00 00 00 FF 08 00 00 00 7D
Z-Wave Debug . . requestAlarmSensorStatus: node 031, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 8, valueExt 0, classSubKeyExt 7100000800
Z-Wave Lock Manager Unknown lock status received: 0 [Node: 31]

Quick press and release
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 1F 0A 71 05 00 00 00 FF 08 01 00 00 7C
Z-Wave Debug . . requestAlarmSensorStatus: node 031, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 8, valueExt 1, classSubKeyExt 7100000801
Z-Wave Lock Manager Unknown lock status received: 0 [Node: 31]
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 1F 0A 71 05 00 00 00 FF 08 00 00 00 7D
Z-Wave Debug . . requestAlarmSensorStatus: node 031, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 8, valueExt 0, classSubKeyExt 7100000800
Z-Wave Lock Manager Unknown lock status received: 0 [Node: 31]

Press and hold (1-2 seconds), then release

Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 1F 0A 71 05 00 00 00 FF 08 01 00 00 7C
Z-Wave Debug . . requestAlarmSensorStatus: node 031, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 8, valueExt 1, classSubKeyExt 7100000801
Z-Wave Lock Manager Unknown lock status received: 0 [Node: 31]
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 1F 0A 71 05 00 00 00 FF 08 00 00 00 7D
Z-Wave Debug . . requestAlarmSensorStatus: node 031, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 8, valueExt 0, classSubKeyExt 7100000800
Z-Wave Lock Manager Unknown lock status received: 0 [Node: 31]


Press and hold (1-2 seconds), then release

Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 1F 0A 71 05 00 00 00 FF 08 01 00 00 7C
Z-Wave Debug . . requestAlarmSensorStatus: node 031, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 8, valueExt 1, classSubKeyExt 7100000801
Z-Wave Lock Manager Unknown lock status received: 0 [Node: 31]
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 1F 0A 71 05 00 00 00 FF 08 00 00 00 7D
Z-Wave Debug . . requestAlarmSensorStatus: node 031, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 8, valueExt 0, classSubKeyExt 7100000800
Z-Wave Lock Manager Unknown lock status received: 0 [Node: 31]

Re: Nexia Z-Wave Doorbell Sensor, DB100Z

PostPosted: Wed Nov 30, 2016 4:46 pm
by matt (support)
Thanks – I believe we have the information to create the device definition for it now.

Re: Nexia Z-Wave Doorbell Sensor, DB100Z

PostPosted: Wed Nov 30, 2016 5:15 pm
by aldera
matt (support) wrote:
Thanks – I believe we have the information to create the device definition for it now.


Great. Still new to Indigo but does that mean it will make it in one of the upcoming v7.0.x releases?

Re: Nexia Z-Wave Doorbell Sensor, DB100Z

PostPosted: Wed Nov 30, 2016 5:29 pm
by jay (support)
Probably won't be in a 7.0.x (bugfix) release, but likely 7.1.

Re: Nexia Z-Wave Doorbell Sensor, DB100Z

PostPosted: Tue Jan 03, 2017 1:22 pm
by blysik
Any update on DB100Z support? I have one sitting around waiting to be used. :)

Re: Nexia Z-Wave Doorbell Sensor, DB100Z

PostPosted: Tue Jan 03, 2017 3:40 pm
by matt (support)
Not yet, but still on the feature request list.