Ecolink motion sensor not working

Posted on
Sun Mar 12, 2017 1:37 pm
clawmd offline
Posts: 87
Joined: Jan 01, 2007

Ecolink motion sensor not working

Just got 2 of these units. PIR-Zwave2.5-ECO. Was able to include them easily but they don't seem to detect motion. If I put them in the continuously awake mode by taking off the cover I can poll them. No matter what I do, the state always remains" off." I also notice in the event log this message " Z-Wave Lock Manager Unknown lock status received: 0 [Node: 33]". Not sure what to do next. It seems unlikely that both motion sensors are broken.

Here is the log for when I included

controller included module: 033 - Notification Sensor
Z-Wave stopped controller inclusion mode
Z-Wave Syncing - started for "033 - Notification Sensor"
Z-Wave Syncing - retrieved module neighbors list: 5, 6, 15, 16, 18, 21, 23, 24, 25, 28
Z-Wave Syncing - assigning return route to "033 - Notification Sensor"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Ecolink - 014A, Notification Sensor - 00040001
Z-Wave Syncing - retrieved protocol version 4.05, app version 10.01
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 30v1 70v1 71v1 72v1 73v1 59v1 5Ev1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, battery, beaming, waking
Z-Wave Syncing - retrieved wake interval of 240 minutes
Z-Wave Syncing - device "033 - Notification Sensor" wake interval changed to 60 minutes
Z-Wave Syncing - retrieved group 1 associations: []
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Syncing - added group 1 association to interface
Z-Wave Syncing - retrieved battery level of 99%
Z-Wave Syncing - retrieved battery level of 99%
Z-Wave Syncing - created device "033 - Notification Sensor"
Z-Wave Syncing - complete
Z-Wave sent "033 - Notification Sensor" status request
Z-Wave received "033 - Notification Sensor" status update battery level 99%
Z-Wave received "033 - Notification Sensor" status update battery level 99%

Posted on
Sun Mar 12, 2017 1:59 pm
matt (support) offline
Site Admin
User avatar
Posts: 18747
Joined: Jan 27, 2003
Location: Texas

Re: Ecolink motion sensor not working

Turn on the debug logging checkbox (via the Interfaces->Z-Wave->Configure... menu item), then trip the motion sensor a few times and copy/paste the Event Log results into a reply for me.

Image

Posted on
Sun Mar 12, 2017 2:08 pm
clawmd offline
Posts: 87
Joined: Jan 01, 2007

Re: Ecolink motion sensor not working

here is the debugging log

Mar 12, 2017, 4:06:24 PM
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 11 00 04 00 21 0B 71 05 00 00 00 FF 07 08 00 00 00 44
Z-Wave Debug . . requestAlarmSensorStatus: node 033, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 8, classSubKeyExt 7100000708
Z-Wave Debug RCVD requestBinarySensorStatus: 01 0A 00 04 00 21 04 30 03 FF FF E7
Z-Wave Debug . . requestBinarySensorStatus: node 033, endpoint None, type 255, value 255
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 11 00 04 00 21 0B 71 05 00 00 00 FF 07 00 00 00 00 4C
Z-Wave Debug . . requestAlarmSensorStatus: node 033, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700
Z-Wave Debug RCVD requestBinarySensorStatus: 01 0A 00 04 00 21 04 30 03 00 FF 18
Z-Wave Debug . . requestBinarySensorStatus: node 033, endpoint None, type 255, value 0
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 11 00 04 00 21 0B 71 05 00 00 00 FF 07 08 00 00 00 44
Z-Wave Debug . . requestAlarmSensorStatus: node 033, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 8, classSubKeyExt 7100000708
Z-Wave Debug RCVD requestBinarySensorStatus: 01 0A 00 04 00 21 04 30 03 FF FF E7
Z-Wave Debug . . requestBinarySensorStatus: node 033, endpoint None, type 255, value 255
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 11 00 04 00 21 0B 71 05 00 00 00 FF 07 00 00 00 00 4C
Z-Wave Debug . . requestAlarmSensorStatus: node 033, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700
Z-Wave Debug RCVD requestBinarySensorStatus: 01 0A 00 04 00 21 04 30 03 00 FF 18
Z-Wave Debug . . requestBinarySensorStatus: node 033, endpoint None, type 255, value 0

