I think I figured it out. I changed the install method back to method 1 cuz i figured that I edited the local file and should have it included in the config
Thanks so much for your expertise. Faulty wiring jeez!
I have a question though about the install methods. If I choose the remote packages option does that mean my config files stay most up to date with your changes? I assume with a local file usage i will have to periodically download from the repo?
Great thread going on here. I got a few dfrobots going fairly easily and am now just brainstorming ways to block out interference.
Most rooms have ceiling fans which is an issue if the device is not placed just right. I would think a visor of some kind in an enclosure could block off the upper half of the FOV to resolve that, has anyone played around with that? Are there materials to stay away from?
Rotate and tilt down? Tilting does work at distance.
If the fan is >2M from the sensor this may work as the advertised * Angle: 100°Ă40°@6dB. I do know that this angle does not hold true for motion very close to the sensor.
Likewise perhaps the HS2643A part is a better fit advertising *Angle: 60°Ă40°@6dB. Mine hasnât arrive yet to determine actual detection ranges/angles.
I have always stuck with âplacement firstâ as the primary tuning step. Also the most inconvenient!
Lastly metal does interfere. Stick a baking tray on top someone used tinfoil on the FP1, havenât tested it myself
This is an awesome project and really well put together. I have a question though, everything seems to be working properly but the mmwave_presence_detection never changes from clear, even though he num_targets fluctuates as expected. Should mmwave_presence_detection change once num_targets is greater than 0? Or is mmwave_presence_detection entirely separate?
Also am I missing where Distance, Latency, Sensitivity and Safe Mode are explained?
MMWave not showing in HA?
I am just starting with the DFRobot mmwave and your thread is really helpful. I have created a basic setup using ESPHome in HA. The logs seem to run OK and I can see presence is detected but I have a couple of issues. The main one is that the device simply does not show in HA devices/integrations. My ESPHome devices are normally discovered automatically. Am I missing something? Also the logs show a âlatencyâ state of 0.00000 and I get a warning (yellow text) of Socket Operation Fails (See screenshot)
Disconnect the sensor. Confirm same issues. Post a support thread in the ESPHome category as these are not related to the sensor. mDNS / router issues I suspect.
This is curious considering the other values are picked up. Did you try changing the value? Give it 3-4 seconds between further changes. The sensor needs considerable time between configuration commands.
I have built a combo of a D1-mini and a SEN0395 and loaded a simple ESPHome code on it.
And a red LED is blinking once per second. First I thought it was ESPHome signalling a warning condition as it is documented. I tried to change everything in the ESPHome yaml. Then suddenly it struk me that the LED was red. But the LED on the D1-mini is blue. I had been chasing the wrong thing. ESPHome was happy and working as it should. It is the little SEN0395 that seems to be flashing when it is communicating.
Solution: Soldering iron! LED gone, problem solved! I thought I would share that experience with anyone going through similar project.
New problems created. Now you have no visual indicator when the sensor is in config mode or not. Because the LED behaves differently in config mode and we get enough posts here about âit doesnât workâ that the LED is valuable.
AliExpress seller linked in OP came in clutch and the final variant sensor of the LeapMMW series has been delivered.
Initial testing in place of the âDFRobotâ version (100x40°) shows that the HS2643A (60Ă40°) performs better at range for a narrow hallway. Perfect. I suspect the âwiderâ view of the OG sensor creates reflections/occlusions down the hall that limits its range.