brians

It’s in the first page of this thread.

Ok, I am still trying to think what I could use it for. I guess a use case could be to use it as a switch that runs a program or something.

When I manually changed the variable it did not turn on/off the switch though. I will try again.

I am not sure what this is but looked interesting. I installed and made a virtual switch but it did not seem to do anything other than have a switch I can turn on/off. I setup the type to switch and ID to the number of a state variable (eg. 5 in my case), expecting that it would sync and set the variable 1 and 0 for on and off, but did not seem to work. What am I doing wrong? I read through the original thread but seems to focus mostly on temperatures which I am not currently interested in.

I have same issues when replacing insteon devices. I don’t really worry about it and just manually fix it each time presuming they would eventually fix.

To get the S2 firmware version se the event viewer log to level 3 and then do a Z-Wave, Z-Wave version from the top menu. It will show in the log. It looks like it is trying to add additional nodes to existing devices. You can try freeze ISY nodes and see if that helps. But since are running it as a secondary controller it may not be easy to troubleshoot the problem.

What are the ZWave devices that seem to cause the issue? What is firmware on the S2 ZWave stick?

That is strange that it would not light up the keypad. Did you add to the scene as a controller? As a workaround you could write a program that gets triggered by its press and turns on the LED (via a scene).

https://aeotec.com/z-wave-wireless-switch/index.html Also a Zen34... https://www.amazon.ca/Network-Control-Controller-ZEN34-Required/dp/B08TMWLY74/ref=sr_1_2?crid=1P207BHC67WJL&keywords=aeotec+wallmote&qid=1651791528&sprefix=aeotec+wallmote%2Caps%2C216&sr=8-2 Anyone used either of these in ISY? If I had to choose I would pick the Zen34 for its simplicity, but the wallmote quad looks neat to control dimmers with swiping up/down on each button but not sure if those would work as a controller with Insteon. They should work with scene associations controlling another Z-Wave dimmer but UDI seems not to currently fully support scene associations correctly (see big thread elsewhere).

That sounds exactly how I do it. Regarding Alexa I just have a simple in off spoken that sets it to med I think because I had issues with Alexa differentiating spokens that were close to one another - didn’t seem to know the difference between fan high fan medium etc. maybe it’s better now.

I don't think there is a better way. I use four programs triggered by the on level of the fan and four scenes... each one will set the scene appropriately on or off. It doesn't matter then where you turn on/off the fan from the LEDs will stay in sync... Here is one of mine for Med setting as example and calls a scene which set the fan med and all the other keypad buttons off. Master Bedroom Fan Med - [ID 003C][Parent 0033] If 'Master Bedroom / Master Bedroom Fan' Status is Medium Then Set 'MBedroom Fanlinc Scenes / Master Bedroom KPL Fan Med' On Else Set 'MBedroom Fanlinc Scenes / Master Bedroom KPL Fan Med' Off

You should have binary sensors for each input after setting the configuration parameters and exclude/include. Weird that setting to 10 didn't show and 7 did which is a open/close alert. I am not sure what the functional difference is in all those settings 4-10 anyways. It could also have been a second exclude/include fixed - I have seen this with some z-wave devices.

Add remove or whatever isy calls it is same they just used different nomenclature.

Is it possible to use these instead of an RGB controller. I got a TV stand and came with an 8 output RGB controller to connect all the LEDs and the typical RGB IR remote . Is there some sort of RGB hub instead of an LED strip I can interface to this Zen31 to control through ISY instead?

I updated mine and is working.

I looked up my notes: 1. parameter 2 and parameter 3 to 10 (on/off dry contact sensor) 2. exclude/include via ISY controller and it added a couple extra nodes... binary sensor - use these for triggers in programs etc. 3. parameter 10 (and Parameter 11 if wanted) to 0 which does not require a remove/add (this isolates the relay triggered from the input) From manual: IMPORTANT: If you set this parameter to value 4-10, you’ll need to exclude and re-include the device (without changing any settings) so that a child device is created for the input of your choice!

The instructions that come with with zen17 tell you the parameter how to isolate the inputs and that that you have to exclude include again and extra nodes appear. I have two running like this with no issues.

It has low, med, hi you set the fan on highest. It does hum on our fan but not sure if it is the fan's fault. Doesn't bug me.

In my case, my bedroom fan only was wired with one switch, and we are expected to use the pull chains to adjust fan speed and light control. Therefore I don't think your way would work for me because you mention installing two separate switches. The insteon fanlinc solves this because it is installed in the fan itself which separates the outputs for light and fan. If there is a Z-Wave module that does what the fanclinc does that would work great.

Mine shows this: The reason that it does not show in the Z-Wave Version menu is probably because UDI have not implemented that for Polisy yet, most likely using code/method to determine firmware version from ISY.

There is already another thread a few topics down in this forum that explains how to do. Please go read that entire thread.

