Great stuff! Built one my own. Works really well! Would love to be able to have smaller increments for distance. Found that in the leapmmw_sensor.yml file but after changing it via home assistant it changes back to a value with 0.15 increment. Does someone know where to change it to 0.05 increment? Thanks!
[edit] let me double check because the DFRobot wiki is slightly confusing and the LeapmmW docs are somewhereā¦
Confirmed. You canāt.
ah that makes a lot of sense. Thanks for checking and letting me know!
Does anyone has a code sample for using 2 (sen0395) sensors on 1 ESP please? I need a wide detection field and want to utilize 2 sensors.
Any code snippet really appreciated!
After so long having these sensors around I finally got them installed yesterday, I need to tweak the parameters yet, but here goes a probably stupid question that I didnāt find the answer toā¦
Whatās the use_safe_mode
switch for?
Another weird thing that is happening to me is that I canāt see the different target lines in the web server.
I see in the logs thereās a switch named show_target_stats
but it says itās set to OFF and I canāt see that switch either in the HA or the web serverā¦
What am I doing wrong? I think I manage to see it yesterday but donāt recall changing anything
Hey guys,
So it seems like restore_state is depreciated.
But after changing it, I get this error and Im not sure what needs quotes?
Thanks
EDIT*** should be;
restore_mode: always_on
really? F or C?
@crlogic. Question for you or anyone here, I have recently got into the esp and mmwave board, I have tried to look for a solution on this thread and else where, but canāt seem to find the solution.
I am using DFRobot mmwave, connect to esp32.
I have the mmwave connected to GPIO16, 17, 21, and 22.
The MMWave Tx is going into GPIO22 and the RX is going into GPIO21.
Here is my .yaml
substitutions:
device_name: leapmmw
# This will vary based on your board
uart_tx_pin: GPIO21
# This will vary based on your board
uart_rx_pin: GPIO22
# This will vary based on your board
gpio_pin: GPIO16
# (Optional) Path to the leapmmw_sensor.h file relative to your esphome configuration directory.
header_file: leapmmw_sensor.h
My Log is only outputting the following:
Cross check that your TX ā RX and your RX ā TX
The TX is Definitely going into the GPIO22 slot and RX is going into GPIO21. I have the mmwave solder to the esp32 board.
Iāve also switched the yaml file to try the other way with the same result. Could this be a connection issue, or could I have a bad board?
I have the LED blinking on the mmWave.
Got to at least sense presence, but I have no control over the configurations form HA?
GPIO21 need to be connected on your mmwave on RX pin and GPIO22 as it at RX need to be connected to the mmwave on TX pin.
I have the mmWave soldered onto the esp32 board.
Given the last pin hole on mmWave is an tx and second to last is rx.
Wouldnāt the yaml be correct?
Io2 is going into GPIO16
IO1 is going into GPIO17
RX is going to GPIO21
TX is going to GPIO22
See documentation about IO1 & IO2 on wiki of dfrobot website.
You donāt need to connect both and Iām wondering where is going GPIO17 in your config.
Based on the yaml, it seems good for RX/TX.
What kind of esp32 board you have used ? Check your ESP32 pinout. That may help and highlight some incompatibilities.
I donāt use the GPIO17 pin in the config, it was just soldered onto the board, because the pins were in that location. I am using
HiLetgo ESP32 Mini ESP-WROOM-32 Development Board.
And have the DFRobot mmwave soldered to VCC, GND, 16, 17, 21, 22.
I get presence detection, but changing any of the configs on the board through the dashboard, yields no changes, and it looks like I only get one way debug logs as well >>>.
I donāt see how the board can be direclty soldered by following your pin choice and the pinout here
In that case, itās correct. I would check connection soldering and may be trying to add a USB TTL to capture serial data and find the bad player.
Honestly, completely new to all of this, this is what the ttl output. Is there any indication here, with what could be going wrong?