Break beam sensor using VL53L0X for Home Assistant using ESPHome

distance-sensor-0.yaml

##
## A standard "break beam sensor" uses a laser or LED with a device on both
## sides of an opening and is triggered when something breaks the beam
## (such as a customer walking through the beam). Some garage doors use them.
## Stores often use them at the entrace to ring a chime when a customer enters
## or leaves.
##
## This is my attempt at using a VL53L0X i2c Time of Flight sensor 
## as a break beam sensor in Home Assistant using ESPHome.
##
## The binary sensor 'breakbeam_sensor' is
## * A synthetic break beam that is controlled by changes 
##   to 'breakbeam_sensor_dist'.
## * Should only send changes when the 'beam is broken':
##   * 'breakbeam_sensor_dist' becomes < 'minTripDistance' (or)
##   *  'breakbeam_sensor_dist' becomes to greater than 'minTripDistance'
##
## The sensor 'breakbeam_sensor_dist' is the actual VL53L0X sensor. 
## * The maximum reliable "open" distance seems to be to about 1.5 meters.
## * This sensor is marked intnernal as to not send distance data to HA.
## * When distance first falls less that 'minTripDistance', 
##   'breakbeam_sensor' will turned on.
## * When the distance is first greater than 'minTripDistance', the
##   'breakbeam_sensor' will be turned off.
## * This will poll at 0.1s. This seems fast enough, but 1s was not.
## 

esphome:
  name: distance-sensor-0

esp8266:
  board: esp01_1m

# Logging (DEBUG is the standard level)
logger:
  level: INFO

# Enable Home Assistant API
api:

ota:
  password: "XXXXX"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  fast_connect: true

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Distance-Sensor-0"
    password: "XXXXX"

captive_portal:

# the vl53l0x is i2c
i2c:
  scan: true

##
## The virutal break beam sensor.
## The state of this will be controlled 
## by breakbeam_sensor_dist's lambda as necessary.
##
binary_sensor:
  - name: "Breakbeam Sensor"
    id: breakbeam_sensor
    platform: template
    device_class: motion

##
## The actual sensor. 
## This sensor's lambda will control the state of our 
## virtual break beam sensor, breakbeam_sensor.
##
sensor:
  - name: "Breakbeam Sensor Dist"
    id: breakbeam_sensor_dist
    platform: vl53l0x
    address: 0x29
    update_interval: 0.1s
    long_range: true
    internal: true
    #
    # Only send a value back if breakbeam_sensor changes.
    #
    filters:
      - lambda: !lambda |-
          /**
           * YOU MIGHT WANT TO CONFIGURE THIS.
           * Distance below which to trip the virtual break beam sensor.
           * '0.5' meters is about 20  inches.
           */
          static double minTripDistance = 0.5;

          if (x <= minTripDistance) {
            if (id(breakbeam_sensor).state == true) {
              // Beam was already broken
              return {};
            }
            // Beam was just broken
            id(breakbeam_sensor).publish_state(true);
            ESP_LOGI("breakbeam_sensor_dist", "Set breakbeam_sensor to Detected");
            return {};
          }
          else {
            if (id(breakbeam_sensor).state == false) {
              // Beam was already un-broken
              return {};
            }
            // Beam was just un-broken
            id(breakbeam_sensor).publish_state(false);
            ESP_LOGI("breakbeam_sensor_dist", "Set breakbeam_sensor to Cleared");
            return {};
          }

@wizardnl additionally you mention address: 0x41 and address: 0x42 for your breakbeams where mine is address: 0x29 (which is the default for vl53l0x). If you changed the addresses, I'm not sure why you'd need the enable_pin.

Did you change the address on both of your vl53l0x? These seem like odd addresses.

Sorry that my previous message wasn't clear. After posting, I did some more testing and, stupidly, I didn't add the filter correctly per sensor as in your example. I got it working later in the afternoon.

To answer your question, if you want to use more than one sensor, you need to change the default 0x29 address and assign an address per sensor. Also, you need to connect the enable pin (Xshunt) per sensor (https://esphome.io/components/sensor/vl53l0x.html).

I now have your code working with 3 sensors on one wemos D1. This is amazing and just what I needed. I want to automate the LED lights for my stairs, and I needed a good way to detect someone who will step on the stairs at the bottom, top, and in the middle part where I have a small platform. With your solution, I can now detect if and where the person is, and based on that, I can automate the LED lights per stair step, so the lights "walk" with you. when you go up and when you go down.

@wizardnl AWESOME! I'm glad you got it all running! Thanks for the heads up about changing address - very useful! I don't think the ESPHome driver did that when I first implemented this (or I missed it). I would have loved to have used just one.

Hello

Thank you so much for your work! It makes a great DIY sensor for my smart home. I have built 2 of them so far and plan on doing more. One of them is working flawlessly but the other one has a small issue. I use the exact code you have published on a Wemos D1 Mini. It works most of the time with no issues. The only issue comes up when there is to much light in the room. The sensor is pointing to the window. Even though it is very low and does not see the window directly, it affects its reliability. I tired to make the reading interval 0.2 seconds and it did the same. I did make it 0.05 seconds to see how long it detects false readings. The result is for just 1 reading. So, I have the idea to keep it 0.05 seconds but create a filter to only make the virtual sensor "detected" if the reading is consistent for 0.2 seconds. This way I can prevent false "detected". The problem is I do not know how to do that. Is there any chance you are able to do this? I looked for it on the internet but I have too little knowledge to understand the things on there. Yes, I could do it in the automation in HA, but it would still have a lot of traffic in my wifi. I rather solve it in the ESP controller.

Thank you so much again!

@kerimtrn
It sounds like you want to remember the last 3 readings and only trigger if the current and the previous 3 entries are correct.
I'd keep an array of readings, and keep track where you are writing in the array so you write to the array over and over. Do some reading about creating a circular buffer using an array.

Alternatively, you could look at what I did with data-smoothing.h in https://github.com/kdorff/esphome/blob/main/cat-water-sensor/cat-water-sensor.yaml. My code in data-smoothing.h assumes the data is an int and would need to be changed to double, I imagine.

Hello

Thank you for your quick answer. I actually think about simpler solution if it is possible to do. Just like a button filtering, can I use a filter to activate the virtual sensor after 0.2 seconds of activity? I use delay_on on my buttons to prevent fluctuations but it did not work for this one when I tried. Maybe I did something wrong or maybe it is not possible for this kind of entity.

The lamda, itself, is a filter. Look at other filtering you can do on sensor https://esphome.io/components/sensor/index.html
Perhaps sliding_window_moving_average could be helpful? or median or quantile? I'm not entirely sure how they would interact with the lambda but the docs may say or just experimentation.

@wizardnl AWESOME! I'm glad you got it all running! Thanks for the heads up about changing address - very useful! I don't think the ESPHome driver did that when I first implemented this (or I missed it). I would have loved to have used just one.

Had to try it to see if it would work with 14 sensors. ;-) In theory, I can now control every step on my stairs individually. I still need to do some intensive testing, but for now, it works. Thanks again for sharing your code.

@wizardnl Looks like you picked up the ball and ran with it. Sure would be appreciated if you shared the code you came up with in a new gist.