ISY 5.3.0

Most people might be aware of this problem/solution. I wasn't until last weekend so thought I'd document this in case some are still having problems with Z-Wave and Control program triggers.

I'm using a Homeseer WD200+ switch (v5.14 firmware) in an entry hallway. I rely on being able to detect "Control" conditions in order to properly trigger entry and exit programs. Sometime in the recent ISY update past, "Control" stopped triggering my programs. While looking through this, I discovered a new feature UDI added to the device Z-Wave menu: "Add/Refresh Button Press Node."

I clicked to add this new "Detect Button Press" node to my WD200+ Hallways switch and then used this new node as the Control test condition in my programs. WORKS PERFECTLY. Just to be clear, my issue is with triggering udi programs. I have not tried using a button press node to trigger scenes and am not sure this will work for those needing a z-wave scene controller.

 

Edited November 6, 20204 yr by gviliunas
Clarify that I only tested for triggering programs, not scenes

4 minutes ago, gviliunas said:

ISY 5.3.0

Most people might be aware of this problem/solution. I wasn't until last weekend so thought I'd document this in case some are still having problems with Z-Wave and Control program triggers.

I'm using a Homeseer WD200+ switch in an entry hallway. I rely on being able to detect "Control" conditions in order to properly trigger entry and exit programs. Sometime in the recent ISY update past, "Control" stopped triggering my programs. While looking through this, I discovered a new feature UDI added to the device Z-Wave menu: "Add/Refresh Button Press Node."

I clicked to add this new "Detect Button Press" node to my WD200+ Hallways switch and then used this new node as the Control test condition in my programs. WORKS PERFECTLY.

 

I was told about this by UDI a few weeks ago, but in my case it does not work. I also believe that UDi is working at resolving the issue.

@asbril,

Yes, we are working on it and it's almost done.

With kind regards,
Michel

12 hours ago, gviliunas said:

Most people might be aware of this problem/solution.

I don't know about most people, but I have posted more than a couple of times that my z-wave devices do not respond to "control" conditions, as well as opened a ticket with UDI about a z-wave device and made such a point.  If this response was ever given, I have completely missed it.

I consider myself mostly unknowledgeable on things Z-wave, including nodes, associations, groups, and whatever else applies.  I have, simply, treated z-wave devices as I would have insteon and been less than fully satisfied with the results.  Along with lack of control conditions, neither could I successfully use them as a scene controller.  

FYI...I followed your solution and, yes, I seem now to be able to use a z-wave device as part of a control condition in a program.  I am still investigating whether I can use it as a scene controller.

Edit update...So, the newly-added custom button press node sorta acts as a scene controller.  I added it to a scene that includes a micro-module and a keypad button.  The micro module responds to the z-wave node command, but the keypad button does not.  Interestingly, the node does not act as a scene responder, so I must also keep the primary z-wave node/device in the scene, as well.  Still not quite right, in my view.

Edited November 6, 20204 yr by oberkc

@oberkc,

Most of this issues are solved and will be in the new release shortly.

With kind regards,
michel

8 hours ago, Michel Kohanim said:

Most of this issues are solved and will be in the new release shortly.

I look forward to seeing whether this update solves the problems that I am having.