Tried these Matter bulbs. No love.

[oberkc]

10 hours ago, Guy Lavoie said:

Are you certain that sharing it from Alexa worked?

Yes.  I shared it from the Alexa to the google home app.  I do not recall any errors.  I do not recall any mention of a thread network, but this may be my failure to recall.  When I originally added it to Alexa, I did not, and still do not, have the nano leaf app.  Perhaps that is a variable I should play around with.  

 

[Guy Lavoie]

Well, sharing might not be the same as simply going across a router. If sharing implies a proxy relationship, where Alexa receives the request and then talks to the device itself, then it might not be passively routing it. I would have been curious to see what happens if you would have deleted the light in the Alexa app; if google home could have still controlled the light. I'd think that a true "routing" would be a direct communication between google home and the light.

We still have a lot to learn.

Let me know if you play around with the nanoleaf app.

[oberkc]

8 hours ago, Guy Lavoie said:

We still have a lot to learn

I sure do.  I sense that you are a bit more ahead of me.  

 

8 hours ago, Guy Lavoie said:

I would have been curious to see what happens if you would have deleted the light in the Alexa app; if google home could have still controlled the light.

I am almost certain that google would not have controlled it.  When I originally did this, I did NOT have a thread-capable nest hub.  Since that time, I have added a gen2 hub which has thread.  I have since reset the bulb and added to the new nest hub and shared with Alexa (also worked without any problem that I could recognize).  I have since reset the bulb several other times.  

 

8 hours ago, Guy Lavoie said:

Let me know if you play around with the nanoleaf app.

Will do, but it will be a week.  Heading to Utah for some skiing.

[Guy Lavoie]

8 minutes ago, oberkc said:

I sure do.  I sense that you are a bit more ahead of me.  

 

I am almost certain that google would not have controlled it.  When I originally did this, I did NOT have a thread-capable nest hub.  Since that time, I have added a gen2 hub which has thread.  I have since reset the bulb and added to the new nest hub and shared with Alexa (also worked without any problem that I could recognize).  I have since reset the bulb several other times.  

 

Will do, but it will be a week.  Heading to Utah for some skiing.

Hah no, I'm not necessarily ahead of anyone! Just doing some testing and theorizing, all in the aim of learning.

Since the goal of Matter is interoperability, I'm also thinking that sharing is just one more way of achieving that goal, and that indeed control is being done by proxy through the sharing controller. This would be different from the border router, which is to provide connectivity across two physical communications methods. I'm still a bit puzzled at how Amazon describes their border router as being enabled if you configure a Matter device. It's like you need to configure at least one device in the Alexa app for it to activate. Then there's the nanoleaf app attempting to connect an added bulb to any thread network it sees (and fails). Not helping is the fact that when googling the nanoleaf bulbs, Lots of discussions comes up about unreliability and other problems. Many of those discussions are a year or more old, and nanoleaf has been issuing firmware updates. So some of these problems might be fixed, others not.

Enjoy the skiing! 😀

 

[bigDvette]

Guys, I think you are  pissing up a rope until UDI fixes their matter fabric / server for thread.
A device can be a part of 1 or more thread border routers but only 1 thread network. When you are asked if new or existing installing the device, that is determining if it is being added to a new thread network TBR or not.

The nanoleaf app is not going to help you.  You can add the device using Bluetooth and it will see your devices on the existing thread network.

when you add a device to the first matter controller (Apple, Alexa, google, OTBR) you are putting it on the thread network and first fabric and establishing the credentials.  When you share the device you are sharing the credentials to commission on a second fabric.  That fabric talks directly to the device because it has the credentials to do such and does not go through the first fabric.  Each fabric needs a TBR to hat can talk between thread and WiFi / lan networks so that you can talk to that device  on the network.  

Nanoleaf are working fine now.  

obviously UDI haven’t figured out the ability to put a thread device on their fabric which is what it sets up so you can control them from the admin console /  eisy.

Watching the network it seems like it isn’t getting the Mdns messages that would tell it the ipv6 address so it can interview and setup the device.

I haven’t  seen anyone get a thread device working yet.  

 

[Guy Lavoie]

I agree. That's why I'm not overly concerned that Thread not working yet. It's a work in progress, openly identified as beta by UDI. I call it a learning experience (learning about how Matter works) and the sharing mechanism is certainly aimed at making interoperability easier.

Do you have links that detail what you're saying in your third paragraph (about how credentials are shared)? It's the type of general information that I've been looking for. Thanks for that.

[bigDvette]

