Tried these Matter bulbs. No love.

[xlurkr]

I hope everyone will start adding information regarding the mobile app platform being used with these reports.  Unless I misunderstand @Guy Lavoie's posts, it currently works (for some things WiFI, anyway) with the Android  UD app, but not with the iOS one.

-Tom

[Guy Lavoie]

1 hour ago, xlurkr said:

I hope everyone will start adding information regarding the mobile app platform being used with these reports.  Unless I misunderstand @Guy Lavoie's posts, it currently works (for some things WiFI, anyway) with the Android  UD app, but not with the iOS one.

-Tom

Yes. It works with the android version of UD Mobile. You also need the latest iteration of 5.9.1 in your eisy or Polisy, which as of Monday was 5.9.1_13. From what I can tell, forcing an upgrade when you already have an earlier 5.9.1 requires going in by ssh and issuing a pkg install command.

The first Matter device I was able to add was a wifi bulb. I just got (like an hour ago) a 4th gen. Amazon Echo, which has Zigbee and the needed border router functionality. I should have a chance to install it tomorrow and try out installing my Nanoleaf bulb, which is Matter over Thread. I'll report back on that when I get a chance. 

[Bumbershoot]

11 hours ago, Guy Lavoie said:

From what I can tell, forcing an upgrade when you already have an earlier 5.9.1 requires going in by ssh and issuing a pkg install command.

I upgraded to 5.0.1_13 using the "Upgrade Packages" button, so the recommended upgrade path works.

************ IoX ************
isy-5.9.1_13
Name           : isy
Version        : 5.9.1_13
Installed on   : Tue Mar 11 11:53:58 2025 PDT
Origin         : misc/isy
Architecture   : FreeBSD:14:amd64
Prefix         : /usr/local
Categories     : misc
Licenses       : 
Maintainer     : michel@universal-devices.com
WWW            : UNKNOWN
Comment        : ISY Port to X (IoX)

 

[Guy Lavoie]

25 minutes ago, Bumbershoot said:

I upgraded to 5.0.1_13 using the "Upgrade Packages" button, so the recommended upgrade path works.

************ IoX ************
isy-5.9.1_13
Name           : isy
Version        : 5.9.1_13
Installed on   : Tue Mar 11 11:53:58 2025 PDT
Origin         : misc/isy
Architecture   : FreeBSD:14:amd64
Prefix         : /usr/local
Categories     : misc
Licenses       : 
Maintainer     : michel@universal-devices.com
WWW            : UNKNOWN
Comment        : ISY Port to X (IoX)

 

Did you already have an earlier 5.9.1 when you did that?

[bigDvette]

My issue with the post is that the only devices I have tried to commission using IOS were already commissioned devices when I got the error.  

[bigDvette]

1 hour ago, Guy Lavoie said:

Did you already have an earlier 5.9.1 when you did that?

I had 5.9.1 and just updated and it is installing 1_13 as I watch the log.

 

[Guy Lavoie]

35 minutes ago, bigDvette said:

My issue with the post is that the only devices I have tried to commission using IOS were already commissioned devices when I got the error.  

From my (very limited) experience so far, an already commissioned device isn't "found" by UD Mobile when you try to add it. It just keeps finding other bluetooth devices that aren't Matter devices, then tells you none were found. Factory resetting the bulb will allow it to be found again. You'll quickly learn the joys of factory resets (often by powering the bulb on and off 5 times or so) while experimenting with this.

I finally got my Echo device set up this morning. The Alexa app quickly found my Nanoleaf bulb (Thread) and added it. Then I went into the device configuration and tried to share it, but just like the Hue app, it only gives me a numeric pairing code, while UD Mobile only accepts a QR code. So close...

I'm still trying to find a way to convert a pairing code to a QR code, though that's not straightforward because a Matter QR code contains more then just a pairing code. There is vendor, version, etc information in it too.

[bigDvette]

So, we do have different experiences.  I am using Home Assistant with Apple as my border router.  I updated to 1_13 and don't get same error, HA generates a QR code so that isn't the issue and I'm not resetting my devices as they are paired all to HA and i have not problem sharing the pairing to Apple Home from there as well.  I can scan the QR code and I get "Adding Matter Device" pleas wait and on the UDI Admin console the Add a device to the Matter network pops up with Listening for MAtter devcies to add to network, but it never works. My guess is given people have gotten Matter over Wifi devices to work, UDI is having problems with ipv6 traffic.  For home assistant there were serveral ipv6 hop params needed to listen inside a container. I have no idea of UDI is working.  Now it seems to be a listening issue.

