Guy Lavoie

Try powering off your eisy and rebooting. I've had to do that after configuring the dongle.

I'm not aware or remember anyone directly configuring a new Matter device on the eisy. I tend to believe that this just doesn't work yet. I got started with a Google Home mini that I had bought off marketplace for $15. It had been sitting there unused for over a year until Matter came along and I discovered Matter was supported. So I've matter of factley been configuring new devices on that first, then sharing. First configuring a new device on the eisy wouldn't be the best idea at this time anyways, because UDI doesn't yet have a function to create device share pins or QR codes. They're just concentrating on getting the devices themselves to be added and properly recognized through the interview process. Start small. Get a Matter bulb and give it a try. If you have Alexa, that also supports generating share codes. As for your question about HA and Matter, I'm not a HA user but anything that supports Matter and has a network connection should work with a Matter wifi device. Only Thread devices need a border router. Back to my KAJPLATS bulb: I'm not convinced it's a Thread device. As a test I unplugged my Alexa Echo (ie: my border router) and the bulb still worked from the eisy. So it's probably Matter over wifi.

After your turn on Zigbee with the checkbox, did you click on "save" at the bottom?

Well you and I post often enough on this forum to know that we're techies, and love to try new stuff!

The one you want it simply called "Hue". Hue emulator is a different thing. It's a great plugin, very well made. It communicates over IP with your Hue hub (can be a ordinary V2 hub, or the new Pro one), so Zigbee isn't used.

The moment we've been waiting for (well, some of us!): I tested the new Ikea KAJPLATS bulb. I happened to drive by an Ikea store that's not in my area and just had to pop in to see if these bulbs had become available, and they had just received some! The KAJPLATS (gotta love those names) is a native Matter bulb. Up until now, Ikea had Zigbee bulbs (TRADFRI) and their DIRIGERA hub, which exposed them as Matter devices. The TRADFRI line is being replaced by the KAJPLATS products. They will have other Matter products in due time, including sensors. As has been the case with just about all Matter devices so far, directly adding it to the eisy doesn't work, but adding it to another platform such as Google Home and then sharing it with a pin code to the eisy works fine. The Ikea documentation and specs are minimalist, to put it mildly. The bulb I have is model # LED2405G8NA. Looking over the box, you wouldn't know it's a color bulb by any of the text. A colored circle on the corner might be the only hint. It also sports the Matter logo, but no Thread logo or text, though from what I can find on the web, it's a Thread device. Adding it to the eisy also flashed a mention of Thread in the progression messages in UD Mobile. Anyways the end result is that it appears to be working fine, and shows the same three node types as the GE Cync bulb, with the X-Y color setting scheme. I'll be testing it more over the next 3 days. If it works as well as it appears to be, it's a nice low cost option. Priced at $9.99 in Canadian dollars, it's a nice alternative to the more expensive Cync and Hue options.

Following my test Polisys updates and seeing no reports of real trouble, I updated my eisy. Smooth as butter.

Up until now, the few of us that have been dabbling in Matter have been doing so on an experimental basis, knowing fully well that having it operating reliably on the eisy might take a while yet. If your thermostats are otherwise working correctly in Apple Home, I don't see any harm in deleting them and adding them back in the eisy. There was also a IoX update just a couple of days ago (to 6.0.5) that includes unspecified improvements to Matter, so it would be a good idea to do that update now if you haven't already.

Do you mean successfuly adding directly, without by using a share pin? Which devices exactly? Just to be clear, up until now I've been able to add both wifi devices (Cync bulb and Cync smart plug) as well as the Thread bulb (Nanoleaf), but always by first adding them to Google Home, then generating a sharing PIN to add it to the eisy.

I have four Somfy shades working fine with the Somfy plugin. It's older RTS technology, and requires a URTS-II serial device and interface. For newer technology, I'd go with Zwave, since you could get a Zooz dongle to use with the eisy.

Well you do have the interface for Matter: it's the network cable. The dongle should eventually add direct communications to Thread devices. I don't think leaving it set to On would have any adverse effects, other than possibly consuming some processing time on your controller.

