Ecolink Motion running slow

Posted on
Fri Sep 07, 2018 7:42 pm
dnomode offline
Posts: 337
Joined: Apr 12, 2008
Location: North Georgia

Ecolink Motion running slow

Hello Everyone,

I just received my Z-Stick Gen5 and two Ecolink motion sensors PIR-zwave2.5-eco today.

The motion sensors seems very slow. After I move my hand in front of the sensor the LED on the front takes about 15 seconds to flash and once it does flash Indigo gets the command within 1 second (very fast)

Is this normal?

The way I set it up is:
-Setup Z-stick on Serial Port usbmodemFA121
-added the eco link in devices
-setup a trigger Type=Z-Wave Command Received, Event=Incoming Command Received from Device, From=003-Notification Sensor, Received=Match Raw Packet, Match bytes=0x01 0x0A 0x00 0x04 0x00 0x03 0x04 0x30 0x03 0x00 0xFF 0x3A

Is this the correct setup?

Shouldn't we see when the motion is activated from the devices folder. The state of the device never changes from off.

Also Indigo only gets the motion trigger from one of the motion sensors. The other seems like doesn't even work. Both are setup the same way.

Is it normal for this motion sensor to take 15 seconds to detect the motion?
What should I check with the second sensor to make it work?

And most important, what sensors are y'all using? I need something fast.

Thanks for the help
Edmond

Posted on
Sat Sep 08, 2018 6:57 am
dnomode offline
Posts: 337
Joined: Apr 12, 2008
Location: North Georgia

Re: Ecolink Motion running slow

I've been playing around with these and I now have them reacting faster in Indigo. I noticed the Write Recent Packets to Log button on the configuration window for the triggers. So I copied and pasted the longer string into the Match Bytes field. The reaction time is much better.

I still don't have any visual notification in the Home Window of Indigo that motion is detected. The state never changes from off
Screenshot 2018-09-08 08.38.45.png
Screenshot 2018-09-08 08.38.45.png (87.94 KiB) Viewed 249 times


At my last house I used the motion sensors from my DSC alarm and used the DSC plugin. The state of the motion sensor would change from closed to open every time motion was detected. I'm was kind of expecting the same for these devices.
Screenshot 2018-09-08 08.37.27.png
Screenshot 2018-09-08 08.37.27.png (104.14 KiB) Viewed 249 times


Matt and Jay, If you have, would you please send me the link for the instruction on setting up Z-Wave motion sensors? I couldn't find documentation and just figured it out by playing around. I'd like to understand better Match Raw Packets and Match bytes

Also, should my Z-Stick be flashing Blue-Amber-Red?

thanks everyone
Edmond

Posted on
Sat Sep 08, 2018 10:12 am
matt (support) offline
Site Admin
User avatar
Posts: 18674
Joined: Jan 27, 2003
Location: Texas

Re: Ecolink Motion running slow

Turn on Indigo's Z-Wave debug logging checkbox via the Interfaces->Z-Wave->Configure... menu item, then clear out the Event Log window and trip the motion sensor. Do any commands show in the log window immediately after the motion sensor trips? Let is sit for a minute to collect all commands being received, then copy/paste the Event Log results into a reply for us.

Image

Posted on
Sat Sep 08, 2018 4:40 pm
dnomode offline
Posts: 337
Joined: Apr 12, 2008
Location: North Georgia

Re: Ecolink Motion running slow

Thanks Matt,

here it is...

Code: Select all
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 11 00 04 00 02 0B 71 05 00 00 00 FF 07 08 00 00 00 67
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 002, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 7, valueExt 8, classSubKeyExt 7100000708
   Trigger                         motion 2
   Z-Wave Debug                    RCVD requestBinarySensorStatus: 01 0A 00 04 00 02 04 30 03 FF FF C4
   Z-Wave Debug                    . .  requestBinarySensorStatus: node 002, endpoint None, type 255, value 255
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 11 00 04 00 02 0B 71 05 00 00 00 FF 07 00 00 00 00 6F
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 002, 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 02 04 30 03 00 FF 3B
   Z-Wave Debug                    . .  requestBinarySensorStatus: node 002, endpoint None, type 255, value 0
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 11 00 04 00 03 0B 71 05 00 00 00 FF 07 00 00 00 00 6E
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 003, 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 03 04 30 03 00 FF 3A
   Z-Wave Debug                    . .  requestBinarySensorStatus: node 003, endpoint None, type 255, value 0


Also, should my Z-Stick be flashing Blue-Amber-Red and do you have any documentation on setting up Z-wave motions?

Thanks for the help
Edmond

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 0 guests