Guy Lavoie

Well that's one for our collective wisdom... and a good first thing to try if this ever happens to someone else.

That's really odd, and interesting. It's as if even manual operation of the switch somehow requires Insteon communications to be used, or something like that. So are you saying that just powering down the eisy would let all the switches work ok manually?

I have all Alexa devices myself. I got the Google home mini several years ago as a used device for $15, and this is the first time it's come in handy for anything. Most sharing apps (Hue, Alexa) only offer pin codes for sharing. The UD Matter implementation is still beta and I'm sure the remaining options will get added over time once it works reliably.

Do you happen to have a Google Home device, like a mini? If your Matter device is wifi, you can configure it in Google Home, and then use the Google app to create a qr sharing code to add it to the eisy.

Sounds like quite a stretch. But then again, the actual problem observed is hard to believe too! It has to be something totally freaky.

How many switches are you unable to turn on manually? Did they all begin to have this problem at the same time?

Not sure I understand. You seem to be saying that manually controlling the switch ("Manually pushing the switch") itself isn't working (at the physical switch, not in Admin Console), but that they work from Alexa and Home Assistant. Unless a bunch of microswitches have all failed at the same time, that sounds impossible. As you say, if Alexa and Home Assistant are controlling them through the eisy, then it wouldn't be a PLM issue.

Here's a little project if you're like me, without a way to buy the ZMatter enclosure by itself (The Canadian distributor for UDI products doesn't offer it for sale). I started by finding the needed mPCIe to USB adapter, and found this one on amazon. I first tested it with the bare ZMatter board I took out of my Polisy. Then it was just a question of getting an enclosure for it. I also used a USB extension cable, such that the enclosure is now a standalone unit, making for easier placement, and connection to a Polisy (I can't see how the UDI enclosure could be plugged directly into a Polisy, given the proximity of it's power connector to the USB slots). So there you have it, the Canadian ZMatter enclosure...

The slots in the Polisy are mini PCIe

Cool, and thanks for the experiment. Adds to the science! It's pretty well how we would expect things to go with RF jamming. I had already seen a similar effect with commands getting delayed and retried when something was happening with the signal path (I forget the exact circumstances). Insteon is quite effective at that. When I decided to power cycle the mini remote, I first ran my fingers lightly over the buttons to see if any appeared to be stuck, and didn't find any. It could still have been a problem internal to the device.

It's a mini remote, so it's RF only. That's why I suspected it in particular, since I only added it a few days ago, and that it appeared as though RF communications was being impacted (though the was switch I tried was dual band). But I certainly could send out commands from the admin console. It would have been interesting to try to send out a command over RF, though devices controlled only by RF are rare. An Insteon thermostat would be one example. I'm just wondering if others have ever had a similar problem occur. Learning as I go. If it ever happens again, the first thing I'll try will be to power cycle that mini remote.

I was just searching for a thread discussing problems with incoming Insteon status changes not being detected and came across this one, which was recent and left unresolved. I just had a similar experience, where I noticed motion detectors were not firing off programs. Then I tried manually activating an Insteon wall switch and status was not updating in admin console. Yet I could turn devices on and off from the admin console. Hmm, that was unusual: commands going out were ok but not status coming in. The things I tried in order: 1 - reboot the eisy 2- unplug and plug back in the PLM 3- restore the PLM. As that was happening, I also went to the bedroom and took the mini controller I added just a few days ago, and turned it's power switch off and back on. The motion sensors started working again, and going back to the admin console, receiving status updates was also ok. I can't tell if it's the PLM restore or power cycling the mini controller (or maybe neither) that fixed it. Has anyone else ever had a similar experience?

The fact that the status is not updated when this happens seems to indicate some kind of communication issue, or something that is falsely triggering them on. Yet if they all belong to the same scene and they always come on together, then something would be triggering the scene. But I don't see the reason why status tracking would be lost at the same time. Until you reboot your eisy, are you able to control them from the admin console?

Did you keep the PLM from your ISY994i and installed it on your eisy? How old is it?

What turns on the scene? Just a schedule? Other things? Could you post the program?