Statistics Sensor won't hold the previous 0 value

Configuration
1

I have a 5 minute average statistics sensor on a Meross energy monitoring plug. I have an automation detecting when the energy drops below 50w because that is when my washing machine has finished.

The issue is that the sensor stays at 0 for most of the time and occassionally jumps up to 0.6w thus triggering the statistics average to jump up and trigger the automation. The image describes the issue better than I can explain.

I have an energy meter that stays at zero watts most of the time, with m

IMG_1514
IMG_15141179×2556 162 KB


  - platform: statistics
    name: "meross watts (5m)"
    entity_id: sensor.meross_switch_mss310_power_w_main_channel
    state_characteristic: average_step
    max_age:
      minutes: 5

It seems like this is a similar issue.

Until I can fix this issue, my automation will keep triggering:

alias: Washing Machine finished
description: ""
trigger:
  - platform: numeric_state
    entity_id:
      - sensor.meross_watts_5m
    below: 3.1

Any ideas how to work around this so my automations don’t constantly trigger?

2

That shouldn’t trigger from the graph you posted — it should only trigger if the sensor goes from above 3.1W to below. Can you post the automation trace file from a false trigger event?

Why 3.1W in the trigger?