dex

Update: Oddly, without any additional action, the system came back online after 9+ hours. I'm grateful it's back, but I would like to know what caused it all.

@Geddy Yep, I checked that earlier, but I forgot to list it in my actions taken. My subscription renewed in September and good through 9/2025.

I see these momentary offline gaps on my system, as well. My offline-to-online gaps are typically 3 minutes long (not 9 as others have observed). This has been going on for many months, perhaps more than a year, and has appeared to be harmless. I assumed it to be some maintenance, since it is always off hours/overnight. Today, however, the system went offline at 4:48 AM (Pacific time) and has not returned online. I can sign into the Admin Console on a PC and navigate and control devices. Programs are running locally from my Polisy execute just fine (e.g., exterior lights were turned off at sunrise). I've done a hard power-off/on reset and reboot from the AC, but when the device comes back up, it works but is not connected to the ISY Portal. In the Configuration / Portals tab, my Portal Integration shows "Offline" and "Registered." The Refresh button doesn't alter the status — still offline. Meanwhile, if I sign into the ISY Portal site via a browser, it says my ISY is offline. The UD mobile app says the Polsy device is offline, but I can ping the Polisy IP address. No other internet issues with the other several dozen things on my network, so I don't think network instability or service is an issue. Agree with @bwdavis7 — this feels like a remote-side issue. However, one thing feels like it could be a local problem. Even though the Admin Console on a PC on the same network can access the ISY with no problem, using the Polisy device's IP address (with port number) in a browser gives a "connection refused" error. This typically allows browser access without problem. Any additional troubleshooting suggestions to narrow the cause? Firmware and UI are v5.8.4. Update: I submitted a ticket. I'll post anything I learn that may help others.

my.iso.io is reachable, but authentication fails (displaying "HTTP error 429"). Everything was working a couple of hours ago.

I agree! Amazon Echo Gen 4, newer Apple TV 4K and HomePods all act as Thread border routers. I’m exploiting that right now to trigger scenes in my Polisy with Eve Motion Sensors (Matter/Thread) bridged temporarily through an Alexa Routine. I just want Matter devices to show up as first-class nodes inside EISY/Polisy so I can replace the lame Alexa Routines for the logic I really want.

Agreed! For this purpose, this is a far better idea than a static button that disappears.

Undo button could work, but it would be bad practice to make it disappear. It could go gray/disabled when there’s nothing to undo, but disappearing buttons tend to undermine user confidence and learning.

Suggestion: Add a checkmark button above the list of notifications. Tap the button to mark all notifications as read. A confirmation dialog is recommended. Dim the icon if there are no unread notifications and make the button inactive. See attached mockup.

Yes, now that I have a working USB cable. Thanks!

Update: I just purchased a new USB extension cable and replaced the first one I was using. Now the Zmatter dongle is discovered and the Zigbee menu is populated! Yay. It was a bad cable. (There is no room on the back of my Polisy to attach the dongle directly due to the power connector and the USB to my PLM.)

Yes, the Zigbee option is ON. In fact, when it’s not on, the Zigbee menu doesn’t show up in the Admin Console. Likewise with the Z-Wave option and menu.

The Zigbee menu says, "ZMatter Zigbee not responding," similar to @KeviNH's post. However, unlike that post, I have a Polisy (not Eisy), I do not intend to use Z-Wave, and my ZMatter module is new and has never been used (whereas KeviNH appears to have had prior functionality and is using Z-Wave). I attached the USB dongle and followed the instructions for Eisy (there are some "eisy/polisy" references that imply the instructions apply to both), but I cannot get it to work after a couple of days of troubleshooting. Before I go deeper into troubleshooting, should this even work via USB on Polisy? Or, do I need to install the ZMatter board inside the enclosure (as shown here)? I am running IoX v.5.7.1 (2023-11-09-11:49:34).

Yes, Zigbee Support is ON and I have tried cycling power (several times).

