Jump to content

Ecolink Z-Wave Door/Window Sensor (DWZWAVE2-ECO) pairing with ISY-994i


aflink

Recommended Posts

Posted

I just bought a Ecolink Z-Wave Door/Window Sensor (DWZWAVE2-ECO), having trouble pairing it with  ISY-994i

 

Ecolink sensor - http://www.amazon.com/gp/product/B00HPIYJWU

 

ISY-994i firmware is version 4.2.18, z-wave version 4.55

 

I set the controller into "include z-wave device", then set the sensor into discovery mode. 

 

Nothing happens. Has anybody paired Ecolink Z-Wave Door/Window Sensor (DWZWAVE2-ECO) with  ISY-994i?

Posted

This may help:

 

1) exclude device first by doing same procedure as below in remove mode.

Then..

2) put ISY in add device mode

3) remove battery from sensor, then put back. Don't put cover on until it pairs.

 

 

 

Sorry for brevity - posted using mobile Tapatalk

Posted

Thanks for the tip. Tried the steps as you suggested, did not work.

 

I have paired a Yale lock previously on this ISY, so I know the ISY works.

Posted

I just spoke with Mike at Ecolink. He said he has sent sensors to Universal Devices to be tested. Did you get any of the Ecolink sensors working?

Posted

After further research with Ecolink this is what we have discovered:

 

Without going into too much detail, the device is going to sleep too fast and the pairing / removal is not happening within the time allowed. The Z-Wave spec is a bit loose on this and every manufacturer is implementing this a bit differently, however the spec specifically says that if a battery operated device sends a wakeup notification frame, the gateway is supposed to look and see if it has anything to send to the device, if it doesn't (per the spec) it is supposed to send a sleep command. Well, Ecolink sends one before the pairing is complete so we respond with a sleep command (because we don't know it's not done yet.)

 

Fear not, it is fixable. Please follow the instructions - most importantly do not put the cover back on until paring is done, this will make the sensor ignore the sleep frames.

 

Instructions:

  1. Place device within 10' of ISY
  2. Remove cover
  3. Remove battery
  4. (optional) open ISY log window and set to level 2 or 3
  5. Put ISY in Remove Z-Wave mode
  6. Replace battery
  7. When the remove dialog box disappears, the device has been removed properly.  If it doesn't remove & replace battery again.  Repeat up to 3 times if it doesn't remove then it's probably already removed.
  8. Remove battery
  9. Put ISY in Z-Wave Add mode
  10. Replace battery
  11. Wait until the device is fully added. 
  12. Now you may replace the cover and put the device in its final location.
  13. If you'd like to heal the network you may while it is in its final location - but remove the cover before you do a heal.

 

This same procedure will work for the Ecolink PIR, Tilt Sensor, and other Ecolink products.

Posted

Mike, thanks for the instructions. Unfortunately, no luck when I followed the steps.

 

Trace below:

 

Wed 04/08/2015 06:59:41 PM : [ZWAVE-TX-NR     ] [0105004B0164D4]

 
Wed 04/08/2015 06:59:42 PM : [uZW-CMD 2       ] Start Exclude
 
Wed 04/08/2015 06:59:42 PM : [ZWAVE-RX        ] ACK
 
Wed 04/08/2015 06:59:42 PM : [ZWAVE-RX        ] [0107004B64010000]...
 
Wed 04/08/2015 06:59:42 PM : [ZWAVE-TX        ] ACK
 
Wed 04/08/2015 06:59:42 PM : Listening for Z-Wave devices to remove from the network
 
Wed 04/08/2015 07:00:06 PM : FYP: Connecting to http://flexyourpower.s3.amazonaws.com/banners/status.xml
 
Wed 04/08/2015 07:00:09 PM : [ZWAVE-TX-NR     ] [0105004B0565D1]
 
Wed 04/08/2015 07:00:09 PM : [uZW-CMD 8       ] Cancel Include/Exclude/Learn
 
Wed 04/08/2015 07:00:09 PM : [ZWAVE-RX        ] ACK
 
Wed 04/08/2015 07:00:09 PM : [ZWAVE-RX        ] [0107004B65060000]...
 
Wed 04/08/2015 07:00:09 PM : [ZWAVE-TX        ] ACK
 
Wed 04/08/2015 07:00:09 PM : Removing Z-Wave devices stopped
 
Wed 04/08/2015 07:00:10 PM : [ZWAVE-TX        ] [01030020DC]
 