Edited March 13 by bigDvette

[Bumbershoot]

4 hours ago, Guy Lavoie said:

Did you already have an earlier 5.9.1 when you did that?

Yes, I did.

[oberkc]

I just tried "upgrade packages" on mine (Polisy, wired).  Formerly 5.9.1.  No change after upgrade.  Still shows 5.9.1

I am inclined not to ssh for a variety of reasons, not the least of which is that I am more comfortable (less perceived risk) in using the official method and waiting for an official announcement.  

[Guy Lavoie]

1 minute ago, oberkc said:

I just tried "upgrade packages" on mine (Polisy, wired).  Formerly 5.9.1.  No change after upgrade.  Still shows 5.9.1

I am inclined not to ssh for a variety of reasons, not the least of which is that I am more comfortable (less perceived risk) in using the official method and waiting for an official announcement.  

Welll you wouldn't see the incremental upgrade (to 5.9.1_13) that way. You really need to view the information in the sysconfig file to know.  https://eisy.local:8443/WEB/sysconfig.txt  that's how I saw my Polisy go from _7 to _13 when I did the pkg install. I estimate the the pkg install command is "safe" because it's not like messing around with individual files. It really is how packages get install and/or upgraded, albeit usually as part of scripts.

 

 

[Guy Lavoie]

3 hours ago, bigDvette said:

So, we do have different experiences.  I am using Home Assistant with Apple as my border router.  I updated to 1_13 and don't get same error, HA generates a QR code so that isn't the issue and I'm not resetting my devices as they are paired all to HA and i have not problem sharing the pairing to Apple Home from there as well.  I can scan the QR code and I get "Adding Matter Device" pleas wait and on the UDI Admin console the Add a device to the Matter network pops up with Listening for MAtter devcies to add to network, but it never works. My guess is given people have gotten Matter over Wifi devices to work, UDI is having problems with ipv6 traffic.  For home assistant there were serveral ipv6 hop params needed to listen inside a container. I have no idea of UDI is working.  Now it seems to be a listening issue.

Well that's actually good: different tests with different devices. Up until my last test, I was thinking that a border router was strictly a networking device. Now it seems that it's also usually the initial commissioning device that the bulb or whatever will belong to, and be shared by. Mind you, this is a sample size of two users... So contrary to my Hue hub and Amazon Echo, your controller can generate a QR code for sharing.

Now when you say that adding the shared Matter device with UD Mobile "never works", are you using the IoS version? That is known to not be working yet. We're both hampered by one thing missing in the chain. That's how we learn! Let's keep trying.

[737simguy]

Just updated my eisy using “Upgrade Packages”. Compared the sys config files and it changed from 5.9.1_7 to 5.9.1_13

[bigDvette]

On 3/7/2025 at 10:40 PM, MGustin said:

For what its worth this is what I got from support when I opened a ticket 9 days ago.

We are working on a couple of issues. 

The "rendezvous" error in UD Mobile is firmware related for some, but not all, users and we hope to have a new build in the next week. 

The "Could not write characteristic" error is being encountered for all users on iOS devices for Matter BLE Wi-Fi commissioning. iOS is blocking communication to Bluetooth for a characteristic (UUID) used by Matter devices. We are looking into the issue with Apple. So, currently BLE commissioning for Matter devices from an iOS device will not work, but Matter should work for IP, Thread, and previously commissioned WiFi devices.

 

55 minutes ago, Guy Lavoie said:

Well that's actually good: different tests with different devices. Up until my last test, I was thinking that a border router was strictly a networking device. Now it seems that it's also usually the initial commissioning device that the bulb or whatever will belong to, and be shared by. Mind you, this is a sample size of two users... So contrary to my Hue hub and Amazon Echo, your controller can generate a QR code for sharing.

Now when you say that adding the shared Matter device with UD Mobile "never works", are you using the IoS version? That is known to not be working yet. We're both hampered by one thing missing in the chain. That's how we learn! Let's keep trying.