Posted on
Sun Mar 12, 2017 2:16 pm
matt (support) offline
Site Admin
User avatar
Posts: 18747
Joined: Jan 27, 2003
Location: Texas

Re: Ecolink motion sensor not working

We'll look at adding a device definition for this module. In the mean time you can trigger off of the motion commands by using the Trigger type Z-Wave Command Received. From the configuration dialog choose Match Raw Packet from the Received popup, then you can use these Matched Bytes for detecting motion:

* 0x04 0x00 0x21 0x0B 0x71 0x05 0x00 0x00 0x00 0xFF 0x07 0x08 *

and these for detecting when the motion detector is idle after a while:

* 0x04 0x00 0x21 0x0B 0x71 0x05 0x00 0x00 0x00 0xFF 0x07 0x00 *

Image

Posted on
Sun Mar 12, 2017 2:33 pm
clawmd offline
Posts: 87
Joined: Jan 01, 2007

Re: Ecolink motion sensor not working

Tried that and got an Error. New trigger->type=Zwave command received ->Event=incoming command. Configure incoming command , From=Ecolink and received=match raw packet. I pasted the packet and I get the error "match bytes can only contain integers"

Posted on
Sun Mar 12, 2017 2:35 pm
matt (support) offline
Site Admin
User avatar
Posts: 18747
Joined: Jan 27, 2003
Location: Texas

Re: Ecolink motion sensor not working

Use:

* 0x04 0x00 0x21 0x0B 0x71 0x05 0x00 0x00 0x00 0xFF 0x07 0x08 *

and:

* 0x04 0x00 0x21 0x0B 0x71 0x05 0x00 0x00 0x00 0xFF 0x07 0x00 *

Image

Posted on
Sun Mar 12, 2017 2:46 pm
clawmd offline
Posts: 87
Joined: Jan 01, 2007

Re: Ecolink motion sensor not working

Hurray! That works perfectly. Thanks!!

Posted on
Sun Jul 23, 2017 5:16 pm
bjmouton offline
Posts: 4
Joined: Jul 23, 2017

Re: Ecolink motion sensor not working

I have an older version Ecolink sensor PIR-ZWAVE2 & it works perfectly, I recently purchased three more of them (new version shipping now) PIR-ZWAVE2.5-ECO and these do not work. I can get them to sync with the cover off, but that's all they do is sync, they do not communicate. I have tried the workaround listed in this thread with no success! Any new developments?

Posted on
Tue Jul 25, 2017 6:38 pm
matt (support) offline
Site Admin
User avatar
Posts: 18747
Joined: Jan 27, 2003
Location: Texas

Re: Ecolink motion sensor not working

Can you copy/paste the Event Log window results of the sync for the module that doesn't work?

Also turn on Z-Wave debug logging (via the Interfaces->Z-Wave->Configure... menu item), and then trip the sensor a few times. Is anything logged to the Event Log window (copy/paste it for us)?

Image

Posted on
Tue Jul 25, 2017 9:25 pm
bjmouton offline
Posts: 4
Joined: Jul 23, 2017

Re: Ecolink motion sensor not working

Matt,

Below is event log from sensor sync (with cover off of unit), once cover is replaced, there is no activity logged.

