Zen30 Weirdnesss

[xlurkr]

My Zen30 isn't working right.  It was, before I migrated to ZMatter.  It used to have controls on the "XXX.1 Binary Switch" node.  Since I excluded it, migrated, and reincluded it, the controls are in the "XXX Binary Switch" node, as shown in the first image, and there are no controls in in the "XXX.1 Binary Switch" node, as shown in the second image.  I wouldn't care, except the controls don't actually change the state of the switch - nor do they reflect any change made locally.  Does anyone here have this device in a ZMatter setup so you could look at your nodes and see if they match mine?  Any other advice would be appreciated, too.

-Tom

[Techman]

What about the "dimmer switch" node. Does that work correctly?

 

[xlurkr]

Yes.  btw, I just excluded and readded, and there's no change.  Except the Z-Wave device number incremented to 4, of course.

-Tom

And I have restarted IoX several times.  I haven't power cycled yet, but I can't imagine that would help.

-Tom

[Techman]

If the "dimmer switch" works then use that node and disregard the binary node(s)

Zwave devices are designed to work with various controllers and not all the nodes are compatible with all the controllers. It's not unusual to have left over nodes.

[oberkc]

11 hours ago, xlurkr said:

I wouldn't care, except the controls don't actually change the state of the switch - nor do they reflect any change made locally. 

Your experience sounds similar to mine in some ways.  Some z-wave devices I have tried do not seem to update status in the ISY when controlled locally.  I have decided that I am not going to use Z-wave devices as scene controllers.  They work quite well for me as responders, however.  I have only used z-wave as part of the ISY/Polisy so I cannot compare that to other systems or know whether this is normal for z-wave or unique to Universal Devices.  

[RRalston]

@xlurkr So far I only have Zwave devices from Zooz, and I do have a ZEN30 in use. Before I get into specifics, I find the Zwave implementation in eISY to be less than satisfactory on so many levels. I had hopes with the 5.9.1 release where Zwave fixes/improvements were apparently implemented, but I have seen no improvement yet. For this ZEN30, UD's implementation won't even let you do an OTA firmware upgrade because they have experienced devices being "bricked". Zooz support does not understand that, but UD does not seem willing to work with Zooz to figure it out. But for devices where you can do OTA upgrades, the process can make a mess out of your device requiring multiple bizarre reboots and "Synchronizations|Update with interview" operations that make no sense. OK, enough  complaining. I'm sure given enough time they will figure it out.

Now, back to your post. My ZEN30 use case was really to have the equivalent of two separate ON/OFF switches in one device, which with device "Advanced Configuration Parameters" I was able to achieve. I use both switches within programs to control other Zwave devices and not for any scenes.

My device has multiple nodes as well, some of which seem to have no value and do not reflect anything useful when the device is operated. In fact the "Y003_147-Binary Switch" is such a node. That node belongs to the upper "dimmer switch" portion of the device. Sounds like it would toggle on and off, but no. You will find operational status under your "ZY003_1 - Dimmer Switch" node, which will represent "OFF" through 100%. Mine now only toggles between those two values based on my configuration.

You might find it useful to use the "Group Devices" operation for the device by right clicking on any node for the ZEN30. This will separate the top and bottom switch nodes for you into two separate branches so it makes a "little more" sense.

My device node which represents the bottom button "ZYxxx_001_1 - Binary Switch" (yours is shown as "ZY003_001_1") has a Status field present, while yours does not, which can't be right as I believe it is the only functional node for the bottom physical switch. That would explain at least part of your problem. Seems like you may need to work with UD support on this.

Here are a couple of captures from my installation:

This is my bottom switch node:

This is my Top Dimmer switch node, which as I said is configured to act as a binary switch via configuration:

 

My device nodes:

 

Edited February 22 by RRalston

[xlurkr]

Thanks @RRalston.  To be clear, you didn't have to do any advanced configuration after adding to get both controllable nodes to show up, did you?

-Tom

 

[RRalston]

@xlurkr, that is correct. The nodes were always there. I just had to play around to figure out which nodes did what when a switch was physically changed, or changed via a program or via Admin Console. The Advanced parameters I used were just to control switch behavior.

[dwengrovitz]

You might also check the switch firmware to make sure you are running the latest/current version. I have three Zen30 switches and they were pretty wonky at first, especially when I tried to get two to work in a group via associations.

I reported some issues to Zooz and they eventually put out a new version of firmware which helped, but just an FYI that there are several versions of the switch, and several versions of firmware. I think you can view firmware details here: https://www.support.getzooz.com/kb/article/393-zen30-double-switch-change-log/.

I now have two Zen30s working as a group, and one that operates as a single.  Here are some screen caps from my install for the switch that operates as a single:

Top Level:

 

Main Switch Control (021):

 

Dimmer Control (021.1)

 

Relay/Fan Control (021.2):

 

Edited February 24 by dwengrovitz

[xlurkr]

Thanks @dwengrovitz.  I think it's ticket time, since you also have On/Off/Query controls for the relay part of the switch, like I had before, and @RRalston has.  That's really all I need right now: control/status for the relay.  I hope UDI can help me get whatever hardware and firmware revision I have to work again.  Fortunately, I still have the Zooz 700 series dongle around here somewhere in case I have to do an OTA update, but I'm hoping that won't be necessary.

-Tom