Strange Energy Spike in day graph

[mwilens]

Hi,
In my day chart I see an energy spike of 626kW (626400W), expexted is less than 200W
Can Anyone explain what this is and if i can prevent nonexisting values?

I'm Using Domoticz Version: 4.9700,, Python Version: 3.5.3, [GCC 6.3.0 20170516] on a Raspberry Pi
and a P1 cable from Ali (just €8 https://nl.aliexpress.com/item/ftdi-ft2 ... 09308.html)

Thanks in advance

[cvro]

Same thing here. Spikes occur when clock is set back one hour, Oct 28 02.00 - 03.00, end of summertime daylight saving hours.
Could be a bug due to double use of the same time?

[SweetPants]

Yet another reason to get rid of winter and summertime

[Silenus]

Same 'problem' here, definitely looks like a bug.

[mwilens]

Thanks for the hint about the summertime daylight saving hours.
It might be a domoticz bug, the energy supplier shows a normal graph.
Tanks all, I'm not worried anymore

[Silenus]

If you take a look in the table MultiMeter you'll notice that there are duplicate values between 2 and 3AM
The graph is set as a 'counter' type and it will calculate the difference between all the datapoints and show that as the value.
And because it's very weird to have a value of 17260414 and a value of 17259785 5 minutes later, the counter 'wraps' and shows you a ridiculous number.

17259542|1|730|0|18630530|3|2018-10-28 01:45:00
17259604|1|740|0|18630530|3|2018-10-28 01:50:00
17259664|1|740|0|18630530|3|2018-10-28 01:55:01
17259725|1|720|0|18630530|3|2018-10-28 02:00:00
17260414|1|630|0|18630530|3|2018-10-28 02:00:00
17259785|1|710|0|18630530|3|2018-10-28 02:05:00
17260466|1|620|0|18630530|3|2018-10-28 02:05:00
17259845|1|720|0|18630530|3|2018-10-28 02:10:00
17260519|1|620|0|18630530|3|2018-10-28 02:10:00
17259905|1|720|0|18630530|3|2018-10-28 02:15:00
17260572|1|630|0|18630530|3|2018-10-28 02:15:00
17259965|1|710|0|18630530|3|2018-10-28 02:20:00
17260624|1|630|0|18630530|3|2018-10-28 02:20:00
17260026|1|730|0|18630530|3|2018-10-28 02:25:00
17260677|1|630|0|18630530|3|2018-10-28 02:25:00
17260088|1|750|0|18630530|3|2018-10-28 02:30:00
17260729|1|630|0|18630530|3|2018-10-28 02:30:00
17260149|1|660|0|18630530|3|2018-10-28 02:35:00
17260782|1|620|0|18630530|3|2018-10-28 02:35:00
17260203|1|640|0|18630530|3|2018-10-28 02:40:00
17260835|1|630|0|18630530|3|2018-10-28 02:40:00
17260256|1|620|0|18630530|3|2018-10-28 02:45:00
17260887|1|620|0|18630530|3|2018-10-28 02:45:00
17260308|1|630|0|18630530|3|2018-10-28 02:50:00
17260940|1|620|0|18630530|3|2018-10-28 02:50:00
17260361|1|640|0|18630530|3|2018-10-28 02:55:00
17260992|1|630|0|18630530|3|2018-10-28 02:55:01
17261045|1|620|0|18630530|3|2018-10-28 03:00:00
17261101|1|750|0|18630530|3|2018-10-28 03:05:00
17261164|1|750|0|18630530|3|2018-10-28 03:10:00
17261227|1|710|0|18630530|3|2018-10-28 03:15:00

[GSV3Miac]

Yes, just saw the same problem. Apparently Domoticz is using local time for the X axis of the graphs and tables, and doesn't cope at all well when 01:00 happens all over again at 02:00. Maybe Dom should record all its data using UTC, and sort out local time axis if the user really wants it later. Presumably it has brain fade in the other direction in the spring, when there is an hour of data (in local time) missing.