Wed 04/08/2015 07:00:10 PM : [ZWAVE-RX        ] ACK
 
Wed 04/08/2015 07:00:10 PM : [ZWAVE-RX        ] [01080120EB1AC511]...
 
Wed 04/08/2015 07:00:10 PM : [ZWAVE-TX        ] ACK
 
Wed 04/08/2015 07:00:10 PM : [ZWAVE-TX        ] [01030005F9]
 
Wed 04/08/2015 07:00:10 PM : [ZWAVE-RX        ] ACK
 
Wed 04/08/2015 07:00:10 PM : [ZWAVE-RX        ] [0104010500FF]
 
Wed 04/08/2015 07:00:10 PM : [ZWAVE-TX        ] ACK
 
Wed 04/08/2015 07:00:18 PM : [ZWAVE-TX-NR     ] [0105004B0166D6]
 
Wed 04/08/2015 07:00:18 PM : [uZW-CMD 2       ] Start Exclude
 
Wed 04/08/2015 07:00:18 PM : [ZWAVE-RX        ] ACK
 
Wed 04/08/2015 07:00:18 PM : [ZWAVE-RX        ] [0107004B66010000]...
 
Wed 04/08/2015 07:00:18 PM : [ZWAVE-TX        ] ACK
 
Wed 04/08/2015 07:00:18 PM : Listening for Z-Wave devices to remove from the network
 
Wed 04/08/2015 07:00:40 PM : [ZWAVE-TX-NR     ] [0105004B0567D3]
 
Wed 04/08/2015 07:00:40 PM : [uZW-CMD 8       ] Cancel Include/Exclude/Learn
 
Wed 04/08/2015 07:00:40 PM : [ZWAVE-RX        ] ACK
 
Wed 04/08/2015 07:00:40 PM : [ZWAVE-RX        ] [0107004B67060000]...
 
Wed 04/08/2015 07:00:40 PM : [ZWAVE-TX        ] ACK
 
Wed 04/08/2015 07:00:40 PM : Removing Z-Wave devices stopped
 
Wed 04/08/2015 07:00:40 PM : [ZWAVE-TX        ] [01030020DC]
 
Wed 04/08/2015 07:00:40 PM : [ZWAVE-RX        ] ACK
 
Wed 04/08/2015 07:00:40 PM : [ZWAVE-RX        ] [01080120EB1AC511]...
 
Wed 04/08/2015 07:00:40 PM : [ZWAVE-TX        ] ACK
 
Wed 04/08/2015 07:00:41 PM : [ZWAVE-TX        ] [01030005F9]
 
Wed 04/08/2015 07:00:41 PM : [ZWAVE-RX        ] ACK
 
Wed 04/08/2015 07:00:41 PM : [ZWAVE-RX        ] [0104010500FF]
 
Wed 04/08/2015 07:00:41 PM : [ZWAVE-TX        ] ACK
 
Wed 04/08/2015 07:00:58 PM : [ZWAVE-TX-NR     ] [0105004B0168D8]
 
Wed 04/08/2015 07:00:58 PM : [uZW-CMD 2       ] Start Exclude
 
Wed 04/08/2015 07:00:58 PM : [ZWAVE-RX        ] ACK
 
Wed 04/08/2015 07:00:58 PM : [ZWAVE-RX        ] [0107004B68010000]...
 
Wed 04/08/2015 07:00:58 PM : [ZWAVE-TX        ] ACK
 
Wed 04/08/2015 07:00:58 PM : Listening for Z-Wave devices to remove from the network
 
Wed 04/08/2015 07:01:05 PM : FYP: Connecting to http://flexyourpower.s3.amazonaws.com/banners/status.xml
 
Wed 04/08/2015 07:01:19 PM : [ZWAVE-TX-NR     ] [0105004B0569DD]
 
Wed 04/08/2015 07:01:19 PM : [uZW-CMD 8       ] Cancel Include/Exclude/Learn
 
Wed 04/08/2015 07:01:19 PM : [ZWAVE-RX        ] ACK
 
Wed 04/08/2015 07:01:19 PM : [ZWAVE-RX        ] [0107004B69060000]...
 
Wed 04/08/2015 07:01:19 PM : [ZWAVE-TX        ] ACK
 
Wed 04/08/2015 07:01:19 PM : Removing Z-Wave devices stopped
 
Wed 04/08/2015 07:01:20 PM : [ZWAVE-TX        ] [01030020DC]
 
