Ecolink PIR motion sensor zwave plus

Using Aeontec Z-Stick Gen5 & Ecolink Zwave Plus PIR (note: you may have the older version that is not the “plus”, so heads up this is different slightly) sensor and have installed openzwave-1.4.1. I am not able to get this fully working properly…

My PIR sensor shows up sleep but it does not get recognized as an ecolink (do not care much).

Here is the OZW_log.txt and Node001 is the Z-Stick Gen5 that works great. Node002 is the Ecolink.

Here are some interesting warnings:

2017-07-06 18:28:10.163 Warning, Failed - Network Key Not Set
2017-07-06 18:28:14.470 Info, Node002, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2017-07-06 18:28:14.471 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2017-07-06 18:28:14.471 Warning, CheckCompletedNodeQueries all=0, deadFound=0 sleepingOnly=1
2017-07-06 18:31:17.946 Warning, Exception: Manager.cpp:2499 - 102 - ValueID passed to GetValueFloatPrecision is not 
2017-07-06 18:34:14.988 Warning, Exception: Manager.cpp:373 - 100 - Invalid HomeId passed to GetDriver

Now, when trigger motion, I see the following in the logs:

2017-07-06 17:22:03.442 Info, Node002, ApplicationCommandHandler - Unhandled Command Class 0x30
2017-07-06 17:22:21.907 Detail, Node002,   Received: 0x01, 0x11, 0x00, 0x04, 0x00, 0x02, 0x0b, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x07, 0x00, 0x00, 0x00, 0x00, 0x6f
2017-07-06 17:22:21.907 Detail, 
2017-07-06 17:22:21.907 Info, Node002, ApplicationCommandHandler - Unhandled Command Class 0x71
2017-07-06 17:22:21.928 Detail, Node002,   Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x02, 0x04, 0x30, 0x03, 0x00, 0xff, 0x3b

That tells me something is being seen by the controller. Do you have any recommendations based on the above information on what I need do to detect motion and run a shell command?

I’ve spend the day experimenting and reading, but have lucked out. I’d appreciate any guidance.

I don’t know for sure but I suspect that the pir needs to be added using secure mode and you perhaps don’t have the key set in the options.xml file.

I have this motion sensor. I added it securely via the zwave option in HA and it works fine. The steps I took were as follows:

  1. remove/exclude the node.
  2. Add Node Secure via zwave menu.
  3. restart HA
  4. you can rename the node via zwave options to provide it a more friendly name.

I didn’t have to provide any other config options for it to report a status to HA. It should appear as a binary_sensor and report off and on status.

Thank you - I did need to add the key in the configuration file.

Thank you for this Mike!

After trying this multiple times to add using the secure mode with no luck. I then tried it with a new Ecolink (I had bought 2) and it showed up fine just like you said!

Which of the sensors do you recommend I use in the picture below?

Just adding this here to help others if they are looking for it… Here is what my page looks like now.

Also, any idea why my first sensor is not able to get added to the network? I took out the battery, did the factory reset and all that and no luck (I factory reset the z-stick too).

If you take a look in the states menu (The 2x <> icons) the motion should be listed as a binary_sensor where the others are listed as sensors. I use the binary_sensor one to trigger my motion based automatons.

So in your case it is the one named Ecolink Unknown: type=0004, id=0001 Sensor. You can rename this via the zwave panel to give it a more friendly name.

1 Like

Got it - Pic attached below of what Mike is talking about if it helps anyone.

Any thoughts on how to reset my first ecolink to get it to reconnect? I factory reset the sensor and the zstick.

That is the one. Off would indicate no motion and on is motion. If I recall to pair mine I removed the battery and ran the remove zwave node and put the battery in then, removed the battery and ran the add secure node and inserted the battery. I think the LED will blink when it is not paired to a controller.

1 Like

Thank you for your help Mike! I was about to return the whole thing :slight_smile:

Glad to hear it worked out…Happy Automating