Guy Lavoie

I decided to upgrade my eisy this morning (after successfully upgrading my test Polisy when 5.9.1 first came out in February). I ran into the same problem. ssh login worked, but no show in the IoX finder. Tried the power off/power on suggested by Michael above, but no go. So I went ahead with the pkg install instructions you posted, and it worked. Now fully operational again. I now have 5.9.1_13, which allowed me to configure a Matter bulb for the first time. The funny thing is that this morning it installed 5.9.1_12, and then redoing the pkg install after lunch upgraded to 5.9.1_13.

I made some progress, and got a Matter wifi bulb working. See here:

Hear ye hear ye! I managed to configure my Matter Cync bulb!! (start 15 minutes of fame) 🤩 Following my post above, I thought I'd look into the eisy upgrade I just did, looking at version numbers, etc. This is because the Matter addition process had gotten further than on my test Polisy before ending in the error I mentioned. The sysconfig.txt file showed me that I had IoX version 5.9.1_12. So I checked the Polisy, which I had upgraded just after the release announcement had come out in February. It had 5.9.1_7. So UDI has been quietly updating it. So back to the Polisy, since it does have the ZMatter board in it. I click on "Update Packages", and nothing updates, being on 5.9.1 already. Ok...so I ssh into it and run "sudo pkg install -f isy". That did identify that there was an update to install. Updated and rebooted it. Did an ssh back into it to view the sysconfig.txt file and...(funny stuff) it shows 5.9.1_13! Did UDI just issue an update in the last couple of hours? I factory reset my Cync bulb and fire up UD Mobile, and try the add. Same process, entering my wifi ssid and password to configure the bulb. The admin console also pops up a message saying it's adding a Matter device. Crossed fingers, toes, anything I could cross...and it successfully added the bulb! Interesting that it appears as a ZM device, even though it's wifi. Next I'll try the Nanoleaf Thread bulb (in case the dongle is really able to talk to it directly). Just before posting this, I also ran the pkginstall command on my eisy, and it did upgrade to 5.9.1_13. So I'll be testing that too. Maybe the ZMatter dongle is really needed, even for wifi. Other notes: - Looks like they fixed the ssh access, so "ssh admin@eisy.local" works again - Matter device addition really seems to be a bluetooth thing, which would explain why it's done only in UD Mobile. - The Cync bulb only shows up as an on/off device, even though it's a color bulb.

Update: I just went ahead and updated my production eisy (I had only updated my test Polisy up until now). Then I tried adding my Cync wifi bulb to it. Still not working, but got farther. I first deleted the bulb from the google home mini (as told by the Matter adding function in UD Mobile). It detected the bulb and prompted me for my wifi ssid and password. I entered those, and the screen was showing "adding Matter device" with an animated radio wave pattern, but then ended in an error saying "Could not get ZMatter RX Requested ISY not online. 500". Interesting that it mentioned "ZMatter" since this is a wifi bulb. I also don't have a ZMatter dongle on my eisy (It's the board version I have, installed in my test Polisy).

Interesting that during the first days of the 5.9.1 update, no eisy's had problems. But now, what looks like two new, out of the box units have the same issue. Did anyone notice if they were running 5.8.4 when first powered up?

I'd start with the java clear cache (all 3 checkboxes) first. Then manually adding the eisy in the finder "https:/192.168.x.x:8443/desc" Try that

Thanks for that. I just listened to the whole thing. Not very heavy on technical details but it does give a sense of how they're seeing the future. I like how at the very end, they do acknowledge that their hub can only do so much and for the real techies, eisy is the way to go 😀 They do mention the current tariff war at the beginning, and how it will put pressure on prices.

Homekit support will likely be something that will come in a later version, so could be a little while yet.

I just read through your linked post. Wow...looks like lots of early adopter issues cropped up, but you stuck with it! Firmware updates, etc are the bane of early use of new technologies. But it looks like perseverance paid off, and I'm happy for you. The vlan thing is particularly interesting, and sharing your experience will certainly be helpful to others. I'm sure Matter will turn out to be great, but still needs time to get there. Your loose neutral issue in your Powerwall thread can certainly be the cause of many problems, and not just noise. If the two phases of your panel aren't well balanced, it means the many electrical appliances might have experienced high or low voltage spikes. Problems might crop up later. Thanks for sharing your experience.

Well don't forget that 5.9.1 is a beta release for Matter support, and hasn't worked for users yet. You'll also notice that the ZMatter dongle isn't even mentioned yet in the release notes. So the network requirements will likely change as the Matter support evolves. We'll just need to be patient. In the meantime, tell us a bit about your Matter devices, notably the Thread switches. What brand and model are they? How is the reliability? Did you migrate from another smart switch type, and reasons that motivated the choice. Matter is still new and we need to learn from other's experiences.