Wed 04/08/2015 07:01:20 PM : [ZWAVE-RX        ] ACK
 
Wed 04/08/2015 07:01:20 PM : [ZWAVE-RX        ] [01080120EB1AC511]...
 
Wed 04/08/2015 07:01:20 PM : [ZWAVE-TX        ] ACK
 
Wed 04/08/2015 07:01:20 PM : [ZWAVE-TX        ] [01030005F9]
 
Wed 04/08/2015 07:01:20 PM : [ZWAVE-RX        ] ACK
 
Wed 04/08/2015 07:01:20 PM : [ZWAVE-RX        ] [0104010500FF]
 
Wed 04/08/2015 07:01:20 PM : [ZWAVE-TX        ] ACK
 
Wed 04/08/2015 07:01:38 PM : [ZWAVE-TX-NR     ] [0105004AC16A1B]
 
Wed 04/08/2015 07:01:38 PM : [uZW-CMD 1       ] Start Include
 
Wed 04/08/2015 07:01:38 PM : [ZWAVE-RX        ] ACK
 
Wed 04/08/2015 07:01:38 PM : [ZWAVE-RX        ] [0107004A6A010000]...
 
Wed 04/08/2015 07:01:38 PM : [ZWAVE-TX        ] ACK
 
Wed 04/08/2015 07:01:38 PM : Listening for Z-Wave devices to add to the network
 
Wed 04/08/2015 07:02:05 PM : FYP: Connecting to http://flexyourpower.s3.amazonaws.com/banners/status.xml
 
Wed 04/08/2015 07:02:15 PM : [ZWAVE-TX-NR     ] [0105004A856B5E]
 
Wed 04/08/2015 07:02:15 PM : [uZW-CMD 8       ] Cancel Include/Exclude/Learn
 
Wed 04/08/2015 07:02:15 PM : [ZWAVE-RX        ] ACK
 
Wed 04/08/2015 07:02:15 PM : [ZWAVE-RX        ] [0107004A6B060000]...
 
Wed 04/08/2015 07:02:15 PM : [ZWAVE-TX        ] ACK
 
Wed 04/08/2015 07:02:15 PM : Adding Z-Wave devices stopped
 
Wed 04/08/2015 07:02:15 PM : [ZWAVE-TX        ] [01030020DC]
 
Wed 04/08/2015 07:02:15 PM : [ZWAVE-RX        ] ACK
 
Wed 04/08/2015 07:02:15 PM : [ZWAVE-RX        ] [01080120EB1AC511]...
 
Wed 04/08/2015 07:02:15 PM : [ZWAVE-TX        ] ACK
 
Wed 04/08/2015 07:02:15 PM : [ZWAVE-TX        ] [01030005F9]
 
Wed 04/08/2015 07:02:15 PM : [ZWAVE-RX        ] ACK
 
Wed 04/08/2015 07:02:15 PM : [ZWAVE-RX        ] [0104010500FF]
 
Wed 04/08/2015 07:02:15 PM : [ZWAVE-TX        ] ACK
Posted

I have two of these paired successfully.

 

I had to try several times, and it was necessary to exclude these first (but I purchased them refurbished so I expected this).

Posted

As far as I can tell, the sensor did not communicate to ISY below. Can somebody who knows the trace please confirm?

 

the device was 22 seconds in exclude mode 

 

Wed 04/08/2015 07:00:18 PM : [uZW-CMD 2       ] Start Exclude
Wed 04/08/2015 07:00:18 PM : [ZWAVE-RX        ] ACK
Wed 04/08/2015 07:00:18 PM : [ZWAVE-RX        ] [0107004B66010000]...
Wed 04/08/2015 07:00:18 PM : [ZWAVE-TX        ] ACK
Wed 04/08/2015 07:00:18 PM : Listening for Z-Wave devices to remove from the network
Wed 04/08/2015 07:00:40 PM : [ZWAVE-TX-NR     ] [0105004B0567D3]
Wed 04/08/2015 07:00:40 PM : [uZW-CMD 8       ] Cancel Include/Exclude/Learn
Wed 04/08/2015 07:00:40 PM : [ZWAVE-RX        ] ACK
Wed 04/08/2015 07:00:40 PM : [ZWAVE-RX        ] [0107004B67060000]...
Wed 04/08/2015 07:00:40 PM : [ZWAVE-TX        ] ACK
Wed 04/08/2015 07:00:40 PM : Removing Z-Wave devices stopped
Wed 04/08/2015 07:00:40 PM : [ZWAVE-TX        ] [01030020DC]
Wed 04/08/2015 07:00:40 PM : [ZWAVE-RX        ] ACK
Wed 04/08/2015 07:00:40 PM : [ZWAVE-RX        ] [01080120EB1AC511]...
Wed 04/08/2015 07:00:40 PM : [ZWAVE-TX        ] ACK
Wed 04/08/2015 07:00:41 PM : [ZWAVE-TX        ] [01030005F9]
Wed 04/08/2015 07:00:41 PM : [ZWAVE-RX        ] ACK
Wed 04/08/2015 07:00:41 PM : [ZWAVE-RX        ] [0104010500FF]
Wed 04/08/2015 07:00:41 PM : [ZWAVE-TX        ] ACK
Wed 04/08/2015 07:00:58 PM : [ZWAVE-TX-NR     ] [0105004B0168D8]
 
  • 8 months later...
  • 3 weeks later...