I had a bit of time this afternoon, and tested this. Not the most rigorous test conditions but enough to satisfy me that the Eero 6 Zigbee network appears to be doing a good job of forwarding both regular Zigbee and Thread commands. My test Polisys are in a basement office at one end of the house, and my work shop is at the other end, about 50 feet away and going through several walls, including a concrete wall with a door. I don't yet have any Zigbee devices in actual use, just a few Jasco modules still in boxes to experiment with. So the only Zigbee mesh network is my 3 piece Eero 6 router setup (well, 4 piece since I also have a 4th generation Echo, located in the office). I configured and tested the Jasco module in the office space, then moved it to the far wall of my shop, and closed the door. One of my Eero 6 satellite repeaters is on the ground floor, almost right above it. Module works fine in the work shop. I then repeated the same test with my one and only Thread device: the infamous Nanoleaf bulb. Works fine, though the bulb sometimes takes time to respond, living up to it's infamous reputation.

I just replicated your program on my eisy, and it worked fine. I suggest you edit the program, highlight each line and click on "update" as if you were modifying them, and then save the program. Sometimes some things don't migrate correctly like that.

The Zmatter board is absolutely needed if you want Zigbee devices. Otherwise for Zwave you have the option of getting a Zooz dongle, and for Matter you only need a border router somewhere in your setup. I still migrated from Zooz to Zmatter because I could, and wanted to start messing with Zigbee.

No, but a device like the Eero could be designed to repeat both types of traffic. That's what I'd like to determine.

If you get Thread devices, then you will have Zigbee... The Matter protocol uses IPv6 and runs over wifi/ethernet for many line powered devices. If it's a Thread device, then the IPv6 is sent over Zigbee. This also means that if the devices (shades in your case) are spread out throughout the home, you'll need to have Zigbee establish a mesh network. The border router simply bridges the wifi and Zigbee networks. This is still quite new to most of us, and I've been experimenting with Matter, as has been @oberkc . Just days ago I've also begun trying out Zigbee on it's own. For example, I have an Amazon Eero 6 router with two satellite repeaters. These also act as Zigbee repeaters for Thread. I'm looking to see if they will also repeat non-Thread Zigbee traffic, given that this is a separate "network" in terms of inclusion, etc. Lots to learn. Just be aware that Matter itself is still quite new, and even newer for the eisy. Just days ago an update was released which includes Matter improvements. I don't want you to go out and get the shades, and be surprised or disappointed if it doesn't work out of the box.

Have you tried rebooting your eisy (with power cycling)? If that doesn't do it, you should open a ticket.

If it's Matter over Thread, you'll need a border router. If the Aqara Hub is also a border router, it should do. You don't need the ZMatter dongle. You'll need to configure the device on the Aqara hub first, then share it to the eisy. There's also the question of whether the device itself will work with the eisy (Matter is still in alpha testing). If it's basically an on/off device, chances are good that it will work.

That's the most detailed explanation I've seen about Insteon communications during scene commands. Thanks for that.

Insteon scenes are one of it's biggest features. Turning off a bunch of lights is just one wonderful application for a scene. I have scenes like that which are only used for turning off devices (those scenes are never "turned on"). And you can have multiple controllers for the same scene, or use programs.

Probably just to keep it easy to restore your backup in case of unforseen problems.

Ok I'll do that, once I get back home later. Thanks for this! It will be better than the Emporia plugs, keeping it all local. 🙂

Ok, restarted admin console, no change. Ran update packages again and rebooted (I had upgraded to 6.0.5 a few hours ago), then reran interview. Still looks the same. Should I be seeing something new, like a consumption field?

I just did that (on the main device node). Interview runs, but nothing has changed on the screen.

I plugged in a LED bulb in a lamp (a Hue bulb in fact, was close by). The last line now shows: Integer DATA devices.59391.endpoints.1.clusters.1794.data.instantaneousDemand = 71 (0x00000047) Then added a wireless phone base station: Integer DATA devices.59391.endpoints.1.clusters.1794.data.instantaneousDemand = 85 (0x00000055) The other consumption fields remains the same.