lilyoyo1

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.

Shouldve bought LG. Less hurdles to jump through. 😀

Are your scenes configured correctly? Make sure the device is set to turn on in the scene vs off.

The new UDM app does not work with the 99i. Hopefully that was a typo and you meant 994. If so, upgrade your 994 to the latest 5.xx firmware and you could give that a try.

You're in the wrong place for this. You need to contact ecobee directly on their website. These forums are geared towards universal devices line of devices.

This was answered in the thread you referenced in the post marked solution. Same board different connectors

I didnt know a new version was available. The changelog that details what's in the update is usually on the nodeserver page when you click on it.