Note that there are issues with pulse_meter for almost 2 years now; pulse_meter seems to have broken with 2023.8.0 · Issue #4807 · esphome/issues · GitHub
The fix PR has been open for more than a year, so not sure when/if this will ever get fixed.
1 Like
The meter seems to work fine. But i still have issue with the value being 0 after reboot (and i still haven’t figured out why it reboots at not fixed interval)…
I’ve set reboot_timeout: 0s on both api and mqtt section of the config file and the framework i’m using is type: esp-idf.
I haven’t set the preferences.flash_write_interval in the config file so it should default to 1 min.
sensor:
- platform: pulse_meter
pin:
number: GPIO16
mode:
input: true
pullup: true
internal_filter_mode: PULSE
internal_filter: 500ms
#update_interval: 30s
filters:
- multiply: 10 # (10L/1 pulse)
name: "Water Pulse Meter"
#unit_of_measurement: "liter/min"
icon: "mdi:water"
id: water_pulse_meter
total:
name: "Water Meter Total"
unit_of_measurement: "m³"
id: water_meter_total
accuracy_decimals: 3
device_class: water
state_class: total_increasing
filters:
- multiply: 0.01 # (10L/1 pulse)
Thanks for any suggestion:)
Hello @GiuseppeP96 were you able to solve the issue with the reset of the total value?
I am also configuring a water meter with pulse_meter with 1 pulse per 10 Liter and tried to reuse you config. One thing made me curious:
should the filter be rather multiply: 0.001 to convert to m3?
No, i’m still experiencing resets.
My meter has 1 pulse each 10L so the filter is correct for my case (divide by 100). If you have a different meter adjust it accordingly 
Issue can be solved with integration sensor or by saving the total on global variable and restoring from there on boot.
I’ve solved the resets it in Home Assistant with a Utility Meter Helper.
It can also be calibrated to match the value of the physical meter, so I have always the metered value