I did the above before receiving my Zmatter board. It arrived yesterday. I'm now troubleshooting how to get Polisy/IoX to recognize the USB device, trying numerous solutions/approaches in these forums. The Zigbee menu in the admin console says "Zmatter Zigbee Not Responding." Ever feel like home automation is designed to be like an escape room?

My Polisy shows up twice in the IoX Finder, once using its local IP address and once using "polisy.local" syntax. Screenshot attached. The Delete button does nothing. I can launch the Admin Console from either line. This doesn't seem to create an issue, but I wonder if it indicates something I have misconfigured. Any action I should take on this? Thanks!

I just got this working, so thought I’d share… This is my interim approach to get Eve Motion Detectors to trigger an Insteon scene: I set up each Eve detector (Matter version) per its defaults, including adding it to my HomeKit network. I have three devices in my home with Thread border router capabilities — an Apple HomePod and two Apple TV 4K boxes. Added each motion detector as a device in Alexa. Note, this required generating a new setup key for the device, but once I found that path, Alexa services added it right away. Wrote an Alexa Routine to respond to the motion detector events to trigger the desired Insteon scene. The scene was already available to Alexa services for my home via the ISY Portal (prior configuration). Motion detected by Eve sensor —> Thread network bridged by Apple TV device —> Alexa services pick up the Eve event —> Alexa-to-ISY Portal signals the scene —> Portal tickles my Polisy and voila, the scene comes on. I don’t have any of the Amazon Echo devices that have Thread built in, though I have ordered one (Echo gen 4). While it’s a bit of a convoluted path, it is working for now — at least until my Polisy has a Matter board (also on order) and, ideally, can participate directly in my Thread network. This would let me cut the Alexa portion of this solution out, which I really want to do because Alexa Routines are very limited.

Nearly a year later… Is there now a path to use Eve Motion Detector (Matter version) with Eisy/Polisy?

Thanks for all the ideas, everyone. I've done another factory reset and before restoring the device, it behaves properly (no beep and the LEDs work). After restoring, then it starts beeping on any use and no LEDs. In the admin console, I tried multiple times to set the Backlight level to 255 (or any other level) and could not get it to come on. Then I discovered an Options dialog for the switch that has a "No LED" checkbox and it was checked. I unchecked it and the LEDs came on. I had no idea this checkbox was there. So, that solved the LED problem, but the button still makes a beep on every press. Changing the Beep level does nothing. In fact, when I set On Level, Ramp Rate, or Backlight, pressing the respective button causes a very quick "Writing>" green status to show up next to the switch's icon. But when I change the Beep level and click that Beep button, the system appears to do nothing -- no "Writing>" status or "System Busy" indicator, even for a fraction of a second. Is there another setting somewhere that I don't know about that controls the Beep setting and how to write that to the device? I'm running IoX v.5.7.0. Thanks again.

I have a dual-band dimmer switch that... Beeps when controlled manually at the switch -- the load is turned on/off with the set ramp rate, as expected. None of the LEDs on the switch come on at any time. Responds fine and controls the load when controlled remotely (invoked via linked buttons, via programs, or from the admin console). Link table reads from the device and matches the PLM link table for that device. I replaced the switch with a brand-new, identical model (2477D) and firmware version (v.45). When I restored power, the new switch exhibited exactly the same behavior. So, now I suspect wiring. I have gone through the wiring very carefully -- great connections with the wire nuts, line voltage verified with a multimeter and is properly connected to LINE input on the switch, and properly/securely connected white to neutral and ground to ground. There is another 2477D in the same 2-gang box, and it works fine (no beep, and LEDs show as expected). What do those four symptoms above suggest might be the problem? Thoughts? Suggestions? Thanks in advance.

Bits of this description are similar to what I’m experiencing, so I’ll give it a go to put some delays in the programs to create separation from the motion event and the first ‘set scene’ command. Makes me also wonder about multiple motion sensors with overlapping ranges — could two of them be triggered (near) simultaneously create collisions that might exhibit this behavior in the system?

