Ecolink Z-Wave Plus Flood/Freeze Sensor

Posted on
Sat Mar 09, 2019 10:25 am
Sjack offline
Posts: 8
Joined: Mar 05, 2019

Ecolink Z-Wave Plus Flood/Freeze Sensor

I'm trying to make a plugin for the Ecolink Z-Wave Plus Flood/Freeze Sensor.
One of the challenges I found is to interpret the raw data received.
I found out some by looking at example plugins in the SDK and enabling "Show debug logging in Event Log window".

I.E. Byte 05 is the nodeId Byte 7 is the command class, etc.
So I found Byte: 1, 5, 7, 13, 14 see code section.

Code: Select all
                                                        0x10 = 16 parameters to follow (1+16=17)
                                                        |           nodeID      
                                                        |           |     cmdClass Alarm 0x71   
                                                        |           |     |                 typeExt = 0x05 water
                                                        |           |     |                 |  valueExt 0x04 = no Water Detected
                                                        |           |     |                 |  |      
No Water Detected                                    0  1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17
   Z-Wave Debug      RCVD requestAlarmSensorStatus: 01 10 00 04 00 05 0A 71 05 00 00 00 FF 05 04 00 00 6E
   Z-Wave Debug      . .  requestAlarmSensorStatus: node 005, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug      . .  requestAlarmSensorStatus: typeExt 5, valueExt 4, classSubKeyExt 7100000504


In the other plugins I have seen testing on other bytes but I could not interpret why or what. I also searched the web, but could not find the details of these messages.
Can someone direct me to this information please.

By the way I'm learning Python at moment although have experience, listed in decreasing skills, with: C, C++, shell scripting, perl, PHP, Java...

Thanks and regards,
Jacob

Posted on
Sat Mar 09, 2019 6:29 pm
Dual offline
Posts: 259
Joined: Feb 05, 2019

Re: Ecolink Z-Wave Plus Flood/Freeze Sensor

Why a plug-in? You can just use Match Raw Packet if it is an unsupported device to red the state of the device when it sends a Z-Wave message to the controller. Have you tried including it in your network already?


Sent from my iPhone using Tapatalk

Posted on
Sun Mar 10, 2019 6:14 pm
Sjack offline
Posts: 8
Joined: Mar 05, 2019

Re: Ecolink Z-Wave Plus Flood/Freeze Sensor

I have included it in the network, that is how I got the debug info.
It is included as an Notification Sensor and gives the Battery status when you press status report:
Code: Select all
 Z-Wave Debug                    SENT requestAlarmSensorStatus: 01 09 00 13 05 02 71 04 25 18 AA
   Z-Wave                          sent "Flood detector Utility Room" status request
   Z-Wave Debug                    SENT requestBatteryLevel: 01 09 00 13 05 02 80 02 25 19 5C
   Z-Wave Debug                    RCVD requestBatteryLevel: 01 09 00 04 00 05 03 80 03 63 14
   Z-Wave Debug                    . .  requestBatteryLevel: node 005, level 99
   Z-Wave                          received "005 - Flood detector Utility Room" status update battery level 99%


When I added the second sensor I have the only option to choose is "Notification Sensor":
Screenshot 2019-03-10 at 18.56.15.png
Sync option
Screenshot 2019-03-10 at 18.56.15.png (248.93 KiB) Viewed 1010 times