To your statement, I think you are conflating topics.  The post that said iOS devices don't work had a specific error and it specifically stated that it was an issue with BLE Wi-FI commissining and it said Matter should work for IP, Thread and previously commissioned devices.  So based on that, my use of iOS should not be a problem and that is not the error I get.  Thread devices are on an ipV6 network managed by the TBR in my case Apple TBR via Apple TVs.  My HA instance use Apple as the TBR to communicate with the device. The device is commissioned in HA.  I also shared the device via QR code adn commissioned it in to Apple Home which would be a separate fabric and that works fine.  When I share the code to commission in to UDI, it just doesn't ever see the device.  

To further my suspicion I have only 4 matter over wifi devices (sonoff relays).  I shared the code the same way and they commissioned just fine via iOS using UD Mobile.  I moved my UDI in to the same VLAN to rule out MDNS issues across VLANs.  So the issue seems to be with Thread devices which should really only differ in that they work via a TBR using ipv6.  

With HA to commission a device on the Apple Network using Thread you have to share the Apple Credentials to to commissioning App to do the initial commissioning. I assume that is why the statement made was that it should work for previously commissioned devices. 

 

I hope someone from UDI is reading the forums. Happy to help test, I have 98 Thread devices and 4 matter over wifi devices consisting of on/off plugs, motion sensors, light switches, fan switches and matter buttons.

[oberkc]

1 hour ago, Guy Lavoie said:

Welll you wouldn't see the incremental upgrade (to 5.9.1_13) that way. You really need to view the information in the sysconfig file to know.  https://eisy.local:8443/WEB/sysconfig.txt  that's how I saw my Polisy go from _7 to _13 when I did the pkg install.

OK.  I will assume that the upgrade took hold and will try some matter devices soon.

 

[Guy Lavoie]

7 minutes ago, bigDvette said:

 

To your statement, I think you are conflating topics.  The post that said iOS devices don't work had a specific error and it specifically stated that it was an issue with BLE Wi-FI commissining and it said Matter should work for IP, Thread and previously commissioned devices.  So based on that, my use of iOS should not be a problem and that is not the error I get.  Thread devices are on an ipV6 network managed by the TBR in my case Apple TBR via Apple TVs.  My HA instance use Apple as the TBR to communicate with the device. The device is commissioned in HA.  I also shared the device via QR code adn commissioned it in to Apple Home which would be a separate fabric and that works fine.  When I share the code to commission in to UDI, it just doesn't ever see the device.  

To further my suspicion I have only 4 matter over wifi devices (sonoff relays).  I shared the code the same way and they commissioned just fine via iOS using UD Mobile.  I moved my UDI in to the same VLAN to rule out MDNS issues across VLANs.  So the issue seems to be with Thread devices which should really only differ in that they work via a TBR using ipv6.  

With HA to commission a device on the Apple Network using Thread you have to share the Apple Credentials to to commissioning App to do the initial commissioning. I assume that is why the statement made was that it should work for previously commissioned devices. 

 

I hope someone from UDI is reading the forums. Happy to help test, I have 98 Thread devices and 4 matter over wifi devices consisting of on/off plugs, motion sensors, light switches, fan switches and matter buttons.

 

Good, great that you cleared that up for any other iOS users.

[oberkc]

Well...just tried adding a couple of matter devices.  One is a Cync bulb and wifi.  The other is a nonoleaf bulb and thread.  Both were prior added to google home and shared with apple (but not yet amazon).  I now shared both via a qr code from google home.  Both appeared to add (certainly got no errors).  The thread device is taking a relative long time and is adding as I type this.  Edit: and I come back after 5 hours of "adding" the thread device and find that it has not added and is stuck on the screen saying "adding matter device".  The matter wifi device added fine.  I may try some different approaches soon.

Edited March 14 by oberkc

[Guy Lavoie]

17 hours ago, oberkc said:

Well...just tried adding a couple of matter devices.  One is a Cync bulb and wifi.  The other is a nonoleaf bulb and thread.  Both were prior added to google home and shared with apple (but not yet amazon).  I now shared both via a qr code from google home.  Both appeared to add (certainly got no errors).  The thread device is taking a relative long time and is adding as I type this.  Edit: and I come back after 5 hours of "adding" the thread device and find that it has not added and is stuck on the screen saying "adding matter device".  The matter wifi device added fine.  I may try some different approaches soon.

