These guys are having a z-wave sale this weekend:

http://www.thesmartesthouse.com/

 

I bought the latest Aeon multi-sensor from them during the pre-order and was pleased with their response, and some theirs come with free batteries

 

Also, I see the Aeon has a dry contact sensor:

http://www.thesmartesthouse.com/collections/aeotec-by-aeon-labs/products/aeotec-by-aeon-labs-z-wave-plus-dry-contact-sensor-gen-5

which isn't even mentioned on Aeon's site yet.  Hopefully these work with the ISY so I can replace some of my IOLink's with them!  And it's OTA firmware upgradeable!

 

And, it looks they are releasing a new garage door controller as week.

http://aeotec.com/z-wave-garage-door

 

- Jim

Holding out some hope for the Aeon Touch Panels.  Hopefully will be easier to integrate than a Wink Relay and at least reasonably useful.

Holding out some hope for the Aeon Touch Panels. Hopefully will be easier to integrate than a Wink Relay and at least reasonably useful.

I've been curious about those as well. I ordered a couple dry contact sensors so hopefully the work with the ISY.

The multi sensors intrigue me right now. Guess its time to add ZWave. Was hoping the newer ZWave chip/module would come for the ISY but there has t been any word on it so...

Also, I see the Aeon has a dry contact sensor:

http://www.thesmartesthouse.com/collections/aeotec-by-aeon-labs/products/aeotec-by-aeon-labs-z-wave-plus-dry-contact-sensor-gen-5

which isn't even mentioned on Aeon's site yet.  Hopefully these work with the ISY so I can replace some of my IOLink's with them!  And it's OTA firmware upgradeable!

 

 

 

I don't see how this device is any different than a Insteon Trigger Linc? Which offers the same capability to connect any dry contact switch to it and initiate a signal in the network.

 

Unlike a I/O link both devices can not initiate a device to be turned on-off. All it does is monitor a open - close state and send the signal to the controller / linked device.

 

Unless I am missing the obvious here?

Pretty much the same, but the trigger linc, or whatever it is now called does not have a low battery sensor, and depending on the version, doesn't even have a heartbeat.

All new open - close / trigger lincs do come with a heart beat node. Again both devices can not initiate another device to come on - off directly as it's not powered.

 

 

Ideals are peaceful - History is violent

Edited September 6, 201510 yr by Teken

Holding out some hope for the Aeon Touch Panels.  Hopefully will be easier to integrate than a Wink Relay and at least reasonably useful.

 

 

I've been curious about those as well. I ordered a couple dry contact sensors so hopefully the work with the ISY.

 

 

I saw the specs of the touch panels on Amazon today.  Only works with their micro switches as a fancy glass companion switch.

Has anyone had success with the Aeon ZW097A dry contact sensor on the ISY994i? I'm new to the ISY994i and could not get the ZW097A to provide a status change that was recognized by the ISY994i. Gave up on it and had an Ecolink door/window sensor using the wired loop option (rather than the magnetic switch option) working in only a few minutes using the same simple program.

I am resuscitating this thread.  I have paired an Aeon dry contact sensor (gen5) with the ISY994.   It shows up as a notification sensor (battery level) and a binary sensor (on/off).  It responds correctly to queries about the status of the contact.  However I am not able to automatically notify the ISY994 about a state change. i.e. report when the contact goes from open to closed or vice-verse without having to initiate a query from the ISY994.  Has anyone gotten this to work?  Is the sensor supposed to work this way?  Thanks. 

I am resuscitating this thread.  I have paired an Aeon dry contact sensor (gen5) with the ISY994.   It shows up as a notification sensor (battery level) and a binary sensor (on/off).  It responds correctly to queries about the status of the contact.  However I am not able to automatically notify the ISY994 about a state change. i.e. report when the contact goes from open to closed or vice-verse without having to initiate a query from the ISY994.  Has anyone gotten this to work?  Is the sensor supposed to work this way?  Thanks. 

 

I got this working yesterday.   I think what I had to do was set the zwave parameter #121 to the value 272.  Got that from:

 

https://github.com/OpenZWave/open-zwave/blob/master/config/aeotec/zw097.xml

 

Doing that made it send an even that actually was able to work.    

That's encouraging. Can you share how exactly you set those parameters from the ISY? I am completely new at this having acquired an ISY under a month ago. I am okay at programming, but new to home automation.

Okay I figured out that if I double click (using a MacBook) the Z-wave device on the ISY network page then it allows me to set the configuration parameters.  The suggestion by dkulp did not work so far, but it might have been operator error on my part.  I will post if I get it to work, or if I figure out anything new.  Great forum!

Chris helped me with this device per the following:

 

To do this, make sure the sensor is awake and then  right+click on the device in the device tree and select

Z-Wave -> Set Configuration Parameter

 

Parameter Number = 121, Parameter Size = 4, Parameter Value = 16

 

Chris Jahn, CTO

Universal Devices Inc.

 

Not sure about parameter value actions but this works for me.

Sigh.  Still no luck with the Aeotec dry contact sensor.  Setting configuration parameter 121 to 16 (size 4) or to 272 (size 4) makes no difference.  I still don't get an automatic update of the sensor status.  Strangely enough my battery level went from 99% yesterday to 41% today.  Not encouraging.  Also when I close the contact, the red lamp on the sensor flashes for a long time.  I have had to open the contact to get it to stop flashing.  I suspect this is the cause of my power drain.  Maybe it's time to give up on this sensor.  The Ecolink garage door tilt sensor has worked quite nicely so far, perhaps it can be repurposed as a dry contact sensor with a bit of soldering.

It really sounds like something is wrong with the sensor, or something is strange with the contact which causes the sensor to flash red.  I use these in a few places and they have worked perfectly with Param 121 set to 272 and they are reporting battery status as well https://docs.google.com/document/d/108vJYiB7BZdLT5d8w8UAHrT18S_QfGMk1NWngz7U1_I/edit?usp=sharing  

Thanks so much for this.  Fixed my issue and now I get useful notifications.  I read the github and it has good info, but dies anyone know of any more parameter info?  I am looking to get it to send periodic sensor status update.  I am using this on a sump and I don't want to risk missing a single notification should it be triggered.

Chris helped me with this device per the following:

 

To do this, make sure the sensor is awake and then  right+click on the device in the device tree and select

Z-Wave -> Set Configuration Parameter

 

Parameter Number = 121, Parameter Size = 4, Parameter Value = 16

 

Chris Jahn, CTO

Universal Devices Inc.

 

Not sure about parameter value actions but this works for me.

I tried again and found success at last.  I am not sure what did it, but here is roughly what I tried. I apologize for the stream of consciousness style writeup.

 

I deleted the dry contact sensor from the ISY network page.  I did a network heal during which I noticed some sort of error:

[ZWAVE-DB ] Unexpected NULL database for uid=7 0x07

The dry contact sensor was number 7 on the list prior to deleting it.

 

I then thought I should have excluded the device first before deleting it from the network page, so I tried that, but still get that error during the network heal.  The network heal completes successfully except for that error.

 

I then included the device on the network.  It enumerated to device 8 skipping its old number 7.

 

I then reset to factory setting by setting parameter 255 to 0.  One thing you have to do is press the round button on the back of the module for 3 sec to wake it up before trying to set any parameters.

 

I then set parameter 121 to 16 and parameter 111 to 86400 (seconds, daily battery reports I hope).  I will update the forum once I confirm I am actually receiving daily battery reports.

 

After all that it seems to function as intended.  The status updates when the contact changes state (closed to open or open to closed).  Hooray!