brians

I was running two separate Z-Wave networks for a while. When I moved from Home Assistant I moved Z-Wave devices from my Polisy manually by first excluding and then including in Home Assistant (Z-Wave JS). Both networks worked fine but I am only talking about 40 devices in total. I had my Polisy Z-Wave still working for long time as a test, but I recently disabled the radio since is useless to me. I only use Polisy for my legacy Insteon in case anyone reading this is wondering. I am not sure what would happen if had multiple larger Z-Wave networks, but I suspect it would still work because Z-Wave is encrypted to a particular controller so the other network will just ignore, and I don't think there is too much network chatter with Z-Wave. With Zigbee you can change the channel to run multiple coordinators, but cannot after adding devices or they need to be repaired. The Zigbee channels sit in the valleys between the WiFi channels' peaks so not really an issue with interference(at least I never found one and I am using all three common 2.4Ghz WiFi channels).

Updated mine using AC. No issues.

No it is in admin firmware and says firmware 5.8.3 is up to date. I’ll try when at home later.

Don’t see update available on UD Mobile. I’m too lazy to open the admin console on my PC.

No sorry I was just curious about the long range since I always thought it was only with 800 series but your post made me learn something new today Hopefully UD reads this thread and clarifies if it supports LR or, if not, will so in future.

Curious why you want to use long range mode anyways? Are these plugs a long distance away and not work otherwise? From what I read if paired in long range they don’t mesh. This feature has only been out less than a month anyways. https://github.com/zwave-js/zwave-js-ui/releases/tag/v9.10.0

Maybe parameter 11-15? https://www.support.getzooz.com/kb/article/608-zen32-scene-controller-advanced-settings/ I never tried setting brightness to zero and have done way you describe. I don’t think it would make much of a difference and has advantage of being able to set brightness separately without being changed.

That is normal how zen32 works with the buttons. You have to make programs to make buttons work correctly (I made a post somewhere here how to do). Sort of a mess how to do in iox and not very reliable and sluggish I found since it seems to process zwave events slow.

Was bored tonight and was on 5.7.1.1 on Polisy so thought I would do an upgrade. Bonus... I got 5.8.0

Insteon, especially older devices, are not very reliable. If you tell us how old some of the devices are by providing first digit of Insteon ID, or revision number then that could help figure out. If they are very old chances are good that you have many of them failing. However, I have never experienced any of mine turning on, but other symptoms would be unresponsive, not turning on, communication errors.. .things like that. How many Inseon devices do you have anyways? You can also try pulling PLM off network for a day or so and see if that resolves, if still continues to turn on then you know it is nothing to do with polisy and PLM.

Looked at the roomie app in the App Store and noticed update 2 weeks ago says “UD ISY Optimized”. Doesn’t mention EISY but what is current problem with EISY and Roomie?

Tried updating using UD Mobile, says there was 5.7.1 but did not seem to update. After a reboot in UD Mobile, only available update is 5.7.0 and current version is 5.7.0. I did update via AC and worked fine. I have a Polisy.

Did you press the button on the Leviton after was blinking? I have a few of those and process I have in my notes is... Leviton: Include or Exclude Press hold till blink, Press again

Yes, and I am sure that about a year ago when I first updated to ZMatter and played with this that this was not the case... maybe something has changed, or I did not test fully, or maybe a firmware update in Zen71 changed the operation how they work. I was testing in Home Assistant basic assoc in Z-Wave JS UI, and came across this looping - after some research I found that I had to do this parameter on one switch to prevent. I don't have much of a need for Basic Assoc anymore anyways since HA seems much faster and more reliable at processing Z-Wave.

In my experience, I had to put in some delays after changing parameters which program functionality relied on... eg. disabling a motion sensor. But regular turning on/off is not an issue.

Why don't you make a program that opens/closes them all at the same time?

You could keep including and excluding same device over and over until it rolls over the 232 node limit LOL.

They don’t remember zwave network after replacing battery? That seems strange. You can try replace zwave device ( if it still is an option ) but that is hit and miss in my experience. IoX unfortunately uses the actual zwave node ID when referencing the device in programs etc. The node ID is auto incremented by the hardware controller and one cannot control this otherwise.

That Insteon address you gave is old and is not dual band and PLC only. Is the majority of your Insteon network old, or lots of RF dual band? I am guessing that your backup messed something up (or was messed up before) and now you need to restore some of your switches. During your restores you could have made your Insteon mesh network unstable, which could cause a whole bunch of switches to fail that relied on one key switch to mesh from. Try restoring different devices and hopefully your network may come back. Maybe remove the device from wall and bring close to PLM and see if it will work. I had lots of issues with Insteon, and I would get similar errors... I started a project a couple years ago to resolve this and would purchase used Insteon switches off Ebay (insteon shortage, months prior to the company closing) and replace my PLC only ones. Little by little my network would become more stable, until one day I replaced a switch which seemed to resolve everything... no errors, no opening AC and error cannot communicate with device. I still have 12 PLC only switches installed, and 8 dual band spares I am keeping to swap out as needed. To give an example how Insteon mesh can be finicky.... one room that had three older Insteon PLC switches experienced severe problems linking and being unreliable, was solved by changing just one of the switches to a newer dual band RF... after than it has been flawless for almost 2 years now... it is using the dual band switch to help bridge to other dual band switches that have better communication path to PLM.

Power cycling resolved issue and is back up now. I’m gonna throw a smart plug on it so I can power cycle remotely.

Yes I will update when I get home. I think this has happened in the past... seems like OS is hung up because I still see on network.

Oh I just did an updated and responded over in PG3x trying to update to 3.2.13. My polisy now seems dead now I can ping it but no response after rebooting through ssh because it was not rebooting via AC, will see what happens when I get home. I was already on 13.2 Edit... resolved by power cycling.

On a Polisy, after update get this message.. And then reboot... and so far has been like 3 reboots with same message each time connecting to AC. Logging into PG3x Then I checked the uptime in IoX and has been running since Oct 13th. So reboot is not working from AC. I ssh in and confirm did not reboot. so I reboot via cli Does not come back.. can still ping and get a response but no ssh and no AC Have to restart system when home by unplugging and hope it comes to life. Seems like way too many update issues lately. An update like this should not take down the system like this. After several tries

Sounds like you are doubling up on things and potential to cause excess traffic and loops. I would simplify things for now until you get stabilized and good performance eg. in case of Lutron, I would only pick one platform to install the integration on.. .either IoX or HA but not both for now. I do not know for sure, but issue seems to be IoX slow at processing events which will compound the problem expecially with going Lutron>IoX>ISY Integration>HA, and probably an ACK back other direction. I said earlier that HA updating via ISY integration seems to happen instantaneously, it does for simple things like turning a lights on/off. But any multiple events and feedback from IoX takes a bit longer, scenes and light groups in HA generating more Network, Insteon traffic causing slowdowns to ISY. However, I do not experience this issue re: light groups/scenes with any other HA integration that I use ( eg. Zigbee, Matter, or WiFi lights). Therefore this seems like it is not an issue with HA but with the ISY Integration, IoX, or way Insteon traffic works.

@CoolToys Some zigbee devices may auto pair when powered on, when you set IoX zigbee coordinator to add devices it will pickup everything that is in pairing mode. You could be picking up neighbours blinds but how do you know neighbours have same ones?