Jul 25, 2017, 22:12:44
Z-Wave Debug intiatingSyncUI (timeout in 1500 seconds)
Z-Wave Syncing - started for "Guest Bedroom Motion Sensor"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 27 01 01 5E
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 4B 0F 78 90 07 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 F5
Z-Wave Debug . . getNodeNeighbors: nodeId 039, neighbors: 1, 2, 4, 7, 9, 10, 11, 12, 20, 21, 22, 23, 29, 32, 33, 34, 35
Z-Wave Syncing - retrieved module neighbors list: 1, 2, 4, 7, 9, 10, 11, 12, 20, 21, 22, 23, 29, 32, 33, 34, 35
Z-Wave Syncing - assigning return route to "039 - Guest Bedroom Motion Sensor"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 27 01 9A
Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD
Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 00 BD
Z-Wave Debug . . assignReturnRoute: node 039, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 27 24 82 18
Z-Wave Debug RCVD nodeInfoFrame: 01 16 00 49 84 27 10 04 07 01 5E 86 72 73 80 71 85 59 84 30 70 EF 20 EE
Z-Wave Debug . . nodeInfoFrame: node 039, combined class list: 20v1 80v1 84v1 85v1 86v1 30v1 70v1 71v1 72v1 73v1 59v1 5Ev1
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 27 02 72 04 25 83 10
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 27 08 72 05 01 4A 00 04 00 01 E3
Z-Wave Debug . . requestManufactureInfo: node 039, manufacturerId 014A, productId 00040001
Z-Wave Debug . . requestManufactureInfo: Ecolink, Notification Sensor
Z-Wave Syncing - retrieved manufacture and model names: Ecolink - 014A, Notification Sensor - 00040001
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 27 02 86 11 25 84 F6
Z-Wave Debug RCVD requestVersInfoGen: 01 11 00 04 00 27 0B 86 12 06 04 05 0A 01 02 00 00 00 5C
Z-Wave Debug . . requestVersInfoGen: node 039, protoVers 4.05, appVers 10.01
Z-Wave Syncing - retrieved protocol version 4.05, app version 10.01
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 27 03 86 13 84 25 85 73
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0A 00 04 00 27 04 86 14 84 02 C6
Z-Wave Debug . . requestVersInfoCmdClass: node 039, class command 84 using version 2
Z-Wave Debug . . requestVersInfoCmdClass: node 039, combined class list: 20v1 80v1 84v2 85v1 86v1 30v1 70v1 71v1 72v1 73v1 59v1 5Ev1
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 30v1 70v1 71v1 72v1 73v1 59v1 5Ev1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, battery, beaming, waking
Z-Wave Debug SENT requestWakeInterval: 01 09 00 13 27 02 84 05 25 86 E2
Z-Wave Debug RCVD requestWakeInterval: 01 0C 00 04 00 27 06 84 06 00 0E 10 01 4B
Z-Wave Debug . . requestWakeInterval: node 039, interval 60 minutes, wakeTarget 001
Z-Wave Syncing - retrieved wake interval of 60 minutes
Z-Wave Debug SENT setWakeInterval: 01 0D 00 13 27 06 84 04 00 0E 10 01 25 87 FD
Z-Wave Syncing - device "039 - Guest Bedroom Motion Sensor" wake interval changed to 60 minutes
Z-Wave Debug SENT requestAssociationGroupCount: 01 09 00 13 27 02 85 05 25 88 ED
Z-Wave Debug RCVD requestAssociationGroupCount: 01 09 00 04 00 27 03 85 06 02 57
Z-Wave Debug . . requestAssociationGroupCount: node 039, group count: 2
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 27 03 85 02 01 25 89 E8
Z-Wave Debug RCVD requestAssociations: 01 0C 00 04 00 27 06 85 03 01 05 00 01 55
Z-Wave Debug . . requestAssociations: node 039, group: 1, num associations: 1, max associations: 5, replies left: 0
Z-Wave Debug . . requestAssociations: node 039, group: 1, associations: [1]
Z-Wave Syncing - retrieved group 1 associations: [1]
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 27 03 85 02 02 25 8A E8
Z-Wave Debug RCVD requestAssociations: 01 0B 00 04 00 27 05 85 03 02 05 00 53
Z-Wave Debug . . requestAssociations: node 039, group: 2, num associations: 0, max associations: 5, replies left: 0
Z-Wave Debug . . requestAssociations: node 039, group: 2, associations: []
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Syncing - group 1 association to interface already exists (skipping)
Z-Wave Debug SENT requestBatteryLevel: 01 09 00 13 27 02 80 02 25 8B EC
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 27 03 80 03 3D 68
Z-Wave Debug . . requestBatteryLevel: node 039, level 61
Z-Wave Syncing - retrieved battery level of 61%
Z-Wave Syncing - complete
Z-Wave Debug SENT requestAlarmSensorStatus: 01 09 00 13 27 02 71 04 25 8C 1C
Z-Wave Debug terminatingSyncUI
Z-Wave sent "Guest Bedroom Motion Sensor" status request
Z-Wave Debug SENT requestBatteryLevel: 01 09 00 13 27 02 80 02 25 8D EA
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 27 03 80 03 3D 68
Z-Wave Debug . . requestBatteryLevel: node 039, level 61
Z-Wave received "039 - Guest Bedroom Motion Sensor" status update battery level 61%