Posted

Using these sensors and same problem as jeffl012 -- the sensors always report ON/tripped (ST=100).  They expose property ST, BATLVL and DON, though the value of DON (at least via the REST interface) is empty.

 

Are these examples of "multi-node" devices?  They are pretty simple.

 

FYI - in my case, the ISY is the secondary ZWave controller and the primary ZWave controller (Vera3) recognizes them and shows when the state changes (door/gate/window opens or closes).  Watching all the properties and the device state via java the ISY Admin console, the state/status of the device never changes.

 

Is there any info I can send (device XML via REST or proeprties, etc) to help diagnose this?

 

Other zwave devices (including temp/humidity sensors, door locks, power sensors and thermostats) work great via the ISY.

 

Gerry

Posted

Hi Gerry,

 

I am not sure I understand the question. DON is a command so it should not have a value unless it's being sent in an event.

 

Are you saying that ST is always 100 regardless of it being tripped?

 

With kind regards,

Michel

Posted

Correct.  The ST property shows 100 all the time and never changes.  That is confirmed from the REST interface and via the Java admin console.

 

Meanwhile, my Zwave primary (Vera3 unit from MiCaseverde) shows that correct state of the switch and updates when the window/door/etc opens and closes.  So it's sending something.

 

Gerry

Posted

Yes -- I'm migrating away from the vera3, but not free yet.

 

All other zwave devices -- 2 thermostats, 2 door locks, 10 temp/humidity sensors and a motion sensor all work 100% correctly with the ISY seeing changes and reporting them correctly.  Only these ECOLINK door switches (of which I have 6).

 

Gerry

Posted

Some devices will only send status and to their primary controller, others (where the manufacturer has not paid for the Lutron patent) don't send status at all. If these are changed outside of the ISY it will be necessary to query the device before the state will show correctly.

 

Have you tried querying the device on the ISY to see if it gets correct status?

 

The MCV has a method of polling that circumvents the Lutron patent.

Posted

Any update on what might be going on?  Has anyone else got them reporting the accurate state?

 

Getting these sensors working is the last thing I need to do before I can complete my migration from the Vera3 to ISY for all ZWave control (after which I have a vera3 available reaaaaaaalll cheap!).

 

Gerry

Posted

Some devices need to have parameters tweaked to send reports. I have an Aeon switch that reports power usage, except it didn't report until I tweaked some parameters. To find out what to tweak is an interesting game - you need the device zwave specs. I often start with searching for a definition of parameters (sites like pepper.net) to see if anyone has figured them out.

Posted

I do understand that some devices need options set, but as I reported earlier, the Vera3 is seeing the device change status (Vera is the primary, ISY is the secondary).  The changes happen immediately with the change in state of the device, so it's not the Vera polling, but actual events being delivered.

 

Plus the ISY not only doesn't report state, but when the device is queried, it still doesn't change the reported state.

 

This class of ZWave device is the only one that is not showing changes (events or from queries).  My ecolink motion sensors, kwikset door locks, Honeywell thermostats and everspring temp sensors are all working as you'd expect (reporting events and responding to being queried with updates).

 

Only this device doesn't ever change state (and I have 6 of them, so its unlikley to be a unit-specific failure -- they all report correctly to/on the Vera3).

 

Gerry

Posted

Howdy,
 

I guess it could be, but not sure how I'd determine that. It's a very simple device the shows as a "Binary Switch" and really only has an on/off or open/close state and battery level.  It doesn't report anything else.

 

How would I go about determining if it is a multi-sensor?

 

Gerry

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...