Jump to content

ZEN32 Z-wave scene controller behavior


Andy P

Recommended Posts

Posted

I am in the process of moving my z-wave devices from Hubitat to the z dongle on EISY (5.6.0, 5226, 21100), and have a lot working but some strange behaviors.

I followed the process of exclusion, factory reset then inclusion to get the best results.

The ZEN32 has one button (called the relay and also called button 5) and 4 smaller buttons are called 1 through 4.

Adding the device creates 11 nodes:

  • 1 node for the relay called _1 Binary Switch
  • 5 nodes for the small buttons plus the relay called 201N001 through 201N005 Central Scene Control Button
  • 5 nodes for the small buttons plus the relay called 252N002, 4, 6, 8 and 10 Basic Association

So, the normal operation of the big button does cause the Binary Switch node to change from On to Off and back again, and I can also control it through programs - all good.

Pressing small button 3 generates a log entry.

Sun 06/25/2023 08:27:09 AM : [D2D EVENT       ] Event [ZY017_201N003] [DON] [0] uom=115 prec=0
Sun 06/25/2023 08:27:09 AM : [ZY017_201N003   ]      DON   0 (uom=115 prec=0)
Sun 06/25/2023 08:27:09 AM : [ZWAVE-CTL-EVENT ] Basic Set from 17.0 unmapped (ignored)

So, it says unmapped ignored (although it will trigger program execution).

First questions  - when I turn on zwave -> detect button presses I can get the dialog box to pop up, but there is no node than allows me to 'right click on an association only node' and map the button - so does that actually work?

Second question - when I press button 3 again, it again generates a DON event. No matter which button I press, or how many times, they only generate DON events, never DOF. I reviewed the advanced settings for the device and there is no setting that would appear to cause this behavior. SO, how do I get this device to generate both DON and DOF events?

One side effect of this behavior is that when I assign a button to a SCENE as a controller and add another switch to that scene, I can turn that Scene ON but cannot turn the scene back off using the ZEN32 buttons. I also tried using the Basic Association nodes, but they don't seem to generate any events at all in the log (at level 3).

My work around right now was to create a program that basically uses the DON events to toggle the other switch - here using button 1 which toggles the loft lights when the stairs button is pressed repeatedly. I am using 'switched on' instead of 'status on' because if you use 'status on' the program just goes into a loop turning itself on and off.

Zen32 - [ID 0018][Parent 0007]

If
        'Shop Stairs-S1' is switched On
    And 'Shop Loft-Binary' Status is Off
 
Then
        Set 'Shop Loft-Binary' On
 
Else
        Set 'Shop Loft-Binary' Off
 

I can live with the work around, but it means that the LED indicator is out of sync sometimes with the on/off status so I would really like to get the buttons to generate off events and get the scenes working.

Any ideas? I am reaching out to ZOOZ as well for firmware updates.

Andy

Posted (edited)

Those buttons are designed like that, they are to turn scenes on. There is no off. They are meant to just do something when pressed, or multiple times etc.

Zen32 is sorta crippled and above link I got working ok in ISY with LED sync. I recommend using programs and stay away from scenes. Z-Wave Basic Association is not recommended (even by Zooz). I have since switched over my Z-Wave to Home Assistant, which my automation is similar idea to the IoX programs.

Your Hubitat probably had a plugin or something that made it easy to setup, just like Home Assistant has blueprints which others made that can do the same.. but nothing like that for IoX... programs haven't evolved much at all in the 15 years I have been using.

Edited by brians
Posted

OK, Thanks, very helpful to confirm that the scene buttons only turn on and I didn't mess anything up.

Based on this, I have changed my usage as follows.

  • created a scene with the loft light switch
  • added shop stairs button 2 as a scene controller to turn the scene ON.
  • added shop stairs button 4 as a scene controller to turn the scene OFF.
  • set the color of button 2 LED to green (parm 8=2)
  • set the color of button 4 LED to red (parm 10=3)
  • created a program that runs when the loft light status changes to turn the button leds on and off

So now, I can turn on the loft light with button 2. Turn off the loft light with button 4 and when the program runs, it either turns on the green light on button 2 or the red light on button 4 and turns the other light off.

Here is the program - had to add the waits to get it to work correctly

Loft light status - [ID 0009][Parent 0007]

If
        'Shop Loft-Binary' Status is On
 
Then
        Wait  1 second
        Set 'Shop Stairs-Binary' Set Configuration Parameter 3 = 3
        Wait  1 second
        Set 'Shop Stairs-Binary' Set Configuration Parameter 5 = 2
 
Else
        Wait  1 second
        Set 'Shop Stairs-Binary' Set Configuration Parameter 5 = 3
        Wait  1 second
        Set 'Shop Stairs-Binary' Set Configuration Parameter 3 = 2
 

Doing the same for the attic light so this effectively gives me a switch that can turn the stairs light on or off with the big button and turn the loft and attic lights on and off with each using a pair of small buttons and including indicators of being on or off on those buttons.

Thanks for your help!

Andy

Posted

Ya I am not sure why have to put delays in with IoX. It seems it is not able to queue commands internally. They should fix this - no reason to need delays. I had this issue with many different things and caused unreliability in programs. Also would be great if they had option for programs to complete without being rerun again by an action. 

Guest
This topic is now closed to further replies.

×
×
  • Create New...