brians

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?

I agree that it was UDI's effort with their ISY that actually brought some stabilization to Insteon owners such as myself, being an early adopter from the beginning, with all the different revisions throughout the years.

I have a three or four of those working but haven’t changed since 5.5.3 so maybe is a bug ? Therefore I don’t want to exclude them to test. I do have a spare dimmer version DZPD3 which is basically same thing but a dimmer, and I just successfully excluded and included it again no problem on v5.5.3. Were those DZPA1 working for you on v5.5.2 and this problem was just introduced in v5.5.3? Are you excluding/including on the Leviton by pressing the button for several seconds until it flashes red, then let go and press once? I do like the DZPA1's and nobody really seems to make a unit as nice for the price. Being typical Leviton, they don't support instant status. Since they are not really designed to be a controller where you would switch on/off locally I have never missed this - I never would turn on the device local by reaching down to the plug and pressing the button. They do support hail if this is necessary to get status, but with ZMatter this is broken for now.

I tried this and works good. On my Zen71 I had to set parameter 9 to 1 which enables scene buttons then it started working. I set button 1 command to on and button 2 command to off for an Insteon switchlinc. I found most other nodes have to be set to ignore the scene buttons otherwise the scene buttons may turn on devices you don't want on. One can even make old style pre-zmatter slower zwave scenes this way which go through the IoX controller (ie. central scene) instead of using basic associations (which are direct switch-to-switch) if need to for whatever reason - maybe an older zwave device want to turn on/off from another that doesn't support direct accociations. I recommend using basic association between Z-Wave devices wherever possible since it is much faster - in a virtual 3-way test, is as fast as Insteon on my Zen71s (other ZWave brands/models may vary). When controlling Insteon from Zen71, as describe previously using scene buttons, it is slower than insteon-to-insteon or zwave-to-zwave, but not that bad since IoX receives a command on ZWave, it is able to send it out Insteon right away. In comparison, when controlling ZWave form ZWave the same way using central scene (through IoX) only, it is significantly slower because of ZWave network overhead ACK, having to wait for ZWave network to be available before it sends to command to other switch. I added screenshot how the scene buttons on Zen71 switch ZY 022 work to control Insteon device named "Stairs", and also control another Zen71 switch ZY 023 using Basic Set. The other ZY 023 is set similarly in scene except its Basic Set is controlling ZY 022 of course. There is not one Node to control all, must use multiple nodes now with ZMatter. Remember that ZWave scene commands send an On command. On Zen71 switch: Scene Button 1 = top paddle Scene Button 2 = bottom paddle Program the scene so: The top paddle Scene Button 1 sends an Insteon On to Stairs The bottom paddle Scene Button 2 sends and Insteon OFF to Stairs. There is no equivalent of a default where it will turn on/off automatically when controlling this way, must handle both cases for pressing top or bottom paddle. NOTE: Both on-off power switches are set to ignore scene commands, otherwise the scene will turn on these switches by default from a scene command. Although, you can set these to same way as the Insteon Stairs with a Command On or Off to use old method of central scene I mention above, this is not desirable because I have the ZWave setup together using basic association and having both methods could cause confusion of the switches. Therefore, in this scene, I have two Zen71 setup using basic set to turn each other directly on/off and also each one turns the Insteon Stairs switch on/off using separate scene button nodes.

Working now again.

I posted issue in the portal forum. Also affects admin console connecting via portal.

Noticed today issue that I cannot seem to connect to portal on both UD Mobile and AC via portal account. Stuck on Initializing, Starting Subscription. I have restarted my Polisy, and then restarted IoX afterwards again which did not resolve. Portal shows it connected however.

In my case I just want the folder to display status of a program (Idle true, Idle false etc.) and I would use those values to change the color indicating a light is on/off in that folder/room, instead of the program setting a variable. The behavior of a folder when changing the display node to a program is not desirable in this case because selecting the icon does not take me into the folder. Not an issue since I currently use variables, was just thinking it as a shortcut without having to make a variable.

I did some tests tonight and was able to set parameter 3 to 3 which has built in momentary garage door setting on button so it turns off relay 2 after a few seconds. I have garage door open sensor on relay 1. The issue seems to be with anything with parameter 4 and above, it does not show the extra nodes. The Zooz instructions say to either exclude/include or re-interview. Neither work. Because of this we cannot get extra parameters and isolate the inputs. Note that it is important to set the parameter using the one ZWave node that contains the parameter option... right clicking on a different node and selecting zwave write configuration parameter did not seem to work for me. In case of Zen17 specifically it is the node named default ZY xxx Binary Switch. The ones named ZY xxx.1 or .2 do not work. Hopefully UDI can fix this Zen17 configuration issue since this is a very useful and popular device... would be nice to be able to separate the inputs from the relay and set different types of contacts. If this was possible to isolate, I could have the switch on relay 2 and sensor on input 2 and could run two separate doors, or maybe other sensors and switches. It worked fine before with Zooz dongle so thing there is just something overlooked hopefully.

@JaviI had an idea that I could just use the program status true or false to determine the status and color of a folder icon for on/off instead of having a variable eg. 1 and 0 for on/off. However, when I set the status of a folder to display a program node, the top half does not operate as a folder and clicking on it runs the program instead, clicking bottom half opens the folder. Is this expected operation? Seems like a bug to me.