No reported Matter pairing yet (or if someone did, they're so excited that they forgot to come and tell us!) The mention of wifi settings change was within the eisy itself, to get it working with Matter. I'm theorizing here, but with a controller like the eisy having both hardwired and wifi connectivity, the vast majority of those using it hardwired will already have a wifi router in their setup (who doesn't have wifi at home now?). Remains the Thread support: Some (most?) will probably have a border router somewhere. If not, the ZMatter dongle should provide that capability, at least between the eisy and devices. Most of us will likely get the dongle anyways because it's the only way to get Zigbee. In theory, the eisy could also act as a border router, device to device. Matter is IPv6 whether it's wifi or Thread, so it's a simple packet forwarding function. Maybe there will be a configuration checkbox to turn on routing.

Oops, look like I got ahead of myself. The QR code isn't just an encoding of the PIN code. Other than including some additional information (Vendor ID and product ID) there is also Base38 encoding. Detailed information here: https://www.matteralpha.com/article/how-does-matter-qr-code-work

Join the club. If anyone has had success, they haven't said so here.

You can create a QR code here: https://qrfy.com/?utm_source=Google&utm_medium=CPC&utm_campaign=17317470455&utm_term=make a qr code free online&gad_source=1&gclid=CjwKCAiA5pq-BhBuEiwAvkzVZfy_UW8SDHl3_jj1ioTPcJ5J-vaRQYxDKxsh6VysN1mk_7Pd19OsphoCPfQQAvD_BwE Just choose "text" and enter the code as text, as I've done here:

Wikipedia has some links, and describes the evolution of the standard from it's beginnings. There is a link to github for developers https://github.com/project-chip/connectedhomeip There is a certification process, etc. Read up on Matter here: https://en.wikipedia.org/wiki/Matter_(standard) For most of us here (as UDI users), having Matter compatible node devices is almost secondary, as we'll already have our systems established around one or more existing technologies, whether it be Insteon, Zwave, etc. Matter isn't really introducing any new topologies. Again, the appeal of Matter is interoperability of existing systems. If you have both Google Home and Amazon Alexa devices, you'll be able to get them communicating more easily, without reverse engineering, plugins, etc. You'll also notice that UDI's announcement mentions "HomeKit plumbing". That must be linked to the addition of Matter support. Apple has always been the outlier. The fact that they're part of the group that got together to create Matter will only help in making home automation more consumer friendly and widespread.

Long press? In UD mobile? You should look for them in the Admin console.

You can find Matter command stuff here: https://community.silabs.com/s/article/Implementing-custom-commands-for-the-Matter-CLI?language=en_US And no, we don't necessarily need new hardware to send and receive commands. Matter is implemented using IPv6 over hardwired, wifi, or Zigbee physical layers. No new physical layer has been introduced along with Matter. Yes, it is a standardized way of interrogating a device to find out what it is, and what parameters it will accept. That's the whole attraction. Up until recently, each protocol had it's own, often proprietary way of doing things. Serial bytes to a PLM to send Insteon, various command implementations sending data over Zigbee and Zwave. Raw bytes to an IP port to send data to various hubs. Then things started to use more similar network layer implementations to save on costs, like HTTP for Venstar and Ecobee thermostats, Hue hubs, etc. Various forms of security too. The physical layers also become more common (like Zigbee and Zwave), but the commands sent across these physical layers were still proper to each device, and often undocumented. Then in 2019 (from the wikipedia article on Matter): In December 2019, Amazon, Apple, Google, Samsung SmartThings and the Zigbee Alliance announced the collaboration and formation of the working group of Project Connected Home over IP. The goal of the project is to simplify development for smart home product brands and manufacturers while increasing the compatibility of the products for consumers. Finally, lets get our stuff to talk to each other! The idea was to create a high level API that allowed common commands to be sent to each other's platforms. It might not implement every single feature, but each one could decide what to allow (expose) to be done by "foreign" controllers. That way they could still compete on finer exclusive features. For example allow lights to be turned on and off, dimmed, and set to a color. But things like animation, scenes etc could be restricted to the native platform. We often see that in product feature descriptions. Now with a controller like the eisy, UDI does the implementation of the commands needed for each protocol. They first did Insteon and X10, then added Zwave, then Zigbee, and now Matter. For us users, it always comes down to the same simple command, such as Turn <device node name> On That's what we pay them to do for us 😀

That's the whole reason why we (UDI controller users) are interested in Matter: because it's the first industry lead effort in interoperability. Go look at the dozens of smart bulb products available. They all boast "Works with Alexa" and "Works with Google Home". They all show a free phone app that you need to create an account for. But count how many of those have an open, local API? How many can you include into a scene command launched locally by your controller? Very few. Right now, Matter compatible products are rare. But give it a year or two and they should become as common as those Alexa compatible products. Many smart products are already IP compatible, so they just need new software. The Hue hub is a good example of acquired Matter compatibility. Having Matter compatibility in our favorite controller now gives us futureproofing.

That's the right approach. You've hit upon the one exception with true/false testing: a test for a state variable being greater than or less than a value will retrigger true every time that the variable itself changes value, along with the logic test itself being true. So you are doing the right thing by setting a second variable to one of two values, as a flag that your conditions are met.

You can't have a scene trigger another scene (though it can be done with a program and using the Virtual plugin). Instead, you should simply create a new 3rd scene, that involves all the lights that you want it to control. Individual lights can be responders to dozens of scenes if you wish.

To my knowledge (from what I've read on the forum since the release of 5.9.1) no one has successfully added a Matter device yet. We all get that kind of error when reading the QR code. I have these two test subjects on hand myself: the Cync bulb is Matter over wifi, the Nanoloeaf is Matter over thread. They both work with their phone apps (Nanoleaf over blutooth) For the Thread bulb, I don't have a border router yet (keeping an eye open for a deal on a used 4th gen. Amazon Echo) though I would think that eventually, the ZMatter dongle should be able to do that directly.

It's only there if you're using the ZMatter dongle. If you have the Zooz dongle, there is no backup option in the menu.

If a common cause was identified, it wasn't mentioned here... But it's interesting that only some Polisys got bricked, and no eisys as far as I know.

Instead of using "control" (is switched on) use the "status" for the If command. That way the Wait statement will execute for it's time interval. Test it with a short time initially, like 15 seconds.

Some of us are keeping them as a spare, and test system. That's what I'm doing with the one I acquired used (I got it after I got my eisy). A Polisy is still capable of running the latest IoX version.