#Energy Peak/Spike at Midnight

1 messages · Page 1 of 1 (latest)

silk lagoon
#

Hi all,

since 1st of May my Energy Dashboard looks odd and not reliable in its measuring/counting anymore.

somehow i'm getting a big spike of energy consumption whenever a day starts and i can not see why this is now happening since i did not change anything for a while except installing updates.

it looks like the attached screenshots, kinda for everyday since then.
And yeah, most of the time, the device which peaks there is actually not in use...

does anyone else experience the same or does someone know why this is now happening?
would be happy to have this fixed.

thanks in advance!

image.png
#

this is how it looked like a day before
i would say quite normal

image.png
old charm
#

That is really strange

silk lagoon
#

yeah :(

thought maybe its a timezone thing but according to my settings "everything is fine" 😅

#

oh about my devices:
i have meross smart meter plugs which measure the consumption and also using powercalc for adding other devices with a fixed consumption.

but as i mentioned, i did not change my setup for a while now

thick brook
#

what device is giving the spike?

silk lagoon
#

should be my "PC" but that spike is impossible for my PC

thick brook
#

instead of daily consumption sensor try to replace it with a lifetime consumption sensor

silk lagoon
#

my PC gets measured by a smart plug

#

so Powercalc should not affect that (i hope)

thick brook
#

check if your plug has a lifetime consumption sensor and use it instead of daily

silk lagoon
#

lol this is soooo odd!
unfortunately it had no lifetime consumption entity...
but an consumption and energy entity both with the same value....
it was energy before and i changed it to consumption and it kinda fixed it except for some days :D but now it is way more reliable and kinda back to normal, thanks @thick brook !

thick brook
#

still doesnt look good

silk lagoon
#

some days it looks like this but i can live with it :D
(and no, i did not get up in the middle of the night and played something xD)

image.png
thick brook
#

tuya plug?

silk lagoon
#

no meross 305

thick brook
#

yeah that's tuya

silk lagoon
#

really? wasnt aware of that :)

thick brook
#

or maybe not im not sure haha. But it does look like other tuya stuff

#

can fix the broken days in dev tools -> statistics. And to prevent further spikes wrap it in a utility meter sensor

silk lagoon
#

yeah thats a good idea! i will observe it further and if it happens again, than i will do that

#

right now i can live with it :)

#

since it seems to be fixed (except for some hours xD)

#

but the values are not sooo wrong like before and some measure issues are for now OK, until i get more tools to do automations, then i will go for "perfect" values :)

#

thanks!

latent moss
#

Hi, I might have a similar situation with a spike in the solar production showing on the energy graph every night. I think it comes from the fact that I have two victron energy solar charge controllers which are not resetting the daily yield exactly at the same time and therefore there is a new value when the first one resets.

Is this similar to the problem here and how would I go about fixing this?

viral ivy
#

Don't combine sensors.

#

If you have two, just add them both to energy.

latent moss
latent moss
viral ivy
#

If those daily sensors are appropriately setup w/ correct units and state_class, then yeah you can do that.

latent moss
#

I wanted to add them up to make it look nicer (only one solar input), instead of having two seperate ones which also brings two slightly diffrent colored bars

viral ivy
#

You could add if they were really lifetime sensors. IDK why it says "Lifetime" but it resets at night.

latent moss
viral ivy
#

It's really long term statistics that has no good way to handle sums w/ partial resets, it doesn't understand it.

#

So this summation of entities doesn't follow the correct reset rules.

latent moss
viral ivy
#

total_increasing can reset.

#

it just can't decrease

#

in fact if it sees a decrease it just assumes it's a reset

#

I think if you pass your daily victron sensor into a utility meter that could transform it into a lifetime sensor.

#

I believe utility_meter has a way to convert resetting sensors into non-resetting.

#

then you can add the two utility_meters together

latent moss
#

could I hack it by running it through a utility meter first? but those need to have some sort of reset aswell right? at least yearly?

viral ivy
#

I think they just go up forever (unless you manually reset them)

latent moss
viral ivy
#

That means if the source sensor resets. Yours does, so I assume you want that to be true.

latent moss
viral ivy
#

That's optional.

latent moss
#

just as a note to anyone coming here later on:
Wrapping both Victron Charge Controllers each in its own Utility Meter with no Cycle and then using a template sensor with the correct setup works and eliminates the spikes from the nightly reset.
My template sensor:

      - name: "Solar Yield Combined Lifetime"
        unique_id: solar_yield_combined_lifetime
        unit_of_measurement: "Wh"
        device_class: energy
        state_class: total_increasing
        state: >
          {{ (states('sensor.solar_yield_buttner_utility_lifetime') | float(0)) +
             (states('sensor.solar_yield_gns_utility_lifetime') | float(0)) }}
thick brook