So you were you able to add the shared Cync bulb to your eisy ok. (I'm also experimenting with a Cync and Nanoloeaf bulb). Looks like it worked because Google Home is giving you a QR code for sharing, while Alexa and Hue only give an 11 digit pin code. But it's still strange that the shared Thread bulb isn't working, esp coming from the same Google home app that worked for sharing the wifi bulb. So each bulb gives you it's own sharing code? This is different from the Hue hub which seems to be giving you a single sharing pin code for everything on that hub. Then again, Hue is exposing the devices as Matter bulbs, even though the bulbs themselves aren't.

If/when UD Mobile is updated to accept an 11 digit pin code for adding Matter devices, it will be a lot easier to try it with Alexa and Hue.

[oberkc]

22 minutes ago, Guy Lavoie said:

So each bulb gives you it's own sharing code?

Yes.

 

22 minutes ago, Guy Lavoie said:

But it's still strange that the shared Thread bulb isn't working, esp coming from the same Google home app that worked for sharing the wifi bulb.

Agreed.

I even tried a few variations.  I reset the nano leaf bulb and tried adding directly to UD Mobile (android).  No luck.  I reset the bulb, moved it closer to the nest hub (gen 2)  and added back to google home.  I then shared the bulb from the google home app (android tablet) to UD Mobile (also android).  No luck.  I have tried variations of this using iOS devices with similar lack of success.

[Guy Lavoie]

Well if Google Home is providing the credential information, but the eisy can't then get to the bulb itself (through the border router), then that could explain the problem. There seems to be no real set up or configuration information of the border router itself. I've been wondering about that. Nothing in the Echo device either. I know it's IPv6 to IPv6 so technically it's just a physical layer thing, wifi to Zigbee. It almost sounds too simple.

[oberkc]

5 hours ago, Guy Lavoie said:

There seems to be no real set up or configuration information of the border router itself.

For a standard (matter) that purports to be universal, why would there be?  Why would there need to be?  There was not setup or configuration information regarding "works with Alexa" or "works with google", either.  Are they going to prove the comic to be prescient?

[Guy Lavoie]

Well, I did find one thing about the border router in the Echo being created "automatically". From:

https://www.amazon.ca/gp/help/customer/display.html?nodeId=TSWevY1sX8ADH2LC20

"Compatible Echo devices can act as Thread border routers. These Echo devices automatically create a Thread network and store Thread network credentials on your Amazon account. When you connect a Thread Matter device with your Echo, your Echo retrieves the Thread network credentials for easy setup." 

That seems to confirm my initial thought that routing across it should be transparent.

I did run into another thing that I noticed with the Nanoleaf app. When it adds a bulb, it looks for a matter network. It finds one and says it will add the bulb to the network, but then says that fails, so it gets added as a bluetooth device. Yet adding the bulb directly in the Alex app (add, other, Matter) works fine. From various searches I've done, it looks like the Nanoleaf bulbs are very inconsistent with linking to various Matter controllers. They probably debugged the most common ones like Alexa and the rest remain flaky. 

I'd love to try and just share it from the Alexa app, but until either the Alexa app can provide a QR code for sharing, or the UDI app accepts a 11 digit pin code, that won't be possible.

[oberkc]

I have the echo hub and have successfully added the nanoleaf bulb as well to alexa.  I could also share it with a google nest and control the bulb from either device.  I have also originally added the nanoleaf to the google hub and shared it with the alexa devices.  In all the various combinations I have tried, the nanoleaf would loose connection eventually, sometime reconnecting, sometimes not.

[Guy Lavoie]

Did you update the firmware in the bulbs? Should be 4.1.3

[Guy Lavoie]

2 hours ago, oberkc said:

I have the echo hub and have successfully added the nanoleaf bulb as well to alexa.  I could also share it with a google nest and control the bulb from either device.  I have also originally added the nanoleaf to the google hub and shared it with the alexa devices.  In all the various combinations I have tried, the nanoleaf would loose connection eventually, sometime reconnecting, sometimes not.

The thing I forgot to elaborate on in my earlier post is that the bulb configuration process in the nanoleaf app says that it sees a Thread network but adding the bulb to the Thread network failed, but it still works with the Echo in the Alexa app. This sounds plausible because the Echo has both a Zibgee hub and a Thread border router. This seems to indicate that Alexa communicates directly with it's Zigbee hub, but that sharing the bulb would have less chances of working if accessing it means going through the border router.

Are you certain that sharing it from Alexa worked? Did you notice any errors or mentions of a Thread network when adding the bulb with the nanoleaf app?