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

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?

Ok, what program logic and/or other devices are related to these devices? Is there something that they have in common, like a scheduled program, or other triggers like motion sensors?

Are these Insteon devices? Dual band? Is it always the same devices? Was it the same devices with the ISY994i?

I had a similar result with Hue bulbs that are configured as Matter devices in Google Home. I used the sharing code provided by Google Home and all the Hue bulbs got added in IoX as Matter devices, all in one shot. Now we have three ways of configuring Hue bulbs: with the Hue plugin, as zigbee bulbs without the Hue hub, and now as Matter devices.

I've been seeing this mention of excessive links a lot recently, in various forum threads. I realize that the PLM supports up to 1000 links, but how many devices or scenes does it take to get there? I have a moderately sized system and if I go view the PLM link table, I get 367, so nothing to worry about. Maybe this is something we need to check every now and then.

Don't give up. You just need to learn a few basics. Start with a simple program that just increments a variable. Look for the "control" event instead of status. Like this: MS entrance on - [ID 009F][Parent 006A] If 'MS Entrance-Sensor' is switched On (notice "is switched" instead of status, because I used control) Then $s_Entrance_ms = +1 Else - No Actions - (To add one, press 'Action')

Update the firmware first. Some Polisys run into an issue with the update to 5.9.1, but is easily recoverable. Best get that done before setting up anything else. I also have a Polisy that I got as a used unit, that I used for testing and as a potential backup unit.

Hopefully UDI support gets you going.

But did you try accessing it by ssh, from a Dos command prompt?

Try logging in by ssh (the password "admin" might work for that. On your PC: ssh admin@<ipaddress>.local and enter "admin" as the password. If that works, then: sudo rm /var/isy/FILES/CONF/0.UCF sudo service isy restart That normally resets the admin console login to the default admin:admin

Yes, sounds like a ticket is next. Let us know how it turns out.

Since you have a Polisy with a separate zigbee network handy, have you tried pairing one of these non responding bulbs on that network? As a test. Is there a factory reset that you can do on them (usually powering them on and off several times in a short period)?

You mention "hub bulbs" at the beginning but then mention "other zigbee devices". Are they configured as Hue devices with the Hue plugin, or as straight zigbee devices?

Plug in module, virtual switch... whatever works for you as a unique indicator of the status you want to look for in your program to control a scene and other non-scene devices. It would be easier if UDI added a "If scene on/off command..." in IoX, but at least we have a workaround. Glad it helped.