Different value between Lixee and Enedis

[prohand]

Hello,

I’ve noticed that on several days the kWh value between the Lixee and Enedis is different while on other days everything is fine.

Do you have any idea?

Thank you

[pierre-gilles]

@prohand

I noticed that over several days the kWh value between Lixee and Enedis is different while on other days everything is OK.

Do you have any idea which source of truth is the correct one?

To know whether it’s an issue on Enedis’ or Lixee’s side

[prohand]

For me Enedis is OK and there seems to be a problem with the zigbee2mqtt elements:

I don’t see why, for example on the 4th around 8:00 PM I have a kWh spike on my devices:

![image|690x297](upload://jEqHtlfZGvtm

[pierre-gilles]

Very strange! You should look at the raw data to understand, you may have received outliers or duplicate values:

Télécharger un CSV des valeurs historiques d'un capteur

Salut à tous ! Je vous propose aujourd’hui un petit tutoriel pour télécharger un CSV de toutes les valeurs historiques d’un capteur. Pour cela, nous allons passer par l’API HTTP de Gladys. Étape n°1 : Télécharger un client HTTP Je vous conseille Yaak. Étape n°2 : Récupérer un token L’API de Gladys étant sécurisée, il va falloir récupérer un token. Créez une nouvelle requête dans Yaak sur l’URL Méthode : POST URL : http://IP_DE_VOTRE_INSTANCE_GLADYS/api/v1/login Body Type : JSON Body : …

[prohand]

I see that on 04/01 at 20:00 it received 11.96 :

I also have 01/01:

At 20:00 it received 33.85 :

I have no idea why the lixee received this kind of value

After analysis there are only these two days where there are large differences and I can’t explain them

There are also other devices that seem to have consumed a lot over this period but it surprises me that suddenly two devices start consuming a huge amount:

And on other days we can see small differences too, for example:

I can look at other elements if you want to try to find the problem but I’m stumped

Edit :

If I take the example of the server rack (zigbee2mqtt-prise-baie-informatique-switch-energy-energy)

We start at 441.23 :

We end at 441.35 :

Which should have given 0.12 and not 2.56

I think there’s a calculation problem somewhere but I think @pierre-gilles will have an idea

[StephaneB]

I think I have the same issue: I had abnormally high consumption readings on January 5 for most of my devices reported in Z2M (Zigbee2MQTT), while I have nothing unusual on the Enedis reporting. And in fact this happened when I tried to update the devices in the Zigbee integration (and the update failed, which is what is described on https://community.gladysassistant.com/t/probleme-maj-appareil-z2m/9898).

I haven’t had time to look in detail yet, but here are some examples:

[pierre-gilles]

@prohand if I understand correctly, the indexes are fine but the 30-minute consumption values are wrong?

[prohand]

Yes, that’s right

[pierre-gilles]

One option would be to rerun the consumption calculation for 30 minutes and then the cost calculation for 30 minutes, and see if the issue persists or was « fixed » by that!

[prohand]

This solved the bulk of the problem.
However, isn’t this likely to happen again?

I still have some minor differences, I don’t know if that’s normal:

[StephaneB]

@pierre-gilles

One option would be to re-run the consumption calculation for 30 minutes and then the costs for 30 minutes, and see whether the issue persists or was « fixed » by that!

I had thought of that, but since the initial calculation had taken several days, I prefer to wait for the integration of what Terdious has prepared (and which you discussed here)

[mutmut]

@StephaneB

the integration of what Terdious prepared

and I can say that its integration works like a charm, having tested it thoroughly

[pierre-gilles]

@prohand

That solved most of the problem.

That’s great!

@prohand

But this might happen again, right?

That’s exactly what I’d like to know

[quote="

[prohand]

Ok, thanks for the feedback.
I’ll try to be vigilant if it happens again.

[Terdious]

@pierre-gilles

@prohand

I still have small differences, I don’t know if that’s normal:

In this case it can be normal to have small differences because there are precision issues with the Lixee; it doesn’t surprise me.

Yes, it’s normal — having encountered this case (and not with Lixee and Enedis but with my Shelly devices) I confirm that it’s just a rounding issue that can recur over time. As a general rule, it’s negligible, especially when it comes to cost.