D-link Motion Sensor DCH-Z122

I was able to setup this z-wave motion sensor but if I set up a basic rule to turn on another device OR send a notification when motion is detected- nothing happens.

The motion status always stays active.

I got this sensor for a very good price so I need to make it work.

I would suggest a couple of things:

  • Provide a screenshot (or at least a text-based outline) of the rule that you have mentioned, including what app if was configured in, e.g. Rule Machine, etc
  • Turn on all logging options for the rule and the device, then provide screenshots of the events tab for the device along with the logs for the device and the rule
2 Likes

Done! Thanks!

1 Like

I'm presuming there's nothing to this, but just so you know, it may be somewhat confusing for some if you post under separate accounts that appear to be you...

2 Likes

What "separate accounts" do you mean?

@amfule and @fuel.me

2 Likes

oh.. i'm not so sure how it happened. @amfule is what I used to register my HE.

1 Like

You have only provided the logs for the device, I also suggested including the logs for the app you are using ("test dlink motion"). Seeing these logs together can help understand what is happening.

Also, I wonder if the settings for repeats could be contributing to your problem... But I am not familiar with the App...

The log for the app is empty.

The "current State" of motion is ACTIVE all the time. It never turns to INACTIVE. The device log also always shows ACTIVE.

That sounds like the place to look then.... unless motion is indeed active "all of the time", then I think you need to check the communications between the device and the HE hub.

If i tried covering the sensor for a few minutes, the device log shows nothing (it doesn't say anything about motion being active or not). If i remove the cover, the device log will show "Dlink Motion Sensor motion became active".

I have also removed (exlcluded) and added (included) the device, rebooted the HE.

Hmmm... My experience with motion sensors doesn't stretch far outside of Philips Hue indoor sensors. Best I can think of is either that there is:

  • Some kind of lengthy "cool-down" time that you need to identify and deal with

I was going to say a loss of comm's, but the fact you see it reporting motion once you uncover the motion sensor tells me communication is not an issue.... So I would suggest checking the cool-down setting... if there is one.

There is none thought. Thanks for the assistance.

I would refrain from any of that; doing so will just complicate things. If the device is paired it should be reporting events, assuming it is supported (or sends the correct messages to be handled as a generic device).

This is the problem. Until it reports inactive, the device isn't working. (don't worry about the rule)

Can you show the logs or events tab from when you did this?

Also... 'became' or 'is'? E.g., one of my motion sensors:

image

FWIW, I don't see this device (or anything from Dlink) here:

3 Likes

Slightly more helpful... :wink: :point_up:

1 Like

I don't know if this will help - The "Manufacturer Provided Product Manual" seems pretty thorough.

https://products.z-wavealliance.org/products/2083?selectedFrequencyId=2

3 Likes

The product detail shows a configuration for "Enable sending motion OFF report.(0:Disable, 1:Enable)" Is there a way to set this configuration to "Enable"?

1 Like

You can use the Basic Z-Wave Tool driver (available in Hubitat Package Manager) to set z-wave parameters for any z-wave device.

Since this appears to be a battery-only device, it will need to be woken up in order to recieve/process any confirguration changes.

I'm not an expert at interpreting the Z-Wave Alliance information, but this does appear to be a Z-Wave Plus device... It says it doesn't support S2 or SmartStart, so my guess is that this is a 500-series device :person_shrugging:

1 Like

Yes it is.
will try that driver. Thanks.

1 Like