dex

I've found only one sequence that works for me to add Tapo TP-Link devices to EISY Matter... In the Apple Home app, add the device by scanning the barcode on the device (or entering that Matter ID). After the device is added, named, and ready in the Apple Home app, long-tap on the device tile until the context menu displays, then choose Accessory Settings. Scroll to the bottom of the settings list and choose Turn On Pairing Mode. Get the pairing setup code on your clipboard with Copy Code. Open the UD Mobile app, choose + and then Add Matter Device. Paste the setup code and follow the UD Mobile process. I found that if I take too long doing steps 2 through 5, the UD Mobile pairing fails. I don't know why, but I'm guessing that by then some other meddling system (Alexa, I suspect) is doing things I haven't asked it to do. I don't need to rush those steps, but I start them as soon as I've completed step 1. If I want to change the ramp rate for a dimmer device, I need to do that in the Tapo app. But only after all of the above! Adding the device to the Tapo app before getting Matter going in EISY always leads to failure for me. In the Tapo app, to change ramp rate, add the device, open the device settings, then look for Lights On/Off Gradually. Matter works -- it's just a bit like the power management sequence for restarting the command module in Apollo 13. One wrong move and you have to start over.

I have a routine tied to the spoken word "relax," which worked fine for several years. After getting an early version of Alexa+, it would intermitently interpret "Alexa, relax" as a general intent-based request to help me chill out. It would play soft music, offer to adjust the thermostat, etc. Occasionally, the routine would run and set the lighting scene as it always had. But sometimes, it tried to be a wellness guru. I tried a number of things, but none helped. Then I asked ChatGPT for a solution, and it suggested I just tell Alexa what I expect to happen when I say 'relax.' I said something like, "Alexa, when I say relax, do not offer to help, just run the routine named relax." Alexa replied like, "Okay, from now on, if you ask me to relax, I'll play the routine named relax." It actually worked, and I haven't had any trouble for at least 6 months.

Perhaps mentioned and common knowledge for others, but I had a helpful unlock and wanted to share in case others have had similar challenges... I've had a dual-band (5Ghz/2.4Ghz) Wi-Fi setup for some time. I broke from the default of having the two bands on the same network name (SSID) a few years ago when a Genie garage door controller would simply not work in that configuration. It was 2.4Ghz only, but had serious connectivity issues until I separated my bands into two unique SSIDs. Using ChatGPT to troubleshoot my Polisy/PG3/Matter challenges, it said to ensure that 2.4Ghz and 5Ghz bands are using the same network name. Something in the way devices are commissioned or paired doesn't resolve this network name difference. Short end to the story: I got rid of the Genie garage door controller (good riddance) and merged my 2.4Ghz Wi-Fi back to the same SSID as 5Ghz, and now I can add Matter devices into my Polisy setup (90% of the time it works on first try, even with occasional socket error messages, etc.). Hope this is an unlock for someone else who has also been struggling to get Matter to work on Polisy/EISY.

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