brians

Presuming you have button one controlling a relay with basic assoc... When you press button one on Zen32 with direct scene assoc which turns a relay on. Then you turn said relay off not using the button but instead using AC. What happens when you press button one again on Zen32? Does the Zen32 believe it's still on and tries to turn it off again, and required a second button press to actually turn on? In other words, I wonder if Zen32 has an internal state that keeps track of the buttons being on or off?!? For dimming yes it appears ZMatter is missing the Basic Assoc Nodes eg. button one would be Group 5 etc.

Nice that it works. I would be curious though if the Zen32 sends an on/off based on its internal sync of what it knows the controlled switch is currently on/off, OR does it send some sort of toggle command to the ZWave switch. If you turn the relay on/off independent of the Zen32, do you then have to press the button on Zen32 twice? Also the relays look neat, Zooz has Zen51 and Zen52 but one person reported issue with Zen52 on the ZMatter unable to include.

Is there any update on this for Zen52 since latest IoX update or does it still not work?

I didn't see anything in that link how you did it, if you figured out zwave basic associations for zen32 to control other zwave devices without having to use programs then please post here.

This thread we are discussing is actually how to do Basic Associations on ZMatter and from what I read you haven't tried yet with the Zen32. I would forget the relay button for now and focus on the little buttons. Please read the first posts in this thread how I explain basic associations work in scenes to control other zwave devices, and see how it would apply to the Zen32. Afterwards, the following should make sense... The Zen32 has basic association 2,4,6,8,10 nodes that could add one for testing to a scene along with a zwave switch node, so select one to test then select its node on left, then click on the zwave switch node on right in scene, and then using the pulldown and selecting zwave basic mc. After doing this see if the switch turns on/off with the button you used to test. If that works then can try more tests to work on led sync issues etc. There may be a chance that it only turns the switch on and not off, I am curious if it toggles though.

Ok I’ll re interview and then restart ac. Just to clarify I should see one of those nodes light up when detects motion ?

What happens when you place one of the Basic Assoc nodes into the scene with another Z-Wave switch? Are you able to set the Z-Wave Basic MC option in pulldown? If so, does it turn on/off the switch? With old ZWave 500 on ISY it did not do basic associations so I had a bunch of programs and variables that would keep track of state of each switch and turn on/off the devices I wanted to, and keep LEDs in sync. I am hoping with basic assoc that part is unneeded (but still need program to sync LEDs... see below) To set colors you can do here: https://www.support.getzooz.com/kb/article/608-zen32-scene-controller-advanced-settings/ Use parameters to turn the buttons off with press by default. You would have to use additional programs that detect the state of the lights which each button controls, and turn the led on/off appropriately using the parameters. I have to do this with Insteon and keypadlincs (and even switchlincs) too if I control a light manually - ie. if I have a scene linked with a lamp as a responder/controller, if I turn the lamp on by itself from AC, a program, UD Mobile, Alexa etc. the keypadlinc does not light up, and I use a program that detectes this and keeps in sync. ie. parameter 2 is for button one... set to 2 always off when light is off, and set to 3 always on when light is on, parameter can choose the color.. or modify the program to make it red for off green on etc.

There seemed to be a bug before where the big button would report turned on in ISY when any of the other little buttons were pressed and it would trigger programs or scenes I had setup for big button everytime little one was pressed.. I would like to know if this is still the case with ZMatter.

Of course you can certainly change the led colors. I guess the zen32 is not really designed for scene control with direct associations. All the points that you bring up like leds doing out of sync are also issue using other controllers eg. Home assistant. It’s just that the zen32 is junk. Please let me know if pressing any of the little buttons makes it appear that the big button is on (it doesn’t really turn on the relay just makes it appear on) - tbis was the biggest issue I had with it before on zoos zwave dongle and wondering if it’s fixed. It’s easy to change the button colors but should start another thread since this is about basic association. I had setuo before with on off toggles controlling lights with leds in sync even from a remote light but was that big button always appear to turn on pressing other buttons issue which made me send it back.

Mine don’t seem to do this. Did you have to update interview or reinclude?

I am running a Polisy and all my node servers seem to be working, but I am not running any that both of you are: Opensprinklier Ecobee Envisalink DSC Timedata Notifications

Sounds like an issue with PG3 since these are node servers. I would check if PG3 is running correctly.

