Probably not, but since it costed me a pretty penny I’m experiencing a strong case of sunk cost fallacy.
I’ll see how big of a window do I have to return it and I’ll try my luck untill then, if I won’t make it work by then, then it’s getting returned.
Hello. We apologize for any inconvenience caused. Before using this kit, it is important to confirm a few key points:
- Could you please let us know what scenario you are setting up? Have you installed the mmWave correctly?
For more details, please refer to the datasheet.
- If you have already confirmed the correct installation method, please ensure that the measurement environment is a single-person indoor space. Please check whether the Active reporting of presence information is constantly reporting the data below regardless of the presence of a person:
Report: 0x53 0x59 0x80 0x01 0x00 0x01 0x01 sum 0x54 0x43
If it is, please try adjusting the sensitivity.
https://files.seeedstudio.com/wiki/mmWave-radar/MR24HPC1_User_Manual-V1.5.pdf
Hope this will be helpful!
@frank @Carsten76 We really apologize for any inconvenience caused. Perhaps you could check the parameter called “Motion Trigger Boundary inquiry.”
I made modifications to the Motion Trigger Boundary inquiry parameter, adjusting it from 2m to 5m. I used the upper computer software to monitor the motion parameters, (Motion Energy waveform). The testing was conducted in a spacious indoor environment. Before the modification, the waveform was close to 0 beyond a distance of 2m. After the modification, the waveform also approached zero beyond a distance of 5m.
If possible, we suggest conducting tests in a spacious indoor environment with only one person. If the issue still persists, please feel free to contact [email protected] for further assistance.
Thank you for the response, but unfortunately, no amount of adjusting the parameters changes the behavior I’ve described.
The Body Movement Parameter is simply unusable in its current state.
The problem is not with other measurements the sensor is performing, but just with the Body Motion Parameter, which you claim uses a special algorithm, my guess is that this algorithm needs some serious adjustments.
I admit that my use case is not the ideal scenario for the sensor, my room is rather short (2m at the tallest point) and more elongated than square, but still, stuff like that should not happen with a product marketed as relatively “plug and play”.
I’d like to return the kit, but troubleshooting it took me so long that the 5 day return window since receiving it has passed, is there a way for me to return it anyway? I don’t want to just throw it away, that would be a waste.
I’ve had the same issues. I’ve been testing this kit three days now and the only thing that’s consistent is how unreliable “Presence Information” is. Regardless of settings and what it measures, it gets stuck on either “Detected” or “Clear,” and the only thing that makes it change is a system reset. I’ll just try a different sensor, this one doesn’t work.
I can confirm that I have the exact same problem. The Body Movement Parameter jumps up and down from ‘0’ to ‘80’ or higher every second or so.
I am not using a custom setting and have used the ‘bedroom’ preset.
Very sorry for the inconvenience!
If you want to perfactly realize the functions of the kit, you need to use the mmWave kit according to the above installation method and usage environment. If the data fluctuates a lot, it is recommended that you can remove the radar, connect it to your computer with a usb to serial port, and adjust its sensitivity or other parameters according to the datasheet to adjust your radar so that it can be suitable for your own usage scenario.
I have exactly the same problem here, Body Movement Parameters jumping up and down randomly. Maybe a hint to the seeed engineers - when removing the cover the kit works perfectly. Maybe some kind of parasitic self oscillation …? interesting that this issue wasnt posted before january 2024
We’re very sorry guys, we’ve noticed that people are giving us feedback on this issue, and the R&D department is already collecting materials to check the cause of the problem. Please give us a few days and when I have new information, I will sync it to you as soon as possible.
1 Like
tried PTFE-sheet instead - this showed nearly no noticeable impact.
Hi, last week i also received the Human Detection Kit. I want to use it with Home Assistant. First it showed all the sensors with unknown data. After re-flashing with esphome every sensor is showing data but now i have exactly the same issues with the body movement parameter. The firmware is up to date. Is there a fix possible or do i need to send it back?
Hello, thank you very much for all your patience!
Regarding this issue, we have made adjustments to the millimeter wave layout and placed it in the center position to minimize the possibility of interference from the casing. Currently, we have open-sourced the PCB board for everyone to use.
https://files.seeedstudio.com/wiki/mmwave_kit/Human_Detection_Sensor_Board_V2.zip
Hi, thank you very much for the update, will there be an option to order the revised PCB from you or do we need to figure out how to manufacture it ourselves?
Hello. The currently available mmWave Kits have all been updated with the new version of the PCB board. If you have soldering skills, you can try to solder the xiao and mmWave to the new board yourself. If you don’t have soldering skills, you can choose to purchase our pre-updated new version mmWave Kit directly.
Here is my email: [email protected]. Feel free to contact me if you have any other requirements.
So if we bought a previous kit, and don’t have soldering skills, we just have a unit that doesn’t work? Can we return it?
I’m just frustrated because I have a product that was advertised to work, but doesn’t.
Hello, what specific problem have you encountered? Perhaps you can contact my email and provide a detailed description of your issue. I will assess whether I can help you resolve it.
Thanks. I’ll send you an email this afternoon when I get home from work and can give details on the issue. At its most basic, it just always reports presence, even when no one is in the room.
I found a solution working very well for me. hoping that others try it too and report success or not. Unfortunately I published to the wrong thread here so pls follow the link
summary: the front panel seems to be at the wrong distance from the antenna plane. Actually 11mm instead of 6mm. Replacing the front cover by a PVC sheet of 1mm thickness 6 mm above the antenna provided perfect results. (6mm is half wavelength at this frequency)
here the result (the garbage to the left is with the original cover in place)
1 Like
with the new pcb-design do you still have 11mm gap between microwave antenna plane and the front cover? My experiments showed that the gap has to be half wavelength at 24GHz which is abt. 6 mm. maybe there exist pin header extenders with this narrow pitch, at least this would be an easy and cheap way to raise the radar pcb 5mm up also for the older pcb design. But first lets see if my results are confirmed.
Sorry, we haven’t changed our casing. Through our testing, we found that placing the mmwave in a more central position effectively avoids interference caused by the casing.
Your method is also quite good, as it provides a second solution for more friends. Thank you very much for sharing!