Zen37 supported maybe?

[xlurkr]

I added a Zen37 wall remote.  The nodes it created are...weird.  I expected the 4 scene buttons to at least have some kind of status, and to have that status change momentarily when the button is pressed.  As you can see from the attached images, those nodes are empty.  And why are the scene control nodes numbered 2,3,6-9?  Maybe it's because direct associations are supported, but only for 1-tap actions?  See the 4th image to understand why I made this guess.

However...

I created a program with "If ZW002 Scene Button 1 is switched On" trigger, and it worked when I pushed the top button.  So I guess everything is OK?

-Tom

[Techman]

The manufactures of Z-wave devices usually include nodes that are specific to a controller.  It's not unusal  to end up with numerous nodes that the UDI controller doesn't use.

You'll have to play with all the nodes to find the ones that are applicable to the UDI Controller.

Most users create a folder to put the unused nodes in. 

[Traditore]

I've just bought the same device. How do you get any button on the remote to turn off a light? It only sends ON commands.

It looks like we could get a toggle function with Groups 6-9, but I don't know how to implement this.

Edited December 9 by Traditore

[brians]

Looks like isy doesn’t support group 4 and group 5 associations for this device that is why numbers are missing. 
The associations only work with other zwave devices. To use buttons to control other things like Insteon you have to make programs variables etc and manually set leds with parameters. I have example using zen32 elsewhere in forums which could be  applicable. Unfortunately isy programming is limited and can run into race conditions and uncertainties due to its execution options (or lack of options) where it restarts program every time is run. 

[Traditore]

Thank you. I gathered a lot of info from your posts in other topics. Conclusion: Insteon scenes are easier for IoP than Z-Wave direct associations.

I ended up creating two programs per button to independently control ON (single press) and OFF (double press). Not ideal, but it works.

[brians]

On 12/9/2024 at 5:11 PM, Traditore said:

Thank you. I gathered a lot of info from your posts in other topics. Conclusion: Insteon scenes are easier for IoP than Z-Wave direct associations.

I ended up creating two programs per button to independently control ON (single press) and OFF (double press). Not ideal, but it works.

You can make a toggle using a state variable. Just make a program that sets the variable 1 or 0 everytime a button is pressed. Then use that variable to trigger a program which turns on/off a light. I think I have example where I did this also.

[Traditore]

I couldn't find your post, and there are lots of posts on variables on the forum for many different situations. But as you suggested, I've just tried something with variables, which I'm not too familiar with. This is probably not the way to do it, but it seems to work in my limited testing.

Lamps ON Copy Copy - [ID 0058][Parent 0054]

If
        'ZY 040 Wall Remote CAC1 / ZY 040 Scene Button 3' is switched On
    And $sZEN37_CAC1_Lamps is 0
 
Then
        Set 'CAC Table Lamps' On
        $sZEN37_CAC1_Lamps  = 1
 
Else
   - No Actions - (To add one, press 'Action')
 

Lamps OFF Copy - [ID 005E][Parent 0054]

If
        'ZY 040 Wall Remote CAC1 / ZY 040 Scene Button 3' is switched On
    And $sZEN37_CAC1_Lamps is 1
 
Then
        Set 'CAC Table Lamps' Off
        $sZEN37_CAC1_Lamps  = 0
 
Else
   - No Actions - (To add one, press 'Action')
 

Those variables will probably get out of sync if I manually turn the light on, so I guess I'll have to add an And ( ) condition to account for that.