Don't think Polisy does S2 yet.

@peterathansIt will work with more switches. The limit is 5 associated devices for each controlling device. I had setup my Zen15 which also turns on/off with either of the Zen71. However, I believe that with this type of direct association, the devices need to communicate directly and do not route through other switches. Therefore both switches should be in close proximity to each other. If using a pair in a hallway or same room I do not see an issue. If using dimmers you will also have to add destination nodes to group 3 (that is "standard" dimming group but some switches may be different) in addition to group 2. Now that I been learning more about Z-Wave, it seems that what I have done here is not really uncommon, and others have been doing this for years similarly to how I have. Some controllers have this ability built-in, others have a utility that you run; there is lots of explanation all over how these associations work - once you know what to look for. I am hoping that UDI fixes this, especially now with Insteon gone, Zwave will be much more relevant to Polisy and IoP. Disclaimer: Do the following at your own risk... I do not take responsibility for you messing up your Z-Wave network! This is for fun and experimentation only... I have used a separate test system to be comfortable with it first. I have tested on IoP but following screenshots are from my ISY.. .but it will be the same. For those who have another S2 stick and another test system eg. ISY or IoP, and want to experiment with this, this is how to include the ISY controller on PC software... On the network management screen, click Select Learn Mode, then NWI, then go to your IoP or ISY, select Z-Wave, Add a Z-Wave device. It should take a while but all the nodes will eventually appear in the Z-Wave PC Controller and you will see a new [S0] Pc Controller in the PC software. If it doesn't work just try again. I had to try 2 or 3 times on my IoP before it added without errors. The ISY will also have the same node number eg. ZW 006 PC Controller but it doesn't do anything from that end. I found that querying it sometimes will cause an error. It can be disabled so the 3am query program ignores it if proves to be an issue. The idea is to keep the 2nd stick always around to do quick changes/updates to associations without having to include it each time (even firmware updates probably). If you make changes to Z-Wave on ISY like including/excluding a new device, just press the Update button on the PC Controller and it will add those devices in, or remove ones you deleted from ISY. Also don't exclude/include devices using the PC because I don't think ISY will be able to pull them in. Always include/exclude from ISY. If you do exclude or delete it from the PC controller, you can always replace failed node on ISY and it will bring it back (I have tested this a few times and works), then of course update on PC again. I would suggest not adjusting any of your existing Z-Wave devices at first, but instead work with a couple test devices to experiment on. Make sure you use the correct node numbers and correlate them from ISY to PC software. If no associations show, just select a device and get press Node Info button, then should appear. I found that removing lifeline id 1 (the ISY) from group 1 makes it perform better - the associated switch turns on/off quicker and more reliable, and probably will make it work without IoP being on on (as I discovered earlier testing with the S2 stick only) but I did not shut down IoP to test this yet. To remove/exclude the PC controller entirely, make sure it is enabled on ISY, and do a Z-Wave, Remove a Z-Wave device on ISY, then on PC Select Learn Mode but this time NWE (Network Wide Exclusion). Note that any direct associations you made will still will exist on the source devices, and to remove them you would have to include the controller back again and change, or exclude the particular device from IoP and include it again (which resets the device in process). If you don't have an extra stick you can try this but extra warning because I have not tried this: shut down Polisy, remove the S2 stick and place in PC and launch the Z-Wave PC Controller... backup the NVM first in PC software (it is on the Home screen or the icon in lower left). Then do your associations, remove stick, put back in Polisy and boot up. Make note of your node numbers of devices in IoP first so you reference the correct ones on PC. Even though both switches will be associated together as one switch, they can still be placed in a scene with other devices- just set each switch to ignore turning the other on/off in the scene option pulldown so they don't send extra redundant traffic to each other. Here is one final screenshot of my IoP and Z-Wave PC Controller with both Zen71 id 50 and 51 setup for direct association, in a scene together (not really needed in this case). Since this screenshot, I went and added the Zen15 power switch into the test scene as a responder and am able to turn it on and off it from either Zen71. As a general rule, I suggest just using this type of direct association for wall switches eg. virtual 3-way, 4-way where the switches are meant to be synchronized always. There is no real need to setup an association to turn on a Zen15 plug and is better handled by the IoP logic, otherwise things can get confusing if you forgot about an association somewhere.

