I just got the new Meross Presence Sensor MS605 in the mail today. I paired it with the Meross app and I got it all setup within. Then I paired it with Hubitat, it paired over Matter but it didn't auto select a driver. So I choose the Generic Matter Motion Sensor. Motion is showing in the Meross app but Hubitat isn't seeing anything.
This is the pairing log from Hubitat...
Hoping the driver just needs to be updated for this device.
@bcopeland @mike.maxwell @Hubitat_Staff
Thanks
How?
MS605 is a Matter over Thread. You need a TBR (Thread Border Router). HE supports only Matter over Wi-Fi.
Used the Hubitat app, add device, matter... etc. As you can see from my log, it found it and added it.
Without a TBR it will not work. For MS605 you absolutely must have a TBR, connect it first to Thread Network and than share it to the HE over Matter.
If it paired to Hubitat, there is a TBR on the network; otherwise, it would never get that far. The issue here is one with the driver, namely, that motion/occupancy seems to be reported on three endpoints (from the fingerprint, I can't tell which means what, but the product descriptions mentions combination mmWave and PIR, so I'm guessing that's two of them), and the driver is probably looking at the wrong one.
Ok, TBR is there. I just added 2 of this toys but to HA. I am planning to use HADB for bringing these devices to HE. However MS600 (Matter over WiFi) paired directly to the HE and driver is Advanced Matter Bridge designed by @kkossev My good guess the same driver should be good for the MS605.
PS. MS605 is a PIR/mmWave combo. Any of these could be configured as Primary Sensor. The device reports Lux and up to 3 MS.
3 posts were split to a new topic: Confusion about TBRs with Hubitat
Did you ever get your ms605 to work? I am stuck as well. I got the ms600 to work, but when I added the ms605, switch the device type to “Generic Matter Motion Sensor”, it still does not register any movements.
Yes, but I'm not sure if it's available yet. I'm in the beta group and don't remember if the updated driver is live or not. But it does work well.
I see. So there was an updated driver you installed to make it work properly though. I’ll be on lookout for that. FWIW, I do have the Advanced Matter Bridge installed from previous MS600 installation.
There won't be an updated driver to "install"; the updated driver will be part of platform 2.4.4, currently beta.
That being said, I see you're using a user Matter Bridge driver. It's quite likely this device will work with that now if you haven't already tried.
Yeah it’s not working. No indicated activities even though the other platforms picks up movement.
Presumably because you are still on 2.4.3 and using the built-in driver?
I’ve since reinstalled the Advance Bridge Matter which I was hoping would help, but still cannot get the motion detector to work. Just so I’m validating correctly, when motion detected, the icon should change red and there should be something in the activity log correct?
And how do I make sure I’m using the most updated driver on the matter device?
Hi @GHN1013 ,
If you’re willing to troubleshoot the custom driver, I will try helping.
The alternative is to wait for the new HE platform 2.4.4 to be released, where this new device is supported using the stock inbuilt drivers.
Hi @kkossev I’m open to both. How long until the new HE platform comes?
Otherwise, I’m open to troubleshooting the custom driver.
Did you just install the driver, or did you switch this device to use it? (Sorry if that is an obvious question, but it's worth asking.)
(In this case, you'll probably want "Discover All" instead of "Configure," but the documentation for this custom driver should say more.)
It's currently in beta, but there is no timeline for public release -- i.e., the norm. 
Had it before but just reinstalled the custom driver in attempt to get it working.
And thanks for the guide on changing drivers using “Device Type”. That’s what I did: changed it to “Generic Matter Motion Sensor.” Then clicked “configure” and “initialize.” Is that not correct?
If you are trying to use the community 'Matter Advanced Bridge' suite, then the correct 'device type' is 'Matter Advanced Bridge'. After changing it, refresh the MS605 web page in HE, you should see a button 'DIscover All'. This will start the Matter device endpoints discovery procedure, and the driver will then create child devices, depending on what this Matter device exposes. The MAB suite should automatically assign the correct drivers for each child device. I suppose you will see 3 motion sensors and probably an illuminance sensor.
Gotcha. Sorry I used incorrect driver. Changed it to MAB and was able to run Discover All to see the three motion sensors and light sensor. Now do I just verify it detects motion on log?
Download the Hubitat app
