Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong values after upgrade to ESPHome 2023.8.0 #314

Closed
wants to merge 1 commit into from

Conversation

Barma-lej
Copy link

@Barma-lej Barma-lej commented Nov 5, 2023

When upgrading from 2023.7.1 to 8.0, it appears that the pulse_meter function has become broken or changed. The counter goes crazy and increments at a high rate endlessly.

There was a lot of issues:
#298 #301 #302 #309

In ESPHome 2023.8.0, there was a pulse_meter refactoring. The default mode is now EDGE instead of PULSE as before.

To use the PULSE mode, you need to add the internal_filter_mode option to the pulse_meter configuration, like this:

  - platform: pulse_meter
    name: '${friendly_name} - Power Consumption'
    id: sensor_energy_pulse_meter
    internal_filter_mode: PULSE
    unit_of_measurement: 'W'
    state_class: measurement
    ...

When upgrading from 2023.7.1 to 8.0, it appears that the `pulse_meter` function has become broken or changed. The counter goes crazy and increments at a high rate endlessly.
@Barma-lej Barma-lej closed this Nov 7, 2023
@Barma-lej
Copy link
Author

It's better to use option internal_filter: 100ms

@chimeranzl
Copy link

chimeranzl commented Apr 15, 2024

Really? I get no results at all if I set internal_filter higher than 5ms. EG:

internal_filter_mode: PULSE
internal_filter: 5ms

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants