Here is the information on how to add the option for Decommissioning the Nano Matter device so that it will be ready to pair with a new commissioning controller.
2 Likes
I'll do it again when I get home and be better about catching the logs.
Yes, and those instructions work as advertised. I did that when I moved it from being paired to Google's thread network to Amazon's.
1 Like
I can add my sensor (originally paired with Apple Home and no shared) to Home Assistant and to Google but I cant get it into HE. Always gets stuck at
Pairing Matter device, current stage: SendAttestationRequest
Can you explain what is communicating via what transport here. This is a thread only device.
How is HE communicating - via IP and a router or Thread? What has to be in range of what and is BlueTooth in play? The Apple Home App is just sitting at the dialog with the new pairing code. Is it down to HE only and the device at this point ?
Anything I can help diagnose?
1 Like
That's exactly where mine gets stuck.
I don't remember looking at the logs to see if it logged anything more than that though.
I think it only logs in the UI 'add matter device' dialogs.
This is no big issue to me as I could if I needed take the HA device value into HE in other ways but it would be nice for it to work as intended. Lowering the Matter frustration issues.
Is 'Share' or 'pairing mode' on the horizon from HE to other Matter controllers.
Stupid thought Zigbee doesnt need to be enabled does it ?
When you share a Matter over Thread device from Apple Home, Google Home, or Amazon Alexa, the Hubitat hub tries to communicate with Apple/Google/Amazon Matter Controller and the thread device using Matter over Ethernet to talk to the Thread Border Router (found within your Apple, Google, or Amazon physical hardware device.) All Matter communications uses a private IPv6 network. You do not need to enable IPv6 on your home network for this to work.
Some details about Device Attestation -
Basically checking the DAC certificate of the Nano, as I understand it - Is it possible it's so new that something is not registered yet in the cert chain-of-trust, or Hubitat is missing some new root cert - But given that it registers just fine, with initial commissioning, I'm sort of confused why it can't be shared with HE.
For your reading pleasure: Matter Device Attestation — Matter 2.3.0-1.3-alpha.1 documentation
Per the process flow below, Device Attestation is Step #3 in the process of:
https://siliconlabs.github.io/matter/2.3.0-1.3-alpha.1/general/SECURITY.html#commissioning-steps
1 Like
Nothing in the system logs on any attempt.
1st attempt, sharing from Amazon:
2nd attempt, sharing from Amazon, just sat on this info (waited 5 minutes)... Never errored out:
But I will say all of my thread based Matter devices tend to come/go, so it could be that I tried this during one of the periods it was not communicating... I'll try again later.
See, lots of holes in the communication/data:
Or here... Sensor dead for 9 hours then just starts reporting again. I see this on all of my thread based Matter devices (although not necessarily at the same times - so I don't think it is just that the border router stopped working) whether on Amazon or Google.
I would guess it is interference/channel selection based (lots of 2.4GHz traffic in my house). But since Thread is so super smart and user friendly, you can't change the frequency on it (or even see it on some manufacturer's thread networks).
Anyway. Enough ranting about my annoyances with thread/matter.
1 Like
I'll try messing around with my Nano Matter over the next 4 days or so, to see if I experience any similar issues. My daughter is getting married in a month, so the 'honey do' list has been larger than normal for me lately. I'll have a lot more free time afterwards. 
2 Likes
I'm going to move my Arduino closer to one of my 2 Amazon Echos tonight and see if the dropouts magically disappear (thus supporting my signal strength / interference hypothesis).
1 Like
I just switched my Arduino sketch to be the matter humidity sensor example. I have it commissioned/paired to my Apple Home, using one of my AppleTV's as the TBR. I then shared the humidity device with Home Assistant. I'll let it run for a few days to see if there are any drop-outs. I do have multiple AppleTV's and one HomePod Mini that can act as TBR's, so my Thread mesh might be somewhat robust??? Not sure. The Nano Matter microcontroller is not in the same room as any of the Apple TBR devices, though. So, we'll see how it behaves. HA will log the data to its historical DB as well as to InfluxDB, so I should have decent data to review.
1 Like
I just moved the device right next to one of my Amazon Echos (instead of down 1 floor from the closest one). We'll see!!!
1 Like
This morning, I received a pop-up on my AppleTV requesting be to upgrade to the recently released tvOS 17.5. I decided to perform that upgrade... ever since, my Nano Matter humidity sensor has gone offline. So, my hypothesis is pulling the TBR out from underneath the Nano Matter is what caused it. I have not restarted the Arduino Nano as I wanted to finish upgrading all of my Apple devices to v17.5 to see if it magically comes back to life.
Prior to that event, it was reporting data consistently.
Once everything is upgraded, I'll give it some time to see if it reconnects. If not, I'll restart the Nano Matter board.
1 Like
Okay, so after sorting out things with my AppleTV firmware upgrades, and finding a self-induced bug in the Matter Humidity sensor example sketch (I made a small mistake when adding in the decommissioning code), I have had a very stable system.
The one drop out in data, circled in red above, was when I upgraded the Home Assistant Matter Server this morning. I figured it would be a good test to see if things came back afterwards, without any manual intervention. It worked great.
So, I am not seeing any drop outs thus far. I will let it continue to run to see if anything odd occurs.
3 Likes
I see A LOT fewer dropouts on mine being right next to my Amazon Echo than I did with it in the other room... I still see a number of dropouts in there, though. But I also did some HA updates too, so like you said it could have been HA related not Matter/Echo related.
I'm going to move it further away again and see if it changes. I have a feeling the old ■■■ Matter stack (and maybe antenna design, not sure) in the Echo is hurting things.
2 Likes
Thank you both for all your effort to bring in DIY Matter to the HE.
I am carefully watching this thread and patiently waiting for the Green Light.
I have a few upcoming projects which could be accomplished with HubDuino
(Thank you, Dan!) but I am not in rush and Matter DIY seems to be more
appropriate. But I am not a SW person and will rather wait for all yours
accomplishments and a Green Light for trying DIY Matter.
1 Like
Another day and I must say I am pleased that this little Arduino Nano Matter board + AppleTV TBR + Home Assistant seems to all be very stable now.
Does anyone know if the Arduno Nano Matter acts as a Thread Repeater device? I have not really thought about what it takes to build a robust, reliable Thread mesh network. 
The only Thread devices I have are the Arduino Nano Matter + my AppleTV's and one HomePod Mini. I would hope the Apple devices are all part of the same Thread Mesh network and can even take over as the TBR should one of the devices go offline. At least, that is my understanding of how it is supposed to work.
I don't believe it can.. - See the Tech Specs - Arduino Nano Matter: Community Preview — Arduino Online Shop Under connectivity, neither WiFi or 802.11 isn't listed, and the device doesn't have an ethernet port. - So, I think it's just a thread endpoint device, as I understand it. And finally, this, specifically calls out that WiFi isn't supported - Without WiFi (or ethernet), it can't an be a TBR.. - The TBR details are here..
There is a class of "Thread Mesh Extender" devices - That might be more aligned with what your asking - See: Difference between Thread Border Router and Thread Mesh Extender
That all said - You CAN make a RPI into a TBR, so that's kind of close - See Below:
Quick Start - OpenThread Border Router - Silicon Labs & Matter Over Thread Example - latest - Silicon Labs Matter Silicon Labs
Finally, did the effort to do multi-admin with the Nano (provisioned by HomeKit, Alex, or Google), and then also connected to HE ever work? - It seems like things could get it provisioned in one of the eco-systems, but then it seemed to never be able to be added to HE after that? - Is that still an open issue?
Agreed, it cannot act as a Thread Border Router. That was not my question, though. 
I am wondering if it is a Thread mesh network repeater. Similar to how mains-powered Zigbee and Z-Wave devices repeat their respective mesh network signals for other devices on the mesh network.
