Hub is C8 Pro with 2.2.2.151 firmware.
Attempt to pair MS605 Matter/Thread Merros Sensor fails with next error:
The device was comissioned with Home Assistant and has no problem communicatiog with HA. It is stable with HA for a few weeks. I decided to connect it directly to HE but this unfortunately did not work. Yes, I used a matter secondary pairing code generated by HA.
While I suspect this is a typo (2.3.7 was the first with Matter), you will need 2.4.4 or later for some battery devices. I believe this was one.
Ops, yes this was a typo.
The pltform is 2.4.4.151 (current latest platform).
Couple versions behind (but I do not remenber which version it was) I was able to add to the HE exactly the same device without problems. However there was not a good driver at that time. So the device was removed from the HE. Current attempt with latest platform fails to add it.
I have a thread in the beta section (created Jan 28) highlighting this issue...
Bryan was supposed to have received the MS605 sensor in February... but I still have not received any further update on this issue 
Is this just a MS605 problem or common matter related?
As I mentioned above, there was not a problem to add a MS605 to the HE. The problem was an unstable driver (I was using the custom Advanced Matter Bridge). Right now simply I cannot add the MS605. I don't have any other Matter devices to try and see if they could be paired with HE.
The day before yesterday on platform 2.4.4.153 (in Beta) I added an Aqara Door Sensor Matter over Thread and an Onvis Matter over Thread plug to HE that was also commissioned by Home Assistant. I had no issues doing so.
Since the change logs from 2.4.4.151 show no changes to the Matter application it appears that either it is an issue specific to your environment or the device.
As I mentioned, the device and invironment did not change. Everything is the same. The only diffrence is - a different platform version. (Sorry, I am not planning to roll back pltforms to see which one was working in a past).
I’m not saying for you to roll back. I am simply saying that I connected matter over thread devices to a specific platform with no issue. This platform is a slightly newer version than the one you are using with no changes noted in the change log.
This says to me that there is no issue with the general matter implementation (for device adoption) unless something was broken inadvertently and then fixed inadvertently without the HE staff knowing it.
Wery well could be a case ...
Unlikely, but it’s possible.
This seems to be a combination of MS605 and new Matter stack not working well together.
As you have experienced yourself, you can add the MS605 to HE with older firmware versions without any issues i.e. any version up to 2.4.3.177 ....
And, you will get the pairing failed error from 2.4.4.xxx onwards.
(Not sure what you mean by unstable driver - your first comment about a suitable driver not being available is correct ... the Custom Advanced Matter Bridge driver was updated later to cater for the MS605 and has been working flawlessly since then!)
Note: currently, I am unable to add MS605 to C8/C8 Pro and Aqara M3 with latest firmware updates. There is no issue with adding MS605 to SmartThings Hub 2, Zemismart M1, and Home Assistant.
Just successfully added MS605 to C8 with v2.4.3.177 as a test:
So it is an issue with this particular device and the matter stack. As I stated I joined devices two days ago with no issue so I knew it didn’t sound like it was the matter implementation in general.
This Matter protocol still have a very long way to go untill it will become resonably usefull.
As of today I can use HA+HADB to bring MS605 to the HE.
I also use Home Assistant and HADB for several devices. The matter protocol in Hubitat still may not be perfect but it has came a long way over the last few months with the recent updates. I have several matter over WiFi devices connected directly to He with no issue. I just started messing around with thread and the two devices I have are ok for now.
Download the Hubitat app
