dex

This page nav issues seems to be a happening again. It’s the same no-response behavior described above — page numbers don’t respond to tap/click and entering a specific page to navigate to just ignores the input. Same problem across Safari and Edge on Windows, Mac, and iPad. Anyone else experiencing this?

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.

Similar question to @robgarrett, but I’m specifically curious if anyone here has tried Eve Home switches? https://www.evehome.com/en-us/eve-light-switch I am intrigued to try them because my experiences with Eve devices so far has been very good. I have replaced my Insteon motion sensors with Eve motion sensors and use them to trigger Insteon scenes/programs via Alexa voice services. It’s a kludgy work-around, but works until UD releases direct support for Matter. So far, I’m impressed with Eve’s overall user experience (hardware design, app design, level of control, integration with HomeKit, etc.). All of Eve’s hard-wired and direct-plug devices (including their wall switches) also serve as Thread Border Routers, which is appealing for the promised overall network robustness.

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.

I am doing a similar thing to use Alexa to bridge Matter-based motion sensors from Eve. Alexa routines are set up to trigger Insteon scenes (my.isy.io —> Polisy) in response to motion events. This requires at least one Thread Router Border device on your network and within Thread range of the Matter accessory. This is a temporary setup, as I am anxiously awaiting true Matter/Thread support directly via UD’s Zmatter accessory. Alexa routines are quite limited, and barely do the simplest things, so I can’t wait to abandon them for Polisy-based automation for Matter devices.

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).