The log entry is here:
Code: Select all
   Z-Wave                          Syncing - started for "003 - Notification Sensor"
   Z-Wave Debug                    SENT getNodeNeighbors: 01 06 00 80 03 01 01 7A
   Z-Wave Debug                    RCVD getNodeNeighbors: 01 20 01 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5E
   Z-Wave Debug                    . .  getNodeNeighbors: nodeId 003, neighbors: - none -
   Z-Wave                          Syncing - retrieved module neighbors list: - none -
   Z-Wave                          Syncing - assigning return route to "003 - Notification Sensor"
   Z-Wave Debug                    SENT assignReturnRoute: 01 05 00 46 03 01 BE
   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 003, success 1
   Z-Wave                          Syncing - assigned return route
   Z-Wave Debug                    SENT requestNodeInfo: 01 06 00 60 03 24 1A A4
   Z-Wave Debug                    RCVD nodeInfoFrame: 01 14 00 49 84 03 0E 04 07 01 5E 86 72 5A 73 80 30 71 85 59 84 33
   Z-Wave Debug                    . .  nodeInfoFrame: node 003, combined class list: 20v1 80v1 84v1 85v1 86v1 30v1 71v1 72v1 73v1 59v1 5Av1 5Ev1
   Z-Wave Debug                    SENT requestManufactureInfo: 01 09 00 13 03 02 72 04 25 1B AC
   Z-Wave Debug                    RCVD requestManufactureInfo: 01 0E 00 04 00 03 08 72 05 01 4A 00 05 00 10 D7
   Z-Wave Debug                    . .  requestManufactureInfo: node 003, manufacturerId 014A, productId 00050010
   Z-Wave Debug                    . .  requestManufactureInfo: Ecolink, Notification Sensor
   Z-Wave                          Syncing - retrieved manufacture and model names: Ecolink - 014A, Notification Sensor - 00050010
   Z-Wave Debug                    SENT requestVersInfoGen: 01 09 00 13 03 02 86 11 25 1C 4A
   Z-Wave Debug                    RCVD requestVersInfoGen: 01 0F 00 04 00 03 09 86 12 06 04 26 0A 09 FF 00 B2
   Z-Wave Debug                    . .  requestVersInfoGen: node 003, protoVers 4.38, appVers 10.09
   Z-Wave                          Syncing - retrieved protocol version 4.38, app version 10.09
   Z-Wave Debug                    SENT requestVersInfoCmdClass: 01 0A 00 13 03 03 86 13 84 25 1D CF
   Z-Wave Debug                    RCVD requestVersInfoCmdClass: 01 0A 00 04 00 03 04 86 14 84 02 E2
   Z-Wave Debug                    . .  requestVersInfoCmdClass: node 003, class command 84 using version 2
   Z-Wave Debug                    . .  requestVersInfoCmdClass: node 003, combined class list: 20v1 80v1 84v2 85v1 86v1 30v1 71v1 72v1 73v1 59v1 5Av1 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 71v1 72v1 73v1 59v1 5Av1 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 03 02 84 05 25 1E 5E
   Z-Wave Debug                    RCVD requestWakeInterval: 01 0C 00 04 00 03 06 84 06 00 01 2C 01 5C
   Z-Wave Debug                    . .  requestWakeInterval: node 003, interval 5 minutes, wakeTarget 001
   Z-Wave                          Syncing - retrieved wake interval of 5 minutes
   Z-Wave Debug                    SENT setWakeInterval: 01 0D 00 13 03 06 84 04 00 0E 10 01 25 1F 41
   Z-Wave                          Syncing - device "003 - Notification Sensor" wake interval changed to 60 minutes
   Z-Wave Debug                    SENT requestAssociationGroupCount: 01 09 00 13 03 02 85 05 25 20 61
   Z-Wave Debug                    RCVD requestAssociationGroupCount: 01 09 00 04 00 03 03 85 06 01 70
   Z-Wave Debug                    . .  requestAssociationGroupCount: node 003, group count: 1
   Z-Wave Debug                    SENT requestAssociations: 01 0A 00 13 03 03 85 02 01 25 21 64
   Z-Wave Debug                    RCVD requestAssociations: 01 0C 00 04 00 03 06 85 03 01 01 00 01 75
   Z-Wave Debug                    . .  requestAssociations: node 003, group: 1, num associations: 1, max associations: 1, replies left: 0
   Z-Wave Debug                    . .  requestAssociations: node 003, group: 1, associations: [1]
   Z-Wave                          Syncing - retrieved group 1 associations: [1]
   Z-Wave                          Syncing - group 1 association to interface already exists (skipping)
   Z-Wave Debug                    SENT requestBatteryLevel: 01 09 00 13 03 02 80 02 25 22 61
   Z-Wave Debug                    RCVD requestBatteryLevel: 01 09 00 04 00 03 03 80 03 63 12
   Z-Wave Debug                    . .  requestBatteryLevel: node 003, level 99
   Z-Wave                          Syncing - retrieved battery level of 99%
   Z-Wave                          Syncing - created device "003 - Notification Sensor"
   Z-Wave                          Syncing - complete
   Z-Wave Debug                    SENT requestAlarmSensorStatus: 01 09 00 13 03 02 71 04 25 23 97
   Z-Wave Debug                    terminatingSyncUI
   Z-Wave                          sent "003 - Notification Sensor" status request
   Z-Wave Debug                    SENT requestBatteryLevel: 01 09 00 13 03 02 80 02 25 24 67
   Z-Wave Debug                    RCVD requestBatteryLevel: 01 09 00 04 00 03 03 80 03 63 12
   Z-Wave Debug                    . .  requestBatteryLevel: node 003, level 99
   Z-Wave                          received "003 - Notification Sensor" status update battery level 99%


When I select the Edit Device Settings I get the Configure On/Off Sensor Module dialog box. See Attached "Edit Device Settings"
I can not select the device in the Modify Configuration Parameter dialog box.
Screenshot 2019-03-10 at 19.10.10.png
Modify Configuration Parameters:
Screenshot 2019-03-10 at 19.10.10.png (160.39 KiB) Viewed 1010 times
Attachments
Screenshot 2019-03-10 at 19.05.02.png
Edit Device Settings
Screenshot 2019-03-10 at 19.05.02.png (232.54 KiB) Viewed 1010 times

Posted on
Sun Mar 10, 2019 6:16 pm
Sjack offline
Posts: 8
Joined: Mar 05, 2019

Re: Ecolink Z-Wave Plus Flood/Freeze Sensor

Oops hit the wrong button.

To complete my respons: where do I find that "Match Raw Packet"?

Thanks and regards,

Posted on
Sun Mar 10, 2019 6:55 pm
matt (support) offline
Site Admin
User avatar
Posts: 21417
Joined: Jan 27, 2003
Location: Texas

Re: Ecolink Z-Wave Plus Flood/Freeze Sensor

In this case the pattern to use in the Trigger would look like this:

* 71 05 00 00 00 FF 05 04 *

Image

Posted on
Sun Mar 10, 2019 7:28 pm
Sjack offline
Posts: 8
Joined: Mar 05, 2019

Re: Ecolink Z-Wave Plus Flood/Freeze Sensor

Did not know that, works as charm thank you very much. :D

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 7 guests

cron