Very nice 
works just like you said ! Thanks
1 Like
Is the illuminance reported correctly in HE?
Yes, the illuminance reading is the same value as reported in other apps (maybe one unit lower?).
There also seems to be an LV value, not sure what this is, but this value is not reported correctly in other apps and is also reported as illuminance?
1 Like
Mine arrived on Sep 4, but I didn't have time to mess with it until yesterday. It took a bit of fiddling to get it commissioned (through Alexa), and talking to the HE, but it appears to be working as a motion detector (it has satisfactorily replaced my previous Bosch motion detector), but I haven't really tested the presence sensing functionality yet.
All the “presence’ mmWave sensors are represented as motion sensors in Hubitat.
You can install the Meross mobile app to fine-tune the numerous configurable parameters for this device (maximum detection range, sensitivity, ‘space learning’ calibration, etc…).
My impression is that this mmWave sensor has a better performance than the popular Linptech devices (better detection of micro-movements).
3 Likes
Thanks for the info on this...
Didn't see any size specs on the Meross site. It looks like this one is going to be harder to hide due to its size. Can someone post measurements of the sensor? L-W-H?
Today I finally got 2 of MS600 from long time pre-order.
Sensor successfully added to the Meross App but I don't see a Matter Pairing Code in the app. Off course, code from a label does not work.
So, how do I pair MS600 to the HE?
Do I have to use, say Alexa instead of the Meross App?
Also, do I have to reserve an IP via DHCP Reserve or it will work reliably without IP reservation?
Believe so...Alexa, Google Home, Apple HomePod, etc. After commissioning w/one of those, get the pairing code from them to add to your HE hub.
1 Like
I have a problem with the new MS600 sensor (got 2 but playing with just one). First time I paired it with Meross application. Everything went OK but after less than 2 hours sensor stopped reporting Mothion, Light l3vel still was reporting. I factory reset the sensor and first commissioned it with Alexa and then paired with HE using Advanced Matter Bridge as device driver. Initially everything looked and worked very well but again within less than 2 hours sensor stopped reporting motion and still reporting light level.
What I am doing wrong?
I think this has nothing do with HE integration because the same thing happened with just a Meross app itself.
1 Like
Have you calibrated the sensor using the Meross app 'Space Learning' ?
Does the device stuck on motion/presence detected or 'not detected' ?
Yes, firsts time I was using Meross app ony and performed all installation steps. Sensor worked for about 2 hours and then stopped reporting motion (stuck in not detected state) but still reported light level.
Second time (after factory reset) I used Alexa for commission and then paired with HE using your Advanced Matter Bridge as a driver. Two child devices was created (motion and lux). Calibration was done by double clicking a button. Again everything was OK for couple hours and then motion reporting stopped stuck in inactive but lux reporting was OK.
These MS600 sensors looked very nice on the spec/description but in reality they are garbage (at least these two what I got recently).
After being added to ether Meross App and/or HE, Motion Detection works fine for couple of hours (approximately 2 hours) than permanently stops stuck in ether active or inactive state. Illuminance reporting is still works fine. This means the connection is active and stable. Recycling Power is not "fixing" broken Motion Detection but Lux reporting is never a problem.
Furthermore, few times I tried to factory reset both sensors and reinstall them again. This worked couple times with the same failure pattern, i.e. Lux reporting is OK but Motion Detection stops after few hours. And finally Motion Detection does not work at all even after factory reset.
Bottom line:
At least two sensors what I got are 100% garbage.
1 Like
I have one in continuous use in my walk-in closet that is working well.
- endpointId: 01
- aqaraModel:
- hardwareVersion: 9.0
- inClusters: 0003,0004,0005,001D,0040,0041,0400,0406
- manufacturer: Meross
- model: Smart Presence Sensor
- outClusters:
- serialNumber: 662001240700857
- softwareVersion: 9.3.4
- uniqueId: 14800DF5F492DE37
1 Like
Mine is working very reliably and has never stopped sending the motion/presence updates in the past two weeks... I don't know what could be the reason for the problems you encounter, it is unlikely to receive two faulty units at the same time... but everything is possible.
If you remove all third-party Matter integrations and use the sensors solely with the Meross app, does the same problem persist?
These two sensors definitely from the same batch. MAC Address difference is 53
I removed both sensors from everything and factory reset them. Than added one to only Meross app. At the very beginning everything looked very sort of good. However "Space Learning" always ends up with "Timeout". I am confused what I am seeing under "Detection Range Calibration". Button "Complete Installation" sometime active (but most likely does nothing when pressed) and sometime gray. After few hours LED stopped to turn on Green (occasionally it still blinks briefly). For the past 18 hours sensor is still reporting motion activity which seems to be correct. I am not sure if if functional as it should or not. At least LED behavior is abnormal.
BTW. Is it any way to retrieve Matter Code from the Meross app for the pairing with HE?
I did not find a way to get it from Meross app. It means I have to factory reset the sensor again, add it to Alexa (just for generation this Matter code. I have an Alexa but I am not using it at all), get the Matter Code and pair with HE. Somehow after pairing with Alexa Meross app can see the sensor and pair it with the app sort of automatically.
After having it installed for a couple of months, I am very happy with its operation. It took some tweaking in HE, but it is performing the way I think any motion sensor should. Specifically, I have it angled slightly towards the doorway and it detects me walking towards the room and the lights are already on by the time I step inside. While I'm in the room, sometimes fairly motionless (sitting and reading), it knows better than to shut off the lights. Then when I leave, the lights stay on for 60 seconds and shut off automatically.
I've never had a motion sensor that performed this well. I will have to consider installing these in a couple more rooms...
1 Like
UPDATE.
Finally I am very happy with MS600 Sensors. These are a replacement for the Linptech sensors which are locking within 4-6 weeks and required to recycle power in order to get them back online. At first I had a problem with MS600 but all what is needed - just let them adjust themselves to the environment. This takes approximately a day and they becomes very stable.
3 Likes
Glad they are working out. If not for the form-factor (zero WAF) I'd be thinking about doing the same.
Have you tested them w/ceiling fans?
Yes, tested. Unfortunately they are picking up spinning ceiling fans. It looks like this is a common problem for all mmW sensors. Aqara FP2 has an ability to filter out this type of interference. I have 2 FP2 but I still cannot use them because very often they creating a ghosts.
1 Like