Oh here is more testing. On my Test ISY994i I included both Zen71 switches. I linked the PC Controller with S2 Zwave dongle to my Test ISY994i. Sometimes doesn't work right away so have to keep trying... it ended up as ZW 006 on the ISY. I can then go on the PC controller and set the Group 2 associations independently of the ISY in real-time and it works the same as my previous posts. Both are "permanently" linked now outside of ISY, it is not possible to turn on/off individually in ISY - eg. if turn one on, the other comes on, vice versa. Of course, it is not really permanent and I can just go and remove association via PC controller and it takes affect instantly (this will be much easier if is supported in IoP). Note that this will take away some logic and ISY abilities for individual switch control. Removing Group 1 lifeline nodes from each of the switches improves performance, but the ISY still sees the status updates so not sure exactly how this works but I think it is sending more info and requiring ACK from ISY which would take more time - I looked briefly at logs but didn't have time to come to a full conclusion right now. One use I can think for this is a proper virtual 3-way, which is a big reason why I have not liked Z-Wave as much. (before doing all of this I also tried putting the Zen71's in a scene on my test ISY994i and also experienced the on/off looping I mentioned before so this is not just limited to IoP). I will do up a tutorial for this eventually after I test on my IoP. Here is info in event viewer for ZW 002 and it even shows the association group 2 now for other switch... Sun 04/17/2022 01:48:17 PM : [ZW-SHOW ] ---------------------------------------------- Sun 04/17/2022 01:48:17 PM : [ZW-SHOW ] ZW 002 On-Off Power Switch Sun 04/17/2022 01:48:17 PM : [ZW-SHOW ] ZW002_1 uid=2 security=None type=4.16.1 mid=634 tid=28672 pid=40961 Sun 04/17/2022 01:48:17 PM : [ZW-SHOW ] Association Group ID 1 Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - x20 V2 BASIC Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - x5E V2 ZWAVEPLUS_INFO Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - x25 V2 SWITCH_BINARY Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - x70 V4 CONFIGURATION Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - x5B V3 CENTRAL_SCENE Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - x85 V3 ASSOCIATION Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - x8E V4 MULTI_CHANNEL_ASSOCIATION Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - x59 V3 ASSOCIATION_GROUP_INFO Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - x55 V2 TRANSPORT_SERVICE Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - x86 V3 VERSION Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - x72 V2 MANUFACTURER_SPECIFIC Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - x5A V1 DEVICE_RESET_LOCALLY Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - x87 V3 INDICATOR Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - x73 V1 POWERLEVEL Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - x9F V1 SECURITY_2 Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - x6C V1 SUPERVISION Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - x7A V5 FIRMWARE_UPDATE_MD Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - Secure Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] Last working route from ISY to Node 2 - ZW 002 On-Off Power Switch Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - Node 3 - ZW 003 On-Off Power Switch Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] Node 2 - ZW 002 On-Off Power Switch has the following neighbors Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - Repeater - Node 1 - [This ISY] Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - Repeater - Node 3 - ZW 003 On-Off Power Switch Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] - Repeater - Node 7 - ZW 007 On-Off Power Switch Sun 04/17/2022 01:48:58 PM : [ZW-SHOW ] Sun 04/17/2022 01:48:59 PM : [ZW-SHOW ] Node 2 - ZW 002 On-Off Power Switch has 3 association groups Sun 04/17/2022 01:49:00 PM : [ZW-SHOW ] Associations for group 002 of ZW002_252N002 ZW 002 Basic Scene Ctl 2 Sun 04/17/2022 01:49:00 PM : [ZW-SHOW ] Max Associations = 5 Sun 04/17/2022 01:49:00 PM : [ZW-SHOW ] - Node 3 - ZW 003 On-Off Power Switch Sun 04/17/2022 01:49:00 PM : [ZW-SHOW ] Sun 04/17/2022 01:49:00 PM : [ZW-SHOW ] Associations for group 003 of ZW002_252N003 ZW 002 Basic Scene Ctl 3 Sun 04/17/2022 01:49:00 PM : [ZW-SHOW ] Max Associations = 5 Sun 04/17/2022 01:49:00 PM : [ZW-SHOW ] - Node 1 - [This ISY] Sun 04/17/2022 01:49:00 PM : [ZW-SHOW ] Sun 04/17/2022 01:49:00 PM : [ZW-SHOW ] ---------------------------------------------- Sun 04/17/2022 01:49:21 PM : [ZWAVE-RX ZW007_1] [32/02] CC=0x32 cmd=0x02 [A1640001CFC00000] ACK,AUTO,EXPLORE From=0x07 Sun 04/17/2022 01:49:21 PM : [D2D EVENT ] Event [ZW007_143] [CV] [118720] uom=72 prec=3 Sun 04/17/2022 01:49:21 PM : [ ZW007_143] CV 118720 (uom=72 prec=3) Sun 04/17/2022 01:49:21 PM : [ZWAVE-RX ZW007_1] [32/02] CC=0x32 cmd=0x02 [A16C000000000000] ACK,AUTO,EXPLORE From=0x07 Sun 04/17/2022 01:49:21 PM : [ZWAVE-RX ZW007_1] [32/02] CC=0x32 cmd=0x02 [216400000000012B00000000] ACK,AUTO,EXPLORE From=0x07 Sun 04/17/2022 01:49:21 PM : [ZWAVE-RX ZW007_1] [32/02] CC=0x32 cmd=0x02 [2174000000000000] ACK,AUTO,EXPLORE From=0x07