Would this device be suitable to detect motion of persons walking up my driveway but not register cars on the road? I have Blink cameras, but they either give too many false alerts or no alerts at all. I would ideally place the monitor where this camera is located (roughly) but concerned the PIR sensor would get every moving car.
How sensitivity is not adjustable? Fixed range is ok for an indoor motion sensors, for an outdoor sensor having adjustable range is a must. I don’t want people on the sidewalk to trigger porch lights. If this has to be explained… well, that’s not right.
Wish I knew this earlier, as I just received an ordered sensor, now will be returning it.
Typically, you should be able to position the sensor to cover just the area you need for intended use. We’ll try to add adjustable sensitivity in the near future though to help fine tune functionality.
With all due respect, if I have to explain the basics it only reassures I shouldn’t be buying this product
- Ideal motion sensor doesn’t have sniper rifle precision, I don’t have to position it “just to cover the area”. My “area” is everything close to my porch/driveway, this is what I’d consider “typical”. Zenith wireless motion sensor has 270 deg of visibility, for example, 'cause they know the business they in.
- Try walking into Home Depot and find an outdoor motion at comparable price. If you manage to find one without range adjustment I promise I’ll keep mine.
Point taken, we’ve been working on adding sensitivity to the sensor and hope to have it implemented both as a hardware and software feature in the next version. We’ll send you a message once it’s ready and offer a free sample at that point. Please feel free to share any other feedback you have on the product.
1 Like
A way to include it non secure would be great. With recent platform changes, these sensors seem to have extremely slow reaction time. Maybe it’s the cloud latency of the custom DTH, but even switching to a local handler still they react slow.
1 Like
Thanks for the feedback Bob. Did you try re-including the sensor recently after it was added to the platform and officially certified? We’ll do some testing and see if we can replicate this behavior. Will also work on an option to add them in a non-secure mode.
1 Like
@TheSmartestHouse can you provide details about how wide the field of view is both horizontally and vertically for this device (in degrees)? For some reason none of your documentation seems to have clear information about this.
It’s a 100 degree radius horizontally and vertically, with full coverage at the edges and smaller coverage towards the center of detection field.
1 Like
Zooz Outdoor Motion Sensor 1.1
I just posted a new version that has a tile that shows the firmware version, but after upgrading the handler that tile will be empty until the next time the device wakes up. You can force the device to wake up by removing the batteries for about 5 seconds and then putting them back in.
The new version also has the following settings, but they’re only supported by firmware 1.4 and above.
Motion Cleared Delay: The delay between the last motion event and the device reporting motion inactive.
Brightness Trigger: The lux value below which basic_set command is reported to the hub.
(I believe this only affects devices that have been manually added to this device’s association group)
I just got one of these sensors. I first installed the DTH from the first post in this thread (the new version 1.1). I then powered up the sensor. It was immediately recognized by my SmartThings hub and added using the correct DTH. But I can’t get it to work. When I start it in test mode (both knobs turned all the way to the left and the tamper switch not pressed), the first time I move in front of the sensor the LED turns on, but SmartThings doesn’t show that motion was detected. Then the LED just stays on until I remove the batteries or take it out of test mode. When it’s in normal mode, SmartThings never indicates that motion was detected. The SmartThings log gets a bunch of errors similar to this:
groovy.lang.MissingMethodException: No signature of method: script_dth_9e1cea8ea7d0c9d18ce3f5aecad23e36f57bc73cc672734abeef8ec93ac7da91.logTrace() is applicable for argument types: (org.codehaus.groovy.runtime.GStringImpl) values: [BasicSet: BasicSet(value: 255)]
Do I have a defective sensor? Or is there a step I might have missed in setting it up?
Does your device show that it’s version 2.0?
The SmartThings app doesn’t show anything.
But within the SmartThings web interface I see this, which appears to indicate that it’s version 1.04?
zw:Ss type:0701 mfr:027A prod:0001 model:0005 ver:1.04 zwv:4.61 lib:03 cc:5E,55,98,9F sec:86,85,59,72,5A,73,6C,7A,80,84,71,70 role:06 ff:8C07 ui:8C07
Check the type filed in the IDE and make sure it was assigned my handler. It should be at the very bottom of the list.
It’s assigned Zooz Outdoor Motion Sensor, which is at the bottom of the list of types.
Can you share your DTH?
On the first post in this thread I clicked “show original” and copied the dth there.
I’ve written about 50 DTHs over the last 4 years and they’ve all had code like the following in them so do you have any idea why it’s logging an error for this user?
def zwaveEvent(physicalgraph.zwave.commands.basicv1.BasicSet cmd) {
logTrace "BasicSet: $cmd"
return []
}
private logTrace(msg) {
// log.trace "$msg"
}Your last comment prompted me to take a closer look at the DTH. The last 3 lines (the logTrace function) were missing from my copy! I don’t know how I did that, but somehow I left them out when I copied it. I have added those 3 lines and now everything appears to be working correctly. I apologize for causing you to spend time trying to diagnose a problem caused by my mistake. Thanks for your help.
1 Like