lilyoyo1

It's compatible which is why you're able to add and operate both devices albeit unreliably. I would say this behavior is indicative of your network or local environment. Unfortunately zwave has always been a poor automation protocol and finicky which is why I e never jumped fully on board except for a few specific use cases. The reason why I brought up 700/800 benefits is due to the longer range and requirement the all devices support nwi/nwe which would've allowed you to exclude/include from your final location. The much longer range would've helped as well. I've never used Shelly and I know a few people who has tried zooz 800. They weren't happy with zooz but since I didn't troubleshoot their issues, I can't speak on it. I've always been in the "you get what you paid for" boat so Shelly never interested me. Have you tried to factory reset the devices vs exclude only? Is your isy on the latest firmware in addition to both firmware AND UI matching? In regards to your question about the range extender vs regular repeaters, there is a difference. Both accomplish the same thing but the range extender has the additional benefit of amplifying the signal.

700/800 series are backwards compatible so they should work but you would not get the benefits of those 2 series. Everything would operate as 500 series devices. Keep in mind that if any of your neighbors along the path to those devices are not 500 series, you'll be using 300 series capabilities when trying to communicate with them. I would bring the devices close to the isy. Exclude and re-add, then take to their final location. Once done. Run a Heal. While you may still have issues, the self healing properties of zwave will hopefully improve performance over time.

possibly. LEDs couldve went out too. If you try to add close to your plm and it still fails then the access points wouldnt be the issue. All insteon devices repeats the signal. With 25 devices, the access points are probably irrelevant.

That is incorrect. The 2413S gets plugged into the ISY port A directly.

Here is what Michel last stated on the Matter. Maybe he'll chime in and answer your questions. If not, you may have to email udi directly. Personally, I'm not interested in matter. I've always been one to use a few devices that does exactly what I want with my chosen system instead of multitudes of different devices. From the stories I've read on matter, it's a $#/+ show, which makes me desire it even less...I do think it's great for those who depend on voice assistants and those with multiple different types in their home (at this time). Since that's not me, it has limited appeal.

I'm confused. How did you try it with zigbee if you don't have the zmatter board?

Depends on how the program is written. Post your program and we'd be able to help.

There may have been something wrong when you migrated your zwave devices. I used to have that lock. Everything you're stating that's missing was/is supported.

You can try Inovelli or ge enbrighten switches/dimmers. They work with companion switches that replace your current zwave devices for direct control. Zooz does support direct association but that's an extremely poor substitution.

I don't use Insteon anymore but when I did, I had a few tricks that I used to save link/scene space. For basic multi-way setups, I simply linked the devices together outside of the isy. If a simple timer controlled those devices, I'd use programs to control each of the switches individually (Controlled switch first). That way, I received the benefits of linked devices and the program turning off the individual devices was irrelevant since I wouldn't be looking at the individual switches. For larger items such as keypads, I'd create scenes with all devices set as responders to minimize how many links I used by setting controllers in the scene. I would then create a program for my control conditions. Additionally, I would reuse scenes where I could. For example, each room had it's own all off button. Each device would be set in the scene as a responder with the button for triggering it being programmed. I then used those all off scenes as part of my away program instead of creating 1 big away scene. My all off scenes were also configured to be my goodnight scenes. Devices that I wanted to turn on (would be configured on and devices that needed to be off were configured as off. When I hit the goodnight button, the program would turn the scene on. Then after the final count, would turn the scene off where applicable.

I've tried most systems out there over the years and none really beat the isy family overall. It's not perfect but none are. Especially when it comes to insteon, there's no way im choosing HA over eisy/polisy. It's simply more elegant in the UD family of devices. The only controller that i've used thats better is control 4 but that like comparing a Rolls Royce to a Genesis (there's a reason for the difference in cost) I use Radio Ra3 so I no longer use my polisy since it cannot control my RA3 keypad buttons (works with regular dimmers/switches). However, if it did, I would have upgraded my polisy to eisy to use with my Ra devices over Control 4. One thing i've learned in life is experience is the best teacher. Since you already have the hardware, give it a try. Make a back up of your eisy to make going back easier should you decide to. Swap over to HA and run that. If you like it better then stick with it. If not, you can always go back to your previous setup.

I'd verify that your scenes are set up correctly. More detailed information about your setup would help.

Create a scene where you want all devices to be when fast on command is issued (all devices should be responders) Create program that triggers that scene upon a fast on command.

Many folks on here talk about and use hue. I used to use hue when I used my polisy. I believe it works natively with it now

Go with what Tazman said. You must operate the scene when using the admin console. Using the device itself will only operate that device. What you are experiencing is proper behavior.