brians

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.

They would need access to your network and then know the MAC address of the QNAP to wake it up if you use WOL, which must also be enabled on QNAP. If you set the QNAP to wake up on schedule then there is should be no way for someone to remotely turn it on.

I think there is a better way to do the backups with synology using either its hyperbackup or active backup or combination depending what you want backed up . You also may be able to send a wol packet to qnap via Node Server but if you don’t run node servers use a program to schedule on a pc. qnap can also use scheduler built in to turn itself on. https://www.qnap.com/en/how-to/faq/article/enabling-power-schedule-on-the-nas

Thanks. Does it still change the on off status of the main switch (without actually turning it on ir off) if you press the smaller buttons? Or are they discrete now. This is what I didn’t like before because couldn’t accurately use main button in a scene then by itself. Basic associations are a new thing but I tbink with zmatter api for zwave now you should be able to use the four buttons in scenes properly now in addition to programs.

Oh, I never did the migration but as I understand, devices that do not migrate correctly stay around as ZW xxx. I would ask for help in the appropriate migration forum.

If you ever get Zen32 working, please provide an information of the nodes it has. I am curious if it has scene button 1 - 5 nodes and basic scene group 2,4,6,8,10 like it did before (ZMatter seems to have issue showing all nodes like it did with 500 series). If has all these or similar then it will most likely make it much better to work with scenes. This is because ZMatter now correctly supports basic associations for zwave devices, and IoX can use scene control nodes now to trigger Insteon etc.... there is a thread here where we discuss... which is probably a better spot to continue this regarding zen32.

Check to see in status if your programs have yellow icon, if they do then just update a line and re-save... this is common during migrating that programs get disabled from running. Regarding your Z-Wave scenes, ZMatter works differently than old ZWave 500 series and you need to use and set the correct nodes now for proper scene control. See this thread in particular for guideline how to do this for Z-Wave direct associations, and further down it is explained how to use the old way (which old ISY software used), using Scene Buttons (which is also required for controlling Insteon devices).

It would restart the timer program.

What would be the solution then? I find that the way isy stops running programs works good for some things and other times it is difficult or impossible to do simplest things. Is there a way to set a flag on a program to not run/ignore “if” until finished? Maybe could do this with a couple programs - the first one has the “if and” which calls the second which contains actual code and first disables the calling program then does its timers etc then enables it again. I think a program disabling itself causes it to stop so would need two.

An update... I tried out the Node Server "Virtual" I made a virtual switch, and a virtual dimmer. In UD Mobile it is able to add a slider widget for the virtual dimmer. I then use a varible to hold dim state and have a few programs that link it all together. Haven't really tested for race conditions yet but seems to work ok so far but I don't really think this is the best solution really.

EISY is definitely the future if you are coming from ISY/Polisy, and have Insteon devices and node servers which rely on, or even if you have no Insteon and ZWave only - and don't want to redo everything in a new system ie. Home Assistant.

@GJ Software ProductsYa I wanted to have local button and load control on Zen32. I am hoping that on ZMatter, each physical button will make a node with scene buttons 1-4, and physical button being scene 5 and all isolated where pressing a small button doesn't make the physical button appear to turn on. Hopefully works better in ZMatter unless was the Zen32 doing this on its own. Don't really care that much anyways anymore since I would buy an Insteon keypadlinc over a Zen32 - this is beauty of still having Insteon support and able to integrate it all with types of devices. Back when I was testing Zen32, fate of Insteon was uncertain so was looking for alternatives. I am curious however about Zen32 now.

I would try restoring the backup you made before conversion.

This is an issue with Zen17 also since moving to ZMatter. Reconfiguring using parameter 2 and 3 does not add the extra nodes. Not sure on Zen16 if it is same parameter or not to do this, but they are similar devices.

The zen32 I am interested how it works now with zmatter regarding scenes and if the physical button still gets its scene triggered by pressing any of the smaller buttons, which made it sort of useless to me so I returned mine.

Try updating firmwares... If you had zooz stick before, I would suggest downloading the Silicon Labs PC software and checking the firmware on those. In past it has been difficult to get firmware for Leviton in files, but now they provided them (probably due to works with Leviton works with HA partnership or whatever) and just last week I upgraded my dimmer as a test - hoping maybe would fix hail or support instant on, but nope!. Anyways maybe a firmware update would fix y our issue and do via the PC software for now. Can look elsewhere in these forums for instructions how or even Zooz site tells how. Here is a link to the firmwares. Maybe UDI will support OTA eventually but they are saying firmware bug in the ZMatter or implying end device's fault, but other hubs seem to be able to do it so not sure on the reason. https://hubconnecteddecorasmart.leviton.com/hc/en-us/articles/7151993826075-Updating-Decora-Smart-Z-Wave-Using-Home-Assistant

I am confused by this. Why would one want to migrate their current Z-Wave on polisy/eisy with zmatter dongle to the same device on same zmatter dongle? Also, I have migrated to zmatter last month and that option no longer appears for me, therefore if I was to migrate my polisy/zmatter to an eisy/zmatter how would I do this then? The only thing I can see is you meant to say migrate from a polisy/eisy using a zooz zwave?