Yes it is necessary because if you reboot your EISY, all the default states of devices are in unknown state and may not operate correctly until a light/device is manually turned on or off once in AC, or queried. Query on start makes sure that IoX knows the state of all devices. I think actualy it is more for toggle buttons in things like homebridge/homekit, UD Mobile, Alexa, Google etc. that has a button to turn on/off... if it is in an unknown state you will not be able to turn on or off this way until it is queried. IoX keeps track of all states but can get messed up so that is why it runs at 3am by default to update itself. It may be an intensive operation on the network and affect performance of other programs etc so presumes you are sleeping at this time and not notice.

That is not abnormal, the node ID which is MAC address has changed so just edit that line and select Your Devices My LIghting or whatever it is called If you restored from backup it is probably still called My Lighting but I know my default Polisy it was named Polisy, and EISY I presume is EISY.. .restoring an ISY backup will change it to whatever it was My LIghting was original name for it.

Updated no issues. Release notes do not mention ZEN17, only ZEN16. Is there support for ZEN17? Preliminary testing via update with interview did not add anymore sensor nodes as expected.

I am updating now from work remotely... wish me luck Updated no issue... I lists support for Zen16 not for Zen17 but I presume they may be similar. So I set parameter on 2 and 3 to 10 (for dry contact sensor) and did an update with interview but unfortunately no new nodes appeared for sensors. I included my Zen17 with no security initially, which is a criteria for the release notes, but maybe I have to exclude/include again - will try to see if that works.

It mentions a bug fix that fix some schlage logs.

To follow up on this, I realized that in my testing other day that since I had set parameter 10 and 11 to 1 which isolates the sensors, my program was therefore not being triggered because due to this issue I can only currently read the relay. What is missing is the two extra sensor nodes that should be created. I since set those parameters back to default value of 1 which turn on/off the relays with sensor input. So it seems like other parameters are working eg. if I set to parameter 2 to 3 which is momentary for garage door it works momentary.. just missing the sensor nodes.

I still do not see any new nodes for sensors when I set the parameters 2 and/or 3. When I set parameter 2 and 3 to 10, it puts the relays 1 and 2 into a dry contact mode. excluding/including, or interview should then add two additional binary sensor nodes. I can then set parameters 10 and 11 to 0 which isolates the sensors from the relays, so the relay doesn't turn on/off with the sensor input. I had this setup on old ISY and Zooz dongle but it does not appear to work with ZMatter. Interesting though I do see this nodes if I Xray a .1 address node which is two more nodes than you show... but it could just mean that the sensor and switch are together which is how it operates now currently. --- 10 Command Classes --- 32 x20 V2 I S BASIC 37 x25 V2 I S SWITCH_BINARY 48 x30 V2 I S SENSOR_BINARY 89 x59 V3 I S ASSOCIATION_GROUP_INFO 94 x5e V2 I S ZWAVEPLUS_INFO 108 x6c V1 I S SUPERVISION 113 x71 V8 I S NOTIFICATION 133 x85 V3 I S ASSOCIATION 142 x8e V4 I S MULTI_CHANNEL_ASSOCIATION 159 x9f V1 I S SECURITY_2 Also before ZMatter, when I change parameter 2 and 3 to a type 7 for a door (for my garage door), the nodes were named different and had shown open/close instead of on/off for an input... like it recognized it was a door and configured appropriately. It is still not working as it was previously with ZW500 series.

That 2 second delay instant status I believe is a problem with the GE/Jasco. I tried them and returned a bunch when I found out the issue. Zen71 report status back to the control about as fast as Insteon in my testing. I personally think all those double, triple... 5 taps are useless and not sure who would use in reality - just a marketing feature. When you mention pure switch, does that mean it turns the load on fully to 100% so the hue work correct, or just makes it a logical switch with the load on? Zen71 has a parameter which turns off the actual load control so you can use the switch without affecting the load - ie. leave light turned on always.

