# Loads – very high, unrealistic consumption peaks

**URL:** <https://community.victronenergy.com/t/loads-sehr-hohe-unrealistische-peaks-beim-verbrauch/58717>\
**Category:** Deutschsprachiger Bereich\
**Tags:** energy\_meter, beginner, cerbo-gx\
**Created:** [1 June 2026 13:18 UTC](https://community.victronenergy.com/t/loads-sehr-hohe-unrealistische-peaks-beim-verbrauch/58717 "2026-06-01T13:18:50Z")\
**Posts on this page:** 8\
**Page:** 2

<div class="post-metadata">

**Author:** ![Milchmann](https://avatars.discourse-cdn.com/v4/letter/m/ce73a5/32.png) [@Milchmann](https://community.victronenergy.com/u/Milchmann)\
**Post date:** [13 June 2026 17:50 UTC](https://community.victronenergy.com/t/loads-sehr-hohe-unrealistische-peaks-beim-verbrauch/58717/21 "2026-06-13T17:50:35Z")

</div>

I’ve now disabled all the other meters apart from the EM24 grid meter. I’m still seeing peaks of nearly 3000kWh. It’s great that they aren’t being added together, but it obscures the others.

Does anyone have any other ideas?

 ![IMG_8820](https://europe1.discourse-cdn.com/victron/original/3X/d/0/d0b47c8071ec347b2b8e776c5bb539f2ef1e1623.jpeg)

 ![IMG_8821](https://europe1.discourse-cdn.com/victron/original/3X/8/f/8f9b7a7da7bf20f674ed89f9c9ffdc8cf5a3c88f.jpeg)

---

<div class="post-metadata">

**Author:** ![dognose](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/dognose/32/968_2.png) [@dognose](https://community.victronenergy.com/u/dognose)\
**Post date:** [15 June 2026 20:16 UTC](https://community.victronenergy.com/t/loads-sehr-hohe-unrealistische-peaks-beim-verbrauch/58717/22 "2026-06-15T20:16:08Z")

</div>

Hi,

this is the Shelly for your heat pump — it sometimes reports a “0 meter reading”, which triggers a reset in the analysis. Then, as soon as it reports the correct 2666 kWh again, the analysis interprets that as 2666 kWh of “consumption” in that minute.

 ![image](https://europe1.discourse-cdn.com/victron/original/3X/6/a/6a36747ce35683cd33971fdf1c106423a3507633.png)

How have you integrated it? (Shelly integration, Node-RED, third-party script)?

---

<div class="post-metadata">

**Author:** ![Milchmann](https://avatars.discourse-cdn.com/v4/letter/m/ce73a5/32.png) [@Milchmann](https://community.victronenergy.com/u/Milchmann)\
**Post date:** [16 June 2026 04:12 UTC](https://community.victronenergy.com/t/loads-sehr-hohe-unrealistische-peaks-beim-verbrauch/58717/23 "2026-06-16T04:12:06Z")

</div>

That’s right. I do have a Shelly in front of the heat pump, but they haven’t been able to be integrated via the console for very long. I had the Cerbo search for the Shellys, and the one for the heat pump was still enabled too. I’ve disabled it now. Otherwise, they’re not integrated into the Victron system. I only use it via the Shelly app. The Shelly has also been there longer than the peaks have been occurring.

---

<div class="post-metadata">

**Author:** ![kr0815](https://avatars.discourse-cdn.com/v4/letter/k/48db29/32.png) [@kr0815](https://community.victronenergy.com/u/kr0815)\
**Post date:** [16 June 2026 18:42 UTC](https://community.victronenergy.com/t/loads-sehr-hohe-unrealistische-peaks-beim-verbrauch/58717/24 "2026-06-16T18:42:55Z")

</div>

> [@dognose](#):
>
> That’s your heat pump Shelly — it sometimes reports a “zero meter reading”, which triggers a reset in the data processing, and as soon as it reports the correct 2666 kWh again, the data processing interprets 2666 kWh as “consumption” for that minute.

But surely Victron should be able to sort that out?

I’ve encountered similar problems with Volkszähler in the past: a cumulative consumption meter can’t report zero or values that differ significantly

An alternative might be to send the power reading in watts instead of absolute meter readings?

Yes, that sounds less accurate at first, but in practice it works surprisingly well

---

<div class="post-metadata">

**Author:** ![dognose](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/dognose/32/968_2.png) [@dognose](https://community.victronenergy.com/u/dognose)\
**Post date:** [16 June 2026 22:49 UTC](https://community.victronenergy.com/t/loads-sehr-hohe-unrealistische-peaks-beim-verbrauch/58717/25 "2026-06-16T22:49:57Z")

</div>

> [@kr0815](#):
>
> but surely Victron should be able to get that under control?

If the problem is on our side, certainly 🙂

In general, though, there are meters that deliberately reset to 0 — after a restart, at regular intervals, when the maximum value of the register is reached, and so on. The energy calculation handles that as intended — only unintended “zeroes” are false positives and should be avoided.

So we’d need to identify and “fix” the exact cause, which is why I asked how the Shelly is connected. Third-party scripts are unfortunately sometimes not protected against “zeroes” if, for example, there’s an MQTT reconnect, or some part of the system turns `null` into a `0`, etc.

It does get tricky, of course, if the Shelly itself is the cause. The EM3 has cropped up in a few threads, whereas, as far as I remember, the PM Shellies never have.

> [@kr0815](#):
>
> Would an alternative be to report power in watts instead of absolute meter readings?  
> Yes, that sounds less accurate at first, but works surprisingly well in practice

I do that too in some cases where there’s no other option, but if the device sends meter readings, it’s not really necessary. It also offers no protection against temporary communication outages. The device’s internal meter keeps counting, and the reading is then at least recorded “with a delay” once the fault is fixed.

---

<div class="post-metadata">

**Author:** ![Milchmann](https://avatars.discourse-cdn.com/v4/letter/m/ce73a5/32.png) [@Milchmann](https://community.victronenergy.com/u/Milchmann)\
**Post date:** [17 June 2026 10:00 UTC](https://community.victronenergy.com/t/loads-sehr-hohe-unrealistische-peaks-beim-verbrauch/58717/26 "2026-06-17T10:00:24Z")

</div>

So I installed this one and have now disabled it in the console. Let’s see if things are quiet now.

Thanks for now.

 ![IMG_8967](https://europe1.discourse-cdn.com/victron/original/3X/e/d/ed63f4e0958367d043566ab17d1135d400d54365.jpeg)

---

<div class="post-metadata">

**Author:** ![mi-hol](https://avatars.discourse-cdn.com/v4/letter/m/f6c823/32.png) [@mi-hol](https://community.victronenergy.com/u/mi-hol)\
**Post date:** [20 July 2026 08:59 UTC](https://community.victronenergy.com/t/loads-sehr-hohe-unrealistische-peaks-beim-verbrauch/58717/27 "2026-07-20T08:59:09Z")

</div>

> [@Milchmann](#):
>
> MultiPlus-II 48/5000/70-502623 HQ2219T7HKT v505v560 **Update device - I’ll do that in winter-**

and “Cerbo GXC00A HQ2215ZJYVG v3.73v3.73 Up to date”  
I’d almost bet that Victron doesn’t test this combination of firmware.

For cost reasons, you have to focus on current versions when testing.  
Since I come from a software development background, I’ve got into the habit of installing new firmware about two months after its release.

That saves a lot of hassle with computers, and so far it’s worked well for me with Victron too.

---

<div class="post-metadata">

**Author:** ![Milchmann](https://avatars.discourse-cdn.com/v4/letter/m/ce73a5/32.png) [@Milchmann](https://community.victronenergy.com/u/Milchmann)\
**Post date:** [4 August 2026 15:08 UTC](https://community.victronenergy.com/t/loads-sehr-hohe-unrealistische-peaks-beim-verbrauch/58717/28 "2026-08-04T15:08:55Z")

</div>

It was the Shelly. Ever since it was disabled in the Shelly device class, the peaks have stopped! 🙌

[Previous page](https://community.victronenergy.com/t/loads-sehr-hohe-unrealistische-peaks-beim-verbrauch/58717.md?page=1)