Thank you, @tazman. I have completely removed and re-added all implicated devices and the link tables are as pristine as they can get. I even authored the programs as new to ensure there was no stray bits there.

I have a simple pair of programs for motion in my garage. This one turns the lights on with motion from any of three detectors... Gar Motion Detected - [ID 001B][Parent 001A] If '2 Main Level / Garage / Garage Sensors / Garage Motion 43' is switched On Or '2 Main Level / Garage / Garage Sensors / Garage Motion 47' is switched On Or '2 Main Level / Garage / Garage Sensors / Garage Motion 64' is switched On Then Set '2 Main Level / Garage / Garage Overheads' On Else - No Actions - (To add one, press 'Action') And this one turns the lights off after a few minutes of no motion... Gar Lights Auto Off - [ID 0004][Parent 001A] If '2 Main Level / Garage / Garage Sensors / Garage Motion 43' Status is Off And '2 Main Level / Garage / Garage Sensors / Garage Motion 47' Status is Off And '2 Main Level / Garage / Garage Sensors / Garage Motion 64' Status is Off Then Wait 3 minutes Set '2 Main Level / Garage / Garage Overheads' Off Else - No Actions - (To add one, press 'Action') This behavior works perfectly as expected in the garage. However, sometimes, when motion is triggered, completely unrelated lights go on or off elsewhere in the house. Using security cameras, I can correlate 100% of these lights/scenes going on/off immediately after motion in the garage. Roughly 90% of the time there is no random event. But 10% of the time there's garage motion, something goes on or off that has nothing to do with the garage When it does happen, all of my Insteon wall modules will come on every time this happens. Sometimes, there's also a dual-band dimmer switch, or two. Sometimes an entire scene will go on or off (e.g. living room lights via 7 Insteon switches). I have deleted, factory-reset, and rebuilt from scratch the scenes and programs -- multiple times! The specific devices that come on/off vary slightly after I do this, but the behavior persists. If I disable the two programs above, the behavior disappears entirely. This is a persistent, multiyear annoyance. I had this issue when I was on ISY-994 (several years ago) and continue to have it on Polisy (past couple years). I'm currently running IoX v.5.7.0 (2023-09-11). Additional "about" info is attached as an image. Any obscure bugs, behaviors, or hints any of you have would be appreciated. Thanks! - Dex

Show ISY Links Table responds quickly with the same results each time I do it. I haven't forensically gone through each of the 78 links, but there's nothing glaringly incorrect when I inspect list. Firmware and UI versions are 5.6.2. The KPL is v.45

Thanks, @MrBill. It was a pretty quiet time on the powerline network and I've watched the detailed log during the process. There were a few runs at this where I had no other Insteon traffic, but still saw the inaccurate link lists. That said, the behavior you describe (which is good to know about) strikes me as a flaw in how the link inventories are taken from a device. Some error-checking logic would be prudent, it seems. No?

I have a KPL that inconsistently reports device links when I choose Diagnostics -> Show Device Links Table. For example, I just ran that Device Links command 3 times over a 15-minute period. No changes were made to the system. No comms errors were reported. See the comparison in the attached image. The number of links in the KPL always comes up short of the 78 that should actually be there. On a few occasions, I get a "Record Missmatch" for a link or two. Never the same links, and it doesn't always happen. I've done it perhaps a dozen times this morning, and the device table is different each time. When I do the same for other devices in the system, no problem -- the table is repeatedly the same and matches the table in IoX (as I'd expect). I've done a complete factory reset and restore. There was no improvement; the link table is reported slightly different each time. Is this a communication issue that's not generating the "Cannot Communicate With ___" message? Could it be a bad sector of memory? Something else? Any troubleshooting tips before I spend $80 on a new KPL? I'm running 5.6.2 on Polisy.