The old Zooz and ISY 500 didn't do basic scene associations and faked it through the controller itself, which is referred to as central scene control. It seems that old implementation either these scene nodes by default and was hard coded into the way scenes worked, or it simply looked at status of on/off of the ZWave device and internally simulated the scene (probably more likely). ZMatter and how it handles ZWave basic associations and scene control are not as easy as just dropping any node into a scene now like it was before, instead have to pick the proper node and settings. Also remember that the history of scenes in IoX originates, and was designed around Insteon scenes. It was with ZWave support in ISY when they were able to add a feature which integrated ZWave devices into scenes but, all traffic was through the controller. Most other controllers don't originate their concept of a scene in the same way as IoX, and instead handle everything through the controller by default. (probably because no other devices are capable of scenes the way Insteon does, and very few support Insteon anyways, so they wouldn't bother). ZWave is sorta kinda similar with its basic associations, in the fact that they can talk directly without a controller, but still not even really close in how it works compared to Insteon, however with basic association they can now be added into a scene and act closer to how Insteon works. UDI for doing this all seamlessly is pretty nice because it is my understanding that with many other hubs you have to keep track of associations yourself and use a separate association tool - but with IoX and ZMatter it is just drag and drop into the scene and it programs the devices accordingly! Regarding your Zen34, I would continue this discussion about it in this thread and maybe UDI will take notice and fix. There are numerous devices that are missing nodes with ZMatter.

In the example, The ZY Scene Button 1 is the controller Master Bedroom Ceiling is responder which is currently selected and pulldown has options what to do when that scene button is On... eg On, Off, Fast Off, Fast On etc. To turn the Master Bedroom Ceiling responder off, I would have to add the ZY Scene Button 2 (which is the bottom paddle) and then select Master Bedroom Ceiling and select off. But for you, since running mostly zwave, I would not bother with this and use basic association instead. This example was mainly how to control other devices like Insteon.

I think there is issue with Zen34 and ZMatter not showing all the nodes. It is missing Scene button 1 and 2. For now it looks like you could still use basic control node to link directly to another ZWave responder switch in a scene, which should be fine for you because you only have ZWave. This switch currently could not control Insteon devices without those scene buttons, but those are really only useful in scenes for controlling non-zwave devices from what I can tell (my opinion may change on this as I learn more). Aside from that, you would need to use programs using control to detect the different presses like double tap, triple tap since these scene parameters are not currently usable in the controller nodes for use in scenes.... maybe it is possible they could add more nodes eg. ZY 015 Scene Button 1.doubletap, Scene Button1.tripletap etc. for use in scenes.

Oh ya I forgot about that keeping those LEDs in sync on Zen32. But could still use programs to do that in addition to zwave basic associations, just the LEDs would take a bit to update after. I had the issue on old ZWave 500 on Polisy prior to ZMatter that it would send a fake On signal to ISY for button 5 even though I pressed any of the four smaller buttons. A query of button 5 after would correct this and show the proper state. Just wondering if you notice this and I am hoping it is fixed now and not something internal on the switch itself but rather a bug in the old Zwave implementation.

Here is a picture of Zen71 I am using here and it also only has paddle on/off.. The way the scenes work is pressing the top paddle triggers scene button1 on and the bottom paddle is scene button 2 on. ----- Upper Paddle: 1 x tap: load on; Scene 1, attribute 00 2 x tap: Scene 1, attribute 03 3 x tap: enter inclusion (pairing) mode (only if the switch is not included to the hub); Scene 1, attribute 04 4 x tap: Scene 1, attribute 05 5 x tap: Scene 1, attribute 06 6 x tap: change LED indicator mode (see parameter 2) held: Scene 1, attribute 01 released: Scene 1, attribute 02 Lower Paddle: 1 x tap: load off; Scene 2, attribute 00 2 x tap: Scene 2, attribute 03 3 x tap: enter exclusion (unpairing) mode; Scene 2, attribute 04 4 x tap: Scene 2, attribute 05 5 x tap: Scene 2, attribute 06 held: Scene 2, attribute 01 released: Scene 2, attribute 02 held for 10 seconds (LED indicator starts blinking): enter the setting menu >> 5 x tap down for factory reset; 5 x tap up to change LED bulb mode (see parameter 11); 2 x tap down to enable the range test tool. ----- I have Jasco/GE and here is extra nodes for mine in IoX... (missing the power on-off switch node because its in a different folder) I should be able to use the same ZY 015 Scene Button 1 and 2 the same way in a scene as Zen71 I added the GE switch to my test scene and I also added an Insteon dimmer Master Bedroom Ceiling, and can see extra options available to control for dimming etc. I am going to test to see if I can hold the Zen71 paddle to dim up/down to control the Insteon device... I expect it to work.