brians

I think what UD would like to do is make this all seamless using their existing scenes, but I am guessing that the main problem they are probably running into is the various devices out there which may be difficult to query/set the associations in a standard way; probably why other hubs have a "driver" model, or a scene association utility, or just don't bother with direct association and encourage you to use the "central scene" method via the controller?!? I can see another issue if one has a direct association on a switch with another device, then exclude/include it and node ID changes. Actually this will break Z-Wave scenes and programs in ISY anyways because they use the Z-wave Node ID for creating/naming the device.

This is interesting reading... https://drzwave.blog/tag/z-wave/ https://drzwave.blog/2021/02/01/controlling-flirs-via-associations/ I have another S2 stick on its way which I will use to experiment with some switches in order to learn more about this.

I just got a Zen32 and the binary switch node turns on/off no matter what button I press... the relay or any of the four smaller buttons. This means that if I turn on the big relay, and then press another button it sets it off (doesn't actually change the physical relay state) so this is not good for programs. Each button actually seems to have an individual on/off state which all share one node in ISY. Maybe is older firmware because parameter 23 doesn't appear to work... I am putting in a ticket to Zooz for this firmware.

Just click the red x to left of each device and delete.

Ahh ok. Wonder what was the model of switches that work! Someone here has tried a zooz zen71 without success.

Please explain how you have done this, what model of switches, and what IAW means.

@BuzzhazzI am curioius how you are going to purchase Insteon for new home when there are no Insteon products available. If Insteon was still available and 100% certain of its fate, yes I would definitely get a Polisy and use IoP. For switches and lighting, Insteon and IoP/ISY is superior to Z-Wave in setup and manageability. Supplement Insteon network with Z-Wave devices that are not available with Insteon (which is what I do - I run 2413S, have two brand new 2413U as backup, and an Insteon stick also as backup so I am good regarding failing PLM) If you cannot get Insteon, as far as alternatives to Insteon, Z-Wave seems to be the only other DIY product that one could use in a system with a local hub/controller (not talking about cloud stuff like Google, Amazon, Homekit, "Matter", or the cheap switches/bulbs purchase from Costco etc.).

Disable program1 temporarily then try run program2 and see what happens. can also try changing the variable manually to 0 and if changes back there is some other program setting it.

I remember I suggested to turn off query on restart in other thread. The IoP needs to know status of Lights to turn on or off. Run the query all. I wrote my own query program that is faster when I’m testing and tell it to run on startup. Basically I just added all my devices in and query.

Is this a brand new install or did you restore from an ISY backup? If you have a lot of Insteon devices, try disabling query at restart. It takes a very long time and ties up the ISY during this process. Also confirm the S2 dongle works... what happens when you insert into a Windows PC? Do you see it in device manager? Does your Insteon PLM connect to Polisy by USB or serial?

Seems like other systems can do this. https://www.support.getzooz.com/kb/article/591-how-to-program-your-zen34-remote-switch-on-home-assistant/ However from what I see others showing how to do things in HA (eg YouTube videos) it seems that they just do everything through the controller and spend most of time messing with yaml LOL. Also read that can get confusing when programming setting associations. The only reason I would use is a virtual 3-way maybe. Also seems limit of 5 associations per device i wonder if possible to temporarily put the zwave stick in a windows pc and use other software to like the zwave controller to setup associations. It seems it is independent of the main controller

Follow up after a few days of running the 7.17.2 firmware on S2 stick. I have 20 Z-Wave devices currently on my network. All Z-Wave Plus or higher (eg. 500 series or higher). 41 Insteon devices currently on my network. Seems my Z-Wave network is more stable and responsive but it could be just in my mind. I added back my ZEN25 double plug, which before seems to have been causing lots of traffic on the network and so far I no longer experience the problem - that issue was in the release notes regarding floods of traffic which seemed to be what I was experiencing. Maybe if someone else here has a ZEN25 on older firmware they can let me know if they experience any issues like I did. I haven't seen any typical communication errors for a long time when opening the Administrative Console, even when previously on 7.15 firmware - except when I would include the ZEN25 within a few hours it would cause issue on my network therefore had been sitting in a box unused.

@KCraterGet the Zooz Zen17 because you can separate the inputs from the outputs. I have a couple... one senses a pump motor via dry contact output AC sensor. Another is on my garage door and senses door closed via reed switch, and I use relay out on that for garage button control. Zen17 can do two simultaneous inputs and should work for what you want. To clarify... I can touch a paperclip between the two connections on either of the two the inputs and I can see it almost instantly update the ISY. I have moved to IoP but had working on ISY994i with 500 series Z-Wave before.

Ok thanks, the way it currently works is fine!

I noticed they are selling the Zooz Z-Wave stick for $19 with Polisy. That is cheap for a stick!

@Goose66Thanks, Alarm Restored works perfect for Disarm. I have a program that disarms the alarm based on a particular user unlocking my z-wave door lock. When the alarm disarms now, an alarm disarm program prepares a pushover message which includes the door lock user so I know who had opened the door and therefore disarmed. Having said that, is there a way to disarm via a particular user? I am always seeing User 40 disarm when I do it through ISY.

Working now thanks.

@TJF1960 I was thinking of that but the program triggers between ready and not ready if I open/close the front door. What I ended up doing is making a variable named something like Alarm_Armed When my program detects armed stay or away, it sets the variable to 1 Then another program that detects disarm, it checks if partition state is ready and Alarm_Armed=1 then is true, and the then sets Alarm_Armed=0, and also inits in case ISY was rebooted. Alarm Disarmed - [ID 006C][Parent 0061] If 'Alarm Panel / Partition 1' Partition State is Ready And $Alarm_Armed is 1 Then Set 'Notification Controller / Service Pushover Brian' Priority Normal Set 'Notification Controller' Message Alarm - Disarmed Set 'Notification Controller / Service Pushover Brian' Send $Alarm_Armed = 0 $Alarm_Armed Init To 0 Else - No Actions - (To add one, press 'Action') Alarm Armed Stay - [ID 006A][Parent 0061] If 'Alarm Panel / Partition 1' Partition State is Armed Stay Then $Alarm_Armed = 1 $Alarm_Armed Init To 1 Set 'Notification Controller / Service Pushover Brian' Priority Normal Set 'Notification Controller' Message Alarm - Armed Stay Set 'Notification Controller / Service Pushover Brian' Send Else - No Actions - (To add one, press 'Action')

Yes I have 3.0.47 also.

I can’t seem to find a way to trigger a program based disarm. I can do for arm stay and away and alarming etc but no way to trigger a program when the alarm has been disarmed.

If you currently have Insteon and plan on going to Z-Wave then I would go for the Polisy. If you do not have your serial cable for the PLM it is easy to make one. Since you are running only Insteon, the transition will be easy. For your roomiermote it should work but since Polisy uses port 8080 for its web interface, you would probably have to add a :8080 to the end of your IP address in the REST commands. The ISY994i only supports Z-Wave 500 series. The newest Z-Wave standard is 700 series which the Polisy supports via S2 dongle. Looking back at history, people with older 300 series boards on ISY could not upgrade to newer versions of firmware because support was dropped and their Z-Wave stop working. I can see the same thing happening with ISY994i and 500 series boards being left behind. I do believe that all future Z-Wave development at UD is going to be with Polisy only, and we will see no new features on the older ISY994i with 500 series boards. With Polisy, the Z-Wave is theoretically upgradable in the future so if a new Z-Wave series comes out (eg. 900?!?) you could just insert a new dongle. If you decide to leave Insteon and Polisy for something else in the future, you still have a useable dongle for something else like Home Assistant. Regarding polyglot node servers, with PG2 being deprecated, future Polyglots will need PG3 which only runs on a Polisy (you cannot install PG3 yourself on your own hardware like you could before with PG2). Right now PG2 are still working but the focus is on PG3. Note that Polisy currently runs both PG2 (for legacy) and PG3 servers so you would have access to everything.

See this starting from Advanced | Factory Reset Z-Wave dongle https://wiki.universal-devices.com/index.php?title=ISY_Users:V5:ZWave:Advanced_User_Guide:TopMenu This is for ISY994 however iI think the same principles apply to Polisy except it uses an external usb stick. Since Polisy does not have similar function to backup stick yet I think we should backup separate on pc and restore if replacing the dongle in a working system. I believe that if I has just placed my brand new stick in without restoring then all my z wave devices would have been orphaned and I would have had to exclude include one by one. Someone here with a test Polisy can confirm by backing up nvram, resetting their stick and plug back in Polisy and note if all wave devices are orphaned, then restore nvram to same stick and plug back in again to see if zwave works. Of course shut down polisy in between removing adding stick. UDs goal I imagine is to create an automated tool that converts the isy994i backup file to one compatible with an s2 stick, in the future for those updating from isy.

@JimboAutomatesI noticed the log package contains pg3-current.log which has logins and passwords for all my PG3 nodes. debug.log looks ok, I will send you that for now until I look over other log to make sure.

You said earlier yours was a new install and stick, I misunderstood and thought you meant you had no previous z-wave on there and when you said new install meant a new IoP install/setup with no previous Z-Wave devices. So please confirm that your old z-wave dongle was being used in IoP and had Z-Wave devices, and then replacing it with a brand new z-wave dongle you still had everything in Z-Wave show up and useable in IoP? If this is the case then there is no reason to do a NVM backup and restore when changing dongles and IoP must reprogram the dongle.

Ok good news is I restored my Z-Wave configuration to a new Zooz stick. The steps are: I shut down Polisy. I removed the old Zooz stick and backed up the NVRAM using PC. It saves as a zip file. I plugged in new stick in PC, then upgraded firmware on my replacement stick I restored saved NVRAM to new stick on my PC. I plugged in Polisy and turned on let it boot up and all my Z-Wave works as before. I recommend whenever doing any significant changes to backup the Zooz stick on PC, in case need of restore... until UD implements a backup/restore like they did in the ISY994i (I presume that is what it did?!?). Now I still do not know what would happen if I just placed in the new stick in Polisy without restoring the saved NVRAM from old stick. I did not want to try because I thought what I did was the proper way based on my research what other hubs and HA people do.