lilyoyo1

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.

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.

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.

Tazman is correct. I didnt read his message close enough. He's activating the secondary switch of a 3way (non-load) instead of the scene itself. Since he's activating the device, he's only controlling that device.

Have you tried File>restore PLM, then File>Restore Devices?

Isy or eisy? Isy integration would be zero chance since it's obsolete and no more updates are coming for it. Eisy would be based on a developers interest. While wiz may be big for you, it may not be big enough for the eisy community (developer or udi) to justify the time and effort to develop, maintain, and support a node server for it.

The only benefit would be not needing a plm. It would require a rewrite of insteon code since insteon is not zigbee based. Since you're wanting to use the eisy anyway, there wouldn't be a noticeable difference in performance.

As others have said (and linked to), 5.3.4 is the latest (and last) update for the isy994 due to it being eol.

Insteon doesnt have to support Matter if the eisy supports it. Your devices would talk to other matter devices via the eisy.

Firmware and UI?

Only udi would have that info

It's not weaker. Devices need to be close to the isy when adding

They've said multiple times they're working on Matter and a few other things. UDI has never been one (until recently) to give set timelines which has scome back to haunt them so I haven't seen that lately.

As others have stated this is incorrect information. Reality is, with 100+ devices in his home, it would be next to impossible for the phases not to be bridged. He would have to purposely set up his devices in such a way to make that happen. Besides, everything works except 3 devices. That's at least 97 other devices (by his numbers). It can be assumed by shear numbers that they are on both phases so everything is phased.

I'm with @IndyMikein that it doesn't appear to be a plm issue. If it were the plm, you'd be having widespread issues. The beacon test is worthless as well. With hundreds of devices, your whole house is pretty much covered so it's pointless. I'd take the problem modules and manually link them together to see if they work (with whatever is plugged into them unplugged) when physically controlled. If they don't work then you have bad modules. If they do work, then plug your devices in and see if they still talk to each other. Once done, you can either factory reset them and then restore each from your isy or follow the unlinking procedure found in the manual.

That should not have erased it from your ISY though. For example, I have zero insteon devices connected in my home. My polisy is still connected so I can test Ra3 devices for @bpwwer. It still shows all of my insteon stuff regardless of communication. The message you received normally occurs when the address is mistyped. If you try start linking, and use the set button, that will avoid incorrect address issues.

I'd try to re-add to the isy to see if it really did disappear

Insteon calls it a 6 button keypad since it has 6 buttons. The console has always shown it as a 5 button since the on/off button cannot be decoupled.

Did you click on command and see what options it gave you?

I don't blame you there. Samsung has a better picture quality (though I love LG's oleds). I just can't get past the hoops you have to deal with when it comes to them with Smartthings.