New Ecolink PIR Sensor appears as Notification Sensor

Posted on
Fri Mar 17, 2017 7:17 pm
noefresh offline
Posts: 119
Joined: Sep 10, 2013

New Ecolink PIR Sensor appears as Notification Sensor

This is what I get instead of a PIR motion sensor. Any ideas:

Code: Select all
Mar 17, 2017, 6:15:53 PM
   Z-Wave                          Indigo Device "017 - Routing Slave" Z-Wave Properties:
Indigo Z-Wave Version: 2.0.68
Node ID: 20
Model: Notification Sensor
Model ID: 00040001
Manufacturer: Ecolink
Manufacturer ID: 014A
Protocol Version: 4.05
Application Version: 10.01
Model Definition Version: 0
Library Type: 6
Class Name: Notification Sensor
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 20v1 80v1 84v2 85v1 86v1 30v1 70v1 71v1 72v1 73v1 59v1 5Ev1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, waking
Neighbors: 2
Associations: 1:[1] 2:[]
Config Values: - none -


Appears as attached files.
Attachments
Image.png
Image.png (46.25 KiB) Viewed 2947 times

Posted on
Fri Mar 17, 2017 7:55 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: New Ecolink PIR Sensor appears as Notification Sensor

What specific model is that one? Do you have a link to a PDF for the manual or technical docs for it?

Image

Posted on
Sat Mar 18, 2017 3:20 pm
noefresh offline
Posts: 119
Joined: Sep 10, 2013

Re: New Ecolink PIR Sensor appears as Notification Sensor

Hi Matt- I ordered it from this page two days ago:

https://www.amazon.com/gp/product/B00FB1TBKS/

and attached is the model info.
Attachments
PIR.jpg
PIR.jpg (154.99 KiB) Viewed 2901 times

Posted on
Mon Mar 20, 2017 11:46 am
noefresh offline
Posts: 119
Joined: Sep 10, 2013

Re: New Ecolink PIR Sensor appears as Notification Sensor

Any suggestions or should I return this and get the older version?

Posted on
Mon Mar 20, 2017 5:53 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: New Ecolink PIR Sensor appears as Notification Sensor

It looks like Indigo is going to need a new device definition for that model. However, you might be able to get it working now with a couple of custom triggers. Turn on the Z-Wave debug logging checkbox (accessible via the Interfaces->Z-Wave->Configure... menu item). Then trip the motion sensor and wait a few minutes for it to reset. Repeat that 2 or 3 times, then copy/paste the Event Log results into a reply for me. That will hopefully help me create the device definition and I can also provide you with the steps to create the custom Triggers for it.

Image

Posted on
Tue Mar 21, 2017 11:11 pm
thatdamncat offline
Posts: 11
Joined: Jul 03, 2016

Re: New Ecolink PIR Sensor appears as Notification Sensor

I'm in the same boat.

Here's 3 cycles of on/off (with 5 second reset, by using the jumper on "test"):

Code: Select all
Mar 21, 2017, 10:09:19 PM
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 11 00 04 00 18 0B 71 05 00 00 00 FF 07 08 00 00 00 7D
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 024, 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 18 04 30 03 FF FF DE
   Z-Wave Debug                    . .  requestBinarySensorStatus: node 024, endpoint None, type 255, value 255
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 11 00 04 00 18 0B 71 05 00 00 00 FF 07 00 00 00 00 75
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 024, 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 18 04 30 03 00 FF 21
   Z-Wave Debug                    . .  requestBinarySensorStatus: node 024, endpoint None, type 255, value 0
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 11 00 04 00 18 0B 71 05 00 00 00 FF 07 08 00 00 00 7D
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 024, 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 18 04 30 03 FF FF DE
   Z-Wave Debug                    . .  requestBinarySensorStatus: node 024, endpoint None, type 255, value 255
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 11 00 04 00 18 0B 71 05 00 00 00 FF 07 00 00 00 00 75
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 024, 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 18 04 30 03 00 FF 21
   Z-Wave Debug                    . .  requestBinarySensorStatus: node 024, endpoint None, type 255, value 0
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 11 00 04 00 18 0B 71 05 00 00 00 FF 07 08 00 00 00 7D
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 024, 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 18 04 30 03 FF FF DE
   Z-Wave Debug                    . .  requestBinarySensorStatus: node 024, endpoint None, type 255, value 255
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 11 00 04 00 18 0B 71 05 00 00 00 FF 07 00 00 00 00 75
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 024, 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 18 04 30 03 00 FF 21
   Z-Wave Debug                    . .  requestBinarySensorStatus: node 024, endpoint None, type 255, value 0


Happy to be Alpha/Beta tester!

Posted on
Thu Mar 23, 2017 8:03 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: New Ecolink PIR Sensor appears as Notification Sensor

Thanks, with that we should be able to create the device definition for it.

In the mean time you all can create Triggers in Indigo using the Z-Wave Command Received type, then from the sub-dialog choose your device and then Match Raw Packet. For knowing when the motion sensor triggers you can use:

Code: Select all
* 0x71 0x05 0x00 0x00 0x00 0xFF 0x07 0x08 *

and if you want to know when it resets (after a period of inactivity you can use:

Code: Select all
* 0x71 0x05 0x00 0x00 0x00 0xFF 0x07 0x00 *

Another approach would be to try the Z-Wave Event and Alarm Listener plugin.

Image

Posted on
Thu Mar 23, 2017 10:57 pm
thatdamncat offline
Posts: 11
Joined: Jul 03, 2016

Re: New Ecolink PIR Sensor appears as Notification Sensor

Nice! That worked. Many thanks.

Posted on
Sat Apr 27, 2019 4:31 pm
cmwaffle offline
Posts: 8
Joined: Apr 27, 2019

Re: New Ecolink PIR Sensor appears as Notification Sensor

I'm running Indigo 7.3 with the Ecolink PIR 2.5. I can include it in my z-wave network and it is recognized by Indigo as a Notification Sensor. Its initial state is "off". I can then activate the sensor and it will work as a trigger (I have it speak that is is working). The sensor shifts its state to "on". It stays in the "on" state until I remove it from the z-wave network and reinstall it. If I simply remove the battery it will restart and fully update (as per the Event Log) but the state will remain "on". It does not appear to be automatically resetting to the "off" state. BTW I have let the PIR sit facing a wall so it couldn't detect any motion for over an hour without any reset to "off".

Any suggestion as to the next step? Thanks.

Posted on
Wed May 08, 2019 6:54 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: New Ecolink PIR Sensor appears as Notification Sensor

Sorry for the delay in responding to this one. After investigating it looks like this is a bug in Indigo's definition for the device. We'll get it fixed in 7.3.1 (to be released soon).

Image

Posted on
Sun May 12, 2019 2:18 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: New Ecolink PIR Sensor appears as Notification Sensor

Indigo 7.3.1 is now available and should fix this problem.

Image

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 7 guests