dex

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

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?