Just picked one of these up from Amazon (LINK) and have it connected to my VeraLite but cant get it working properly yet. Thought it would be nice to finally have a trigger for when someone rings the doorbell to snap an image from the camera watching the front door and then sending it to me and/or lowering my music, etc. Anyone have one of these and gotten it working properly?
Ive Got it wired into my doorbell as shown in the install guide (LINK). I have the doorbell with the three screw terminals showing in the bottom left of the guide. Pairing went fine and it showed up as a _SceneController if I remember correctly (I changed the name to keep track of what it was).
Vera just keeps saying its waiting for it to wakeup to transmit settings. On the unit you can press the button three times rapidly and that will wake it up for 10 seconds. Tried that and that didnt help. Ill attach some images as soon as I get a chance.
I don’t have any experience with this device, but I don;t think that it should be a scene controller type device.
I suspect that it will need to be configured as a binary sensor. To do that, change the fields in the devices Advanced tab to match the following and then Save.
[quote=“Z-Waver, post:2, topic:190953”]I don’t have any experience with this device, but I don;t think that it should be a scene controller type device.
I suspect that it will need to be configured as a binary sensor. To do that, change the fields in the devices Advanced tab to match the following and then Save.
Device_Type: urn:schemas-micasaverde-com:device:DoorSensor:1 Device_File: D_DoorSensor1.xml[/quote]
Ill give that a try. For what its worth the default it showed was:
[quote=“Z-Waver, post:2, topic:190953”]I don’t have any experience with this device, but I don;t think that it should be a scene controller type device.
I suspect that it will need to be configured as a binary sensor. To do that, change the fields in the devices Advanced tab to match the following and then Save.
Device_Type: urn:schemas-micasaverde-com:device:DoorSensor:1 Device_File: D_DoorSensor1.xml[/quote]
Would the device not being configured as a binary sensor effect MiOS’s ability to update it? I havent tried changing it yet but I still see the “Waiting for wakeup to configure device” notification below the device.
I don’t think so. Have you tried clicking “configure node right now” and then waking up the device for 10 seconds as you described? That really should force it to configure.
[quote=“benr, post:4, topic:190953”]Would the device not being configured as a binary sensor effect MiOS’s ability to update it? I havent tried changing it yet but I still see the “Waiting for wakeup to configure device” notification below the device.[/quote]This is due to the fact that the device is battery operated and sleeps for most of it’s life.
As @wilme2 stated, you need to wake the device and then configure it. With only a 10 second wakeup period, this may be tricky to get them both synched.
Yea nothing guys. The best I can get it to do is change the error to: Unable to get any information on node". It does appear that it just doesnt stay awake long enough to configure or give Vera enough time to do anything else. Guess I can give Nexia’s customer support a try…
According to the specs, the DB100Z uses the ZM5202 Z-Wave controller - Which makes it a Z-Wave+ device. It may not be possible to get it working on a VeraLite.
Well guess that’d mean I just wasted fifty bucks. Lame. I just got so excited that there might FINALLY be a Z-Wave doorbell sensor! Probably should have waited a bit and done more research.
For anyone curious, Here’s a picture of the backside of the circuit board used in the DB100Z.
It uses the plastic front to hold the batteries. That board slots into the battery tray. There’s only one set of posts installed for just one doorbell, but the circuit board has two sets of solder pads, as does the case have slots for the wiring.
Since Nexia has a subscription model, they obviously want to push folks to their platform. I think that is also why the Schlage locks also seem to be finicky on Vera. I bought a Nexia to update the firmware on my Schlage locks and tried it out for the free first month. I will tell you the locks also work way more reliably with their system then any other z-wave controller I have tried with Schlage locks, clearly their priority is their own system.
While I don’t dispute your theory, I will say that my schlage locks (3 of them) have worked 100% flawlessly on Vera for the past 3 years. I don’t see how they could work any better or different on another controller.
Newer Schlages locks are better, particularly the touch screens, but the older versions (that don’t have upgradable firmware), cannot beam correctly, so will not work if they cannot talk directly to controller, on Vera you could work arround this by manually setting the route (which you cannot do on the newer Vera firmware). I know several folks have had this issue on the Schlages, or if looking through the forums cannot get their locks connected and configured at all. When I tried out the Nexia, they always included and worked right, even with other nodes on the network, so clearly the Nexia has some magic for dealing with the buggy older locks. For me, I have my ancient v1 Schlages connect to my alarms z-wave controller, along with my thermostat, and nothing else, and that allows them to work very reliably, everything else I have on my Vera and everything works great (and ironically have the alarm also connected to my Vera). So don’t get me wrong, love the schlage locks, I particularly like the non-motorized older dead bolt model, if you need super long battery life, and have like mine French doors that have enough variance in alignment durring the seasons to not work well with a motorized lock.
Benr: to be fair it is compatible with other controllers, it’s just using a newer cheap (Z-Wave+) which imposes a new set of encryption / authentication code that isn’t backwards compatible. To be fair Z-Wave+ is substantially better, and any new products are going to shift to that anyway.
I’ve been mucking with the two DB100Z’s that I’ve got, nothing so far. I tried configuring one as a door sensors, and leaving the other alone, no luck overall. I’m not entirely sure how they are intending to work, which is a real pity as I like the idea
[quote=“warthog9, post:16, topic:190953”]Benr: to be fair it is compatible with other controllers, it’s just using a newer cheap (Z-Wave+) which imposes a new set of encryption / authentication code that isn’t backwards compatible. To be fair Z-Wave+ is substantially better, and any new products are going to shift to that anyway.
I’ve been mucking with the two DB100Z’s that I’ve got, nothing so far. I tried configuring one as a door sensors, and leaving the other alone, no luck overall. I’m not entirely sure how they are intending to work, which is a real pity as I like the idea[/quote]
So would these work as intended with the new VeraPlus controller I wonder?
shallowearth, what is the minimum firmware required to “beam correctly”? I am about the purchase a Schlage Camelot touchscreen (probably ebay) and I want to make sure I have a version that doesn’t have older firmware that will cause issues.
Well guess that’d mean I just wasted fifty bucks. Lame. I just got so excited that there might FINALLY be a Z-Wave doorbell sensor! Probably should have waited a bit and done more research.