Posted on
Tue Jul 25, 2017 9:43 pm
matt (support) offline
Site Admin
User avatar
Posts: 18747
Joined: Jan 27, 2003
Location: Texas

Re: Ecolink motion sensor not working

That is strange it doesn't send anything at all. Following its manual for testing:

1) Place the sensor in an unoccupied room
2) Leave the room for at least 4 minutes
3) Return to the room and pass in front of the lens of the sensor
4) The LED light will flash to indicate movement was detected

when you get to step #4 does the LED even flash?

Image

Posted on
Wed Jul 26, 2017 8:37 pm
bjmouton offline
Posts: 4
Joined: Jul 23, 2017

Re: Ecolink motion sensor not working

Yes, the green LED will flash when approaching the sensor after a period of no motion in the room. As I mentioned in my earlier post, I purchased three of them. Upon setup of the first one, I noticed that Indigo was not detecting the motion events, I then setup a second one with the same results. The third one, I setup on a ST hub & it works flawlessly.

Just captured the following in the event log, apparently Indigo IS receiving transmissions from the two sensors, but not indicating the binary change of state.

Jul 26, 2017, 21:31:31
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 11 00 04 00 27 0B 71 05 00 00 00 FF 07 00 00 00 00 4A
Z-Wave Debug . . requestAlarmSensorStatus: node 039, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700
Z-Wave Debug RCVD requestBinarySensorStatus: 01 0A 00 04 00 27 04 30 03 00 FF 1E
Z-Wave Debug . . requestBinarySensorStatus: node 039, endpoint None, type 255, value 0
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 11 00 04 00 26 0B 71 05 00 00 00 FF 07 00 00 00 00 4B
Z-Wave Debug . . requestAlarmSensorStatus: node 038, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700
Z-Wave Debug RCVD requestBinarySensorStatus: 01 0A 00 04 00 26 04 30 03 00 FF 1F
Z-Wave Debug . . requestBinarySensorStatus: node 038, endpoint None, type 255, value 0

Posted on
Fri Jul 28, 2017 1:09 pm
matt (support) offline
Site Admin
User avatar
Posts: 18747
Joined: Jan 27, 2003
Location: Texas

Re: Ecolink motion sensor not working

I'm afraid I don't know why one of them isn't sending anything on motion, but for the two that are you can catch and Trigger off of the motion by using the trigger type Z-Wave Command Received.

Inside the configure sub-dialog choose your device in the From popup and choose Match Raw Packet from the the Received popup. The Match bytes for would be:

* 0x71 0x05 0x00 0x00 0x00 0xFF 0x07 0x00 0x00 0x00 0x00 *

We will also add this to our list of devices to support (by adding device definitions to Indigo).

Image

Posted on
Sat Jul 29, 2017 8:04 am
bjmouton offline
Posts: 4
Joined: Jul 23, 2017

Re: Ecolink motion sensor not working

That worked (sort of), the mask:
* 0x71 0x05 0x00 0x00 0x00 0xFF 0x07 0x00 0x00 0x00 0x00 *
is apparently for "ON to OFF" transition as Indigo trigger was set approx. 4 min. after sensor was triggered. I changed the mask to:
* 0x71 0x05 0x00 0x00 0x00 0xFF 0x07 0x08 0x00 0x00 0x00 *
and Indigo now triggers on an "OFF to ON" transition as soon as motion is detected.

Posted on
Wed Oct 24, 2018 6:40 am
espressodaily offline
Posts: 29
Joined: Nov 05, 2013

Re: Ecolink motion sensor not working

I have the same sensor, but the posted raw bytes didn't work for me. I inspected the debug log and was able to change to match. This works for me:

ON
* 0x04 0x00 0x85 0x0B 0x71 0x05 0x00 0x00 0x00 0xFF 0x07 0x08 *
OFF
* 0x04 0x00 0x85 0x0B 0x71 0x05 0x00 0x00 0x00 0xFF 0x07 0x00 *

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 0 guests