Waterlezer: update to pulse_meter and add device_class

[dewi-ny-je]

Hi, I think it's worth to update the waterlezer with the improved platform "pulse_meter", see https://esphome.io/components/sensor/pulse_meter.html

Something like (please check!)

  - platform: pulse_meter
    pin: 
      number: 5
      mode:
        input: true
        pullup: true #v3.5 aanzetten
    id: watermeter_pulse
    name: "Watermeter flow"
    state_class: measurement
    device_class: "volume_flow_rate"
    update_interval: 5s # generates one reading per 5s, no need to spam HA, to be passed to filters (if I got it it right)
    internal_filter: 500ms # at max flow, one pulse every 800ms anyway
    timeout: 1min
    accuracy_decimals: 0
    unit_of_measurement: 'L/min'
    filters:
        - delta: 0 # pass through the value only if something changed, delta ">" 0
        - heartbeat: 300s # at least ping a value every 5 min
    total:
        name: "Watermeter total"
        state_class: "total_increasing"
        device_class: "water"
        icon: mdi:water
        update_interval: 5s
        unit_of_measurement: L
        accuracy_decimals: 0
        filters:
            - delta: 0.1 # avoid sending identical readings. One pulse = 1, so pass anything ">=" 0.1
            - multiply: 0.001
            - heartbeat: 300s

api:
  services:
    - service: set_total
      variables:
        new_total: int
      then:
        - pulse_meter.set_total_pulses:
            id: sensor_pulse_meter
            value: !lambda 'return new_total * 1000;' # untested, still waiting for your device to arrive

and no globals needed to be updated via lambda (or maybe needed for restoring from flash?)

[mhendriks]

thanks for the hints. I tried it before but there was a problem with the total counter when using the pulse_meter. I will try it again with the config above.

[dewi-ny-je]

It's untested. As soon as I get mine I'll test it.

[mhendriks]

I am curious , any test results?

[dewi-ny-je]

I installed it but I'm using almost only the total counter, so given the number of projects I have in the queue the priority for improving the realtime flow indicator is low and I haven't touched it. In fact, I still have to hot-glue the white holder to ensure reliable readings, which comes first.