To be clearer on what I meant.  When you share the device from the first one, you are getting a new commissioning code and when you use your mobile device to commission to that ecosystem/fabric, the app shares the credentials for that ecosystem so it can join.  So even when you use home assistant and declare Apple as the Thread Network, if you commission to HA and then commission to Apple by sharing the device you have 2 fabrics using the same thread network as a matter controller / bridge ...  

This is a good source for matter fabrics and such.

https://matter-smarthome.de/en/know-how/what-is-a-matter-fabric/

[Guy Lavoie]

Thanks, that link spells out exactly the kind of topology explanation I was looking for. I just bookmarked it, and will be reading through it at least once.

[Guy Lavoie]

I just read through the explanations of the various Matter components in the matter-smarthome above. It cleared up so many things and assumptions! It should be posted as some kind of sticky post at the top of the ZMatter forum section.

So a "fabric" is essentially a group of devices that are initially commissioned to the same controller. The big feature of Matter is that any given device can belong to at least 5 such groups, so unless you have a huge number of devices and initially set them all up with a bunch of different controllers (that would be a nightmare) and then try to link the groups together, you can safely share them to a few previously created groups (or fabrics) without problem. I like that. A further constraint is that devices are shared on a single device basis, so lots of work if you're trying to link two groups of several devices. I wonder if some systems might allow some kind of one shot group share.

It also clears up the purpose and usefulness of the nanoleaf app. Other than allowing direct bluetooth operation of the lights ("works without a hub!"), it's handy for viewing and upgrading the firmware in the bulbs (currently 4.1.3) and viewing the thread network that the bulb belongs to once commissioned by a controller, and plays no role in assigning or connecting to a network, because the app itself isn't used to commission a bulb to a controller. I have 6 of these bulbs, so I upgraded them all to the latest firmware, and the name I give them in the app is the last 4 digits of their matter pin code, shown under the QR code. Makes for quick identification.

Now for UDI to complete their Matter implementation 😀

[Guy Lavoie]

With what I've learned above (and with my limited Matter devices on hand) I dragged out my wifi Cync bulb again and added it to my Google Home mini with the Google Home app. Then I shared my nanoleaf bulb (still configured on the Amazon Echo as a Thread device) to my Google Home app using the pin code provided by the Alexa app. Worked like a charm, I can control both bulbs from Google Home. That also shows that the border router in the Echo is doing it's thing. 😀.

Lets keep a good thing going...opened up the Philips Hue app and went into the Smart Home settings. There are 3 options for Matter sharing: With Amazon Alexa, Google Home, or "other". Tried selecting Google Home, which opens up the Google Home app...but nothing happens. Ok, stepped back and chose "other" instead. That gave me a sharing pin code and I used it to add the Hue bulbs (adds all 9 in one shot) to Google Home just like it did with the nanoleaf bulb. All bulbs can be controlled from Google Home. Matter works.

I'm basically where @oberkc is at.

I'll leave my test setup like that as I await the next update from UDI 🤩

[bigDvette]

@Guy Lavoie try updating EISY and adding your nanoleaf bulb now.  I was able to add mine after the update today to _18.  It is a dimmer bulb but only has on-off functionality, but it did commission and I can turn bulb on and off.

[Guy Lavoie]

12 minutes ago, bigDvette said:

@Guy Lavoie try updating EISY and adding your nanoleaf bulb now.  I was able to add mine after the update today to _18.  It is a dimmer bulb but only has on-off functionality, but it did commission and I can turn bulb on and off.

I'll certainly try that! I had the same thing with the Cync bulb: just on/off functionality even though it's a dimmable bulb with colors. One step at a time...

[Guy Lavoie]

Yup, updated to _18 and added the nanoleaf bulb. Only thing I did different is that I shared it from the Google Home app where it was already configured. Contrary to Alexa and Hue, The Home app offers both a QR code or pin for sharing. So I emailed myself a screenshot of the QR code and scanned it off my PC screen (I only have one phone).

[rick.curl]

Last week I tried to pair a Linkind Smartplug LC09003-PLUG-US-4 and I got this error message:.  

Could not get Matter QR
Code rendezvous Type for
MT:4Q0002:E15S60F76G00. 500

At the time I was on 5.9.1.7.  I upgraded to 5.9.1.17 and tried again.  I thought for a minute that it was going to work, but UD mobile finally gave me the error message: "could not add Matter Device. Bluetooth Unsubscribed. 500". Any idea what it is telling me?  

[Guy Lavoie]

What type of phone are you using, Android or iOS? My tests have been with Android.

Tried upgrading to 5.9.1_18?

Edited March 18 by Guy Lavoie

[Guy Lavoie]

