brians

Yes, not sure about popcorn response with multiple devices, but I have used the Silicon Labs Z-Wave PC Controller to set basic associations with Z-Wave devices that will run independently of a controller and it is very fast. See this thread and all my significant testing/conclusions are at the end - where it died off and seemed nobody else showed anymore interest. For some reason, ISY/Polisy doesn't allow setting basic associations for common wall switches which I tested (Zen71, Jasco) but these in fact do support basic association when testing using the PC software. It is a Z-Wave standard but maybe it is difficult to implement directly in ISY, however, it seems the ISY does other associations, just not Basic Set (Group 2 in most devices). I would be happy to have an association tool in future Polisy instead of than having to use an additional S2 dongle and PC. Currently I haven't used this feature myself yet beyond testing, because I have mostly Insteon, but there is one room where I plan to setup a virtual 3-way using Z-Wave this would be perfect for. Here is direct link to my post.

Z-Wave basic associations still not fixed/working in this update. I am hoping with new Z-Wave board etc. there will be a utility to do associations.

I discovered that if I query the respective "Access Control Alarm" then it also queries the Barrier node.

Mine does the same.. I think the term "grayed out" is meant to be non-clickable/selectable. If this is the case then there is no BIOS update available. If you can Enable TPM then you have latest BIOS. Make sure you don't lose password, or wait to enable when this is required. You can always disable the TPM again but not sure of the consequences have to reset besides the warning of may not be able to restore backups - maybe has something to do/is a requirement for Z-Wave security and Matter down the road?

@oskrypuchI see the Window Alarm nodes show on/off and also seem to update on query. I have learned to like the open/close node response instead of on/off though I am going to power cycle the zen17 on my garage door when I get home and see if it sends signal to ISY on restart. Not a huge deal for me because my program that checks for garage open > 1 hour will not run because it looks specifically for "open"... I suppose there could be some case where power goes out while door is open etc... so maybe I will change program to use the windows alarm node.

I noticed that when set for input type 7, the new nodes ZW XXX.1 Barrier and ZW XXX.2 Barrier do not update on query from IoP. The only time they update is when the sensor is physically changed eg. closing/opening the contacts - in my case opening/closing the garage door. It is supposed to recover state from power failure, but if Polisy also reboots then it seems that IoP will not get updated until the door state is changed - not even with the 3am query program. On my other Zen17, using the input type 10, query works on the Binary Sensor nodes as intended and the 3am query program picked up the state of my unused Binary Sensor as Off. Anyone else have this issue?

Great news! Please sign me up if you need testers for Z-Wave Will the new software continue to work with the Zooz dongle or is the plan to only make it work 100% with the new dongle?

I just upgraded both my Zen17 to latest firmware and reconfigured on the Polisy. One of my Zen17 uses input type 10 on both of its inputs. Its purpose is to sense when my septic lift pump runs using an AC sensor. It has been working fine and even after the update - eg. I can short a paperclip to it and turns on/off. My other Zen17 is for garage door and I decided to try input type 7 this time and I like it better - because it shows door open/closed instead of on/off (when my door was closed it showed on with input type 10, now it properly shows closed). Here are the instructions I used to set garage opener... For Garage Door --------------- Will hook up the switch and the sensor on separate sensor/relays just in case the isolation is not set correctly. Reset Include in ISY Set for Door Open/Close sensor Set Parameter 2 to 7 Set Parameter 3 to 7 Exclude/Include in ISY This will add additional nodes for each sensor Set Parameter 10 to 0 Set Parameter 11 to 0 This isolates the relays being triggered from the inputs Garage Door Sensor (Sensor 1) ZW XXX.1 Barrier 1 Garage Door Switch (Relay 2) ZW XXX.2 Binary Switch To set simulate momentary 1 second Parameter 8: auto turn-off timer for Relay 2 Parameter 17: auto turn-off timer unit for Relay 2 Set Parameter 17 to 1 (seconds) Set Paramter 8 to 1 (1 second) *** must use 4 byte to write Parameter 20: Reverse the reported values for your selected input on S2 C terminals (select same value as parameter 3 eg. 7) (not reversed set to 0) Closed on Sensor 1 will show door closed Set Parameter 20 to 7 if your door sensor switch is NO when closed.

Nice so I can actually show my garage door is open now correctly. I’ll get the firmware and get later.

Maybe dev could add some more virtual device types like ones with low med hi etc.

The devices will be on the stick. Just inbox and try the update - not sure If the update will work or not like that however. backup stick reset do firmware update then restore Or get a second stick. see my topic elsewhere here about firmware fun.

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.

The later Insteon dual-band switches seems more reliable... and in the past year I have changed out most of mine to those and my Insteon is now 100% reliable. I have about 40 Insteon devices and currently 12 are PLC only... I have about 8 RF models as spares that I can switch out as required. I had Insteon since it first came out, and went through lots of pain and grief... their microswitch recall. The PLC only models are very poor at communication by themselves... I remember using phase couplers and always had reliability issues. What I don't understand is why no other Z-Wave switch manufacturer copies the paddle design off an Insteon switchlinc... did Insteon have some patent/copyright on that design?