I was waiting since a long time ago for this type of tuto, i command all devices instantanetly ! Thank a lot ! it's a really really great chanel, good job !!
Would you please, please share your yaml file? I have been trying for days to use bme680 vs bmp280. I think the BME680 is a far better sensor and fits my need !
This was a very easy to follow Video. Thank you. You did not talk about the MmWave calibration or settings. Does your setup have one distance setting for move and static or do you use all 8 settings?
Hi, yes the LD2450 sensor doesn't expose options for calibration (Like the aqara fp2), all configuration is based on the zone detection feature. No min or max distance, you just create a zone starting at your desired min distance and ending at your desired max distance.
To be honest, I haven't tried ESP32 boards with ethernet support yet, so I can't recommend them. I undestand why you might not like wifi, in some situations they are just not as reliable as a wired connection. I will look into it, but I really think that ESP32 boards with poe support seem like a very flexible base for any sensor you might want to build using ESPHome.
Hi, thank you!!! you made me remember that I needed to order some parts to be able to work on a battery powered sensor. I got an 18650 battery months ago for this, but always forgot to order the parts I'm missing.
Look great, have installed it via your website with the install firmware esphome button. But i am unable to adopt the esphome and therefor not able to update the security updates for esphome. How to adopte the esp?
you'll need to buy the yaml file to be able to adopt it on the esphome dashboard, but don't worry, I'll update the firmware to the latest esphome version. I haven't seen any relevant improvements on the release notes so far regarthing the devices used on this particular sensor, that's why I haven't update it yet.
@@danieljansen1987 hey, I updated the binaries yesterday (right before they launched 2024.6 🤦) could you try using the installer from the post? (It would be weird, since is the same yaml but doesn't hurt to try). Also, which version are you using? with Bluetooth tracker or without.
If you are using a BME280 instead of the AHT20 BMP280 sensor (and you have the yaml) change the configuration like this: 1- Replace all bmp280 with bme280. 2- under sensor change plantform to bme280_ic and address 0x76: sensor: - platform: bme280_i2c id: bme280_sensor address: 0x76
Hi, mmmm the mmwave sensor should be looking in direction of the logo, the ESP32 it's supposed to go in the back. Maybe you can share a picture in the comments on my website so I can understand better
I have a problem with yaml it's probably come from the ledc who use pin02. Am i the onlyone with this type of problem ? Do you have a support or something where i can found some help ?
Hi, I'm going to create a discord channel for that. But as far as I know, you are the only one with a ledc related problem. It's there to expose the LED on the board, so you can safely remove it.
Fair enough. The goal of this project was to keep things as straightforward as possible to encourage more people to give it a try. I haven't experienced any interference myself, nor have I received any feedback suggesting it’s been an issue for others. However, I understand that interference can be a real problem and impact reading quality, which is why I tested the device for a few months before posting the video.
Thanks for this. I get this error when I try to remove the AHT10 sensor? Im using your membership yaml..... The error message you're encountering, "*** [.pioenvs/entrance/src/esphome/components/aht10/aht10.o] Source src/esphome/components/aht10/aht10.cpp' not found, needed by target .pioenvs/entrance/src/esphome/components/aht10/aht10.o'.", indicates a problem during the compilation process related to the AHT10 component. This might be happening for a few possible reasons:
Hi, Thank you so much for your support 🎉. Try using the Clean Build Files options on the ESPHome Dashboard (it's inside the three dot menu of the device), and try again. What is probably happening is that you added information for a new devices to an existing project. The esphome building process downloads and cache the drivers for the device using the yaml file the first time it runs. After that, to speed up the building process the driver download is skipped, as it assumes that it has all the drivers it needs from the first time it runned (on most cases, this is what you desire, when you are working on a devices with a specific set of sensors), so to get around this, using the Clean Build Files will reset the cache of the project and should trigger the download of the drivers the project needs. Let me know if that helps 🤞
Was watching your other video today and was wondering if this was possible. Thanks for making it so easy.
Glad I could help! 😁🙌
Sei una maledetto genio... Bravissimo ❤️❤️
Fantastic!. Excited to update your previous build with the new sensors to have The Ultimate smart sensor.
I was waiting since a long time ago for this type of tuto, i command all devices instantanetly ! Thank a lot ! it's a really really great chanel, good job !!
The vision of your previous video led me to make a design with a ESP32-C3 Super Mini, a BME680 and a BLE repeater Thank you very much.
Fantastic! I just got some ESP32-C3 last week, can't wait to start playing with them too 🙌
Would you please, please share your yaml file? I have been trying for days to use bme680 vs bmp280. I think the BME680 is a far better sensor and fits my need !
This was a very easy to follow Video. Thank you. You did not talk about the MmWave calibration or settings. Does your setup have one distance setting for move and static or do you use all 8 settings?
Hi, yes the LD2450 sensor doesn't expose options for calibration (Like the aqara fp2), all configuration is based on the zone detection feature. No min or max distance, you just create a zone starting at your desired min distance and ending at your desired max distance.
Nice Video 👌 thx
Thank you. I am not very fond of wifi..what add on would you recommend or esp32 board poe network cable enabled?
To be honest, I haven't tried ESP32 boards with ethernet support yet, so I can't recommend them. I undestand why you might not like wifi, in some situations they are just not as reliable as a wired connection. I will look into it, but I really think that ESP32 boards with poe support seem like a very flexible base for any sensor you might want to build using ESPHome.
Love your work, would love to see a build using a 18650 battery
Hi, thank you!!! you made me remember that I needed to order some parts to be able to work on a battery powered sensor. I got an 18650 battery months ago for this, but always forgot to order the parts I'm missing.
@@fixtse. would be interesting to see how long a 18650 would power the setup
Look great, have installed it via your website with the install firmware esphome button. But i am unable to adopt the esphome and therefor not able to update the security updates for esphome. How to adopte the esp?
you'll need to buy the yaml file to be able to adopt it on the esphome dashboard, but don't worry, I'll update the firmware to the latest esphome version. I haven't seen any relevant improvements on the release notes so far regarthing the devices used on this particular sensor, that's why I haven't update it yet.
I already bought the yaml, but the yaml Version keeps rebooting
@@danieljansen1987 hey, I updated the binaries yesterday (right before they launched 2024.6 🤦) could you try using the installer from the post? (It would be weird, since is the same yaml but doesn't hurt to try).
Also, which version are you using? with Bluetooth tracker or without.
has anyone reworked the case to have grooves to hold the addtional sensors?
If you are using a BME280 instead of the AHT20 BMP280 sensor (and you have the yaml) change the configuration like this:
1- Replace all bmp280 with bme280.
2- under sensor change plantform to bme280_ic and address 0x76:
sensor:
- platform: bme280_i2c
id: bme280_sensor
address: 0x76
Ive 3d printed the enclosure but I find it is not getting good detection because the sensor is behind the esp board. Have i built this wrong?
Hi, mmmm the mmwave sensor should be looking in direction of the logo, the ESP32 it's supposed to go in the back. Maybe you can share a picture in the comments on my website so I can understand better
I have a problem with yaml it's probably come from the ledc who use pin02. Am i the onlyone with this type of problem ? Do you have a support or something where i can found some help ?
Hi, I'm going to create a discord channel for that. But as far as I know, you are the only one with a ledc related problem. It's there to expose the LED on the board, so you can safely remove it.
way to long cables, to high risk for interference and not tidy at all
Fair enough. The goal of this project was to keep things as straightforward as possible to encourage more people to give it a try.
I haven't experienced any interference myself, nor have I received any feedback suggesting it’s been an issue for others. However, I understand that interference can be a real problem and impact reading quality, which is why I tested the device for a few months before posting the video.
Thanks for this. I get this error when I try to remove the AHT10 sensor? Im using your membership yaml..... The error message you're encountering, "*** [.pioenvs/entrance/src/esphome/components/aht10/aht10.o] Source src/esphome/components/aht10/aht10.cpp' not found, needed by target .pioenvs/entrance/src/esphome/components/aht10/aht10.o'.", indicates a problem during the compilation process related to the AHT10 component. This might be happening for a few possible reasons:
Hi, Thank you so much for your support 🎉.
Try using the Clean Build Files options on the ESPHome Dashboard (it's inside the three dot menu of the device), and try again.
What is probably happening is that you added information for a new devices to an existing project. The esphome building process downloads and cache the drivers for the device using the yaml file the first time it runs. After that, to speed up the building process the driver download is skipped, as it assumes that it has all the drivers it needs from the first time it runned (on most cases, this is what you desire, when you are working on a devices with a specific set of sensors), so to get around this, using the Clean Build Files will reset the cache of the project and should trigger the download of the drivers the project needs. Let me know if that helps 🤞