One little hiccup I've come across: yesterday the wifi bulb (Cync) stopped responding to commands from the Admin Console, but was still working ok from the Google Home app (from which I shared it). Same thing today. So I deleted it and redid the share from Google Home. Let's see if it lasts longer this time. The Matter sharing codes are only valid for a short period: 15 minutes with the Hue app, 15 minutes with Alexa app...and only 3 minutes with Google Home. Because I'm emailing myself a screenshot of the code to scan it, this is kind of tight. Google should loosen up a bit.

[photogeek54]

Seeing some progress in support for simple matter device I upgraded to 5.9.1_18 and tried to add a Tapo s505 simple on/off matter WiFi switch. I used the ud mobile app to add via QR code . Go this error:

 

Could not Write characteristic: 18EE2EF5-263D-4559-959F-4F9C42 9F9D11: The specified UUID is not allowed for this operation. This may be caused by an iOS security measure that requires developers to install a developer profile see https://docs.silabs.com/mobile-apps/latest/mobile-apps-matter-demos/05-enabling-developer-mode

 

[rick.curl]

On 3/18/2025 at 12:07 PM, Guy Lavoie said:

What type of phone are you using, Android or iOS? My tests have been with Android.

Tried upgrading to 5.9.1_18?

Android.  It's a Google Pixel 7. I did upgrade to 5.9.1.18, but no joy. Looking forward to getting this working. I really need to be able to control a few devices via Wifi instead of PLC or Insteon's mesh RF system. We've got a big piece of property and our Wifi network has outdoor repeaters.   

[Guy Lavoie]

Do  you know for a fact if IPv6 is working on your network. It's the only other thing that comes to mind. Also, do you have Google Home? If so then try adding the plug to that, and then getting a sharing code from the Google Home app (and try scanning it in UD Mobile).

[rick.curl]

2 hours ago, Guy Lavoie said:

Do  you know for a fact if IPv6 is working on your network. It's the only other thing that comes to mind. Also, do you have Google Home? If so then try adding the plug to that, and then getting a sharing code from the Google Home app (and try scanning it in UD Mobile).

Good catch! I had missed that IPV6 was required.  Got it turned on now, but I'm still getting "Could not add Matter Device. Bluetooth Unsubscribed. 500"

I don't have Google Home.  I can successfully add these smart plugs to the Aidot app (from their manufacturer). I did reset the plugs to factory default before trying to add them to the Eisy.

[Guy Lavoie]

13 minutes ago, rick.curl said:

  I can successfully add these smart plugs to the Aidot app (from their manufacturer). I did reset the plugs to factory default before trying to add them to the Eisy.

Does the Aidot app offer you Matter sharing codes? Otherwise, you'd need to try a different device. I only tried a GE Cync bulb with Matter over wifi.

[rick.curl]

15 hours ago, Guy Lavoie said:

Does the Aidot app offer you Matter sharing codes? Otherwise, you'd need to try a different device. I only tried a GE Cync bulb with Matter over wifi.

Aidot does offer matter sharing, but only to other users of the Aidot app. Google Home and Smarthome will both require that I install a matter hub. I thought Eisy would serve as a Matter hub. Will Eisy eventually support adding Matter devices without having to add another hub or gateway? I'm confused.

[Guy Lavoie]

15 minutes ago, rick.curl said:

Aidot does offer matter sharing, but only to other users of the Aidot app. Google Home and Smarthome will both require that I install a matter hub. I thought Eisy would serve as a Matter hub. Will Eisy eventually support adding Matter devices without having to add another hub or gateway? I'm confused.

A hub or border router is needed for Thread devices. No need if your device is wifi or wired ethernet. I'm confident that eisy will eventually be able to communicate with Thread devices using the ZMatter dongle (Thread uses Zigbee for it's physical layer).

Not sure I understand your "Aidot only" sharing. The very idea of Matter is being able to share devices across platforms. 

You bluetooth error message seems to imply a communication problem with the device. You really need to unpair it from any other system (Aidot) if it's already commissioned there and you can't share it. A factory reset is often how you can do that.

[MDoughney]

After upgrading to 5.9.1_18, I'm having partial success in adding a Matter 2 channel switch module. The process seems to get rather far along before failing with these errors in the Matter log:

[2025-03-25 01:59:46.758] [E] [chip] [CTL] Failed to perform commissioning step 29
[2025-03-25 01:59:47.157] [E] [iox] Cannot get Matter BLE Rx Data at offset 2849, offset is greater than length available (24)
[2025-03-25 01:59:47.457] [E] [iox] Cannot get Matter BLE Rx Data at offset 2849, offset is greater than length available (24)
[2025-03-25 01:59:48.191] [E] [iox] Cannot get Matter BLE Rx Data at offset 2849, offset is greater than length available (35)

I've attached the full log file and a photo of the device. Clearly plenty of progress has been made on getting Matter to work!

202503250200-zmat