paulbates

The big manufacturers (Google, Apple, Samsung, Amazon) that are working on creating the matter spec have it working to some degree, but smaller integrators (Homeseer, Insteon, UDI and Home Assistant) are working on their non-beta matter offering of their respective products and across the big manufacturers' product. At this time you are an early adopter of matter. There are numerous posts here on that topic

This post rang a bell to when I set my eisy up about a year ago. The problem seemed to go away after leaving the program sit for a day or 2 and the problem has never returned.

Looks like you've taken logical diagnostic steps. A suggestion, since its not mentioned by name, is to leave iox / AC running and turn on the event viewer and set the level to 3 at the bottom

I sold my last house last year with the ISY. The oldest devices I had were inlinelincs and Icon switches from 2006/2007 with low addresses but no way to remember what they were. I moved my Christmas decorations, and in the box were 2 lamplincs v2s, 01.86.xx and 01.87.xx... still in service in the new house and work fine. Moving forward, I started this house about a year ago with a new eisy and new insteon devices. The range of newly purchased devices is: 47.xx.xx to 70.xx.xx

An option, if your programming is really simple, is to replace the isy with an insteon hub. While the isy is flexible and has more possibilities, the insteon hub is relatively easy use and less expensive. You insteon devices should work with it

Right click on Deck Lights and pick "Restore Device". Compare and test again An additional method is to factory reset Deck Lights, that will clear all links, and then "Restore Device".

Take a look at the solution, here

It's possible a link got lost in the shuffle. Put the the sensor in linking mode, right click on it in iox and pick restore device, restest

It's a long shot, but sometimes the contacts of the card are corroded. Rub over them with an eraser and the wipe with alcohol. It might work and is easy to try, and it can't make things worse.

Search google with "XPF X10", and also try "XPNR X10" The XPF and XPNR are wire in filters for x10 but can work in some cases with Insteon. I used the XPNR for line noise from noisy electronic low voltage lighting transformers that affected insteon. The XPF is rated for 20amps but is kinda big. Take a look at these. I can't guarantee results in your case, but there are limited things to try.

It does... plugin = polyglot pg3. You posted under eisy so I assume you have that, if so you already have polyglot installed. There is a learning curve for sure Another option: if you have the UD portal, use the UDM mobile app and notifications can be sent to it relatively easily, probably not a big leap from your att texting, making some mods to programs. You won't need polyglot. This may be the place to start.

The PG3 notification plugin has a free version, and also a pay for which I use and recommend. I use the notification plugin to send notifications to the pushover app, it's $5 one time, and it organizes my notifications in to different folders I definr. It keeps my text app open for family / friends communication and I can look at pushover notifications when I need to.

Wireless devices do use the plm, it has both powerline and rf radios

I'd use the powerstrip as a control for your rebuild. Plug everything in there to test, even if you have to remove something you got working to make room. We can get to the phase bridging once you confirm the devices do talk to the plm

Thanks Mike So it sounds like this can be replicated in iox programs in a scene of Insteon devices: scene1 contains 3 switches in this example If Status switch 1 is (on or >0) Or Status switch 2 is (on or >0) Or Status switch 3 is (on or >0) Then $scene1 = "1" ... then programs function off of $scene1, or other actions. And a converse version of the program to turn it off using "and"s and setting $scene1=0 I see why it is that way, and don't know how else it could be approximated