Loxone Support Community

Find answers, ask questions and become part of the Loxone Community.

Loxone Support Community › Category: Loxone Config › Wrong production value on energy monitor since update to version 12 – Way to restore a backup
0 Vote Up Vote Down
3 years ago
Wrong production value on energy monitor since update to version 12 – Way to restore a backup

Hi all,

since the update to version 12 yesterday, I got a false energy production peak value value point of 2.1GWh at 4:20 in the morning.

This is messing with the statistics and the Energy monitoring as I’m using absolute value, my energy monitor is now unusable.

I have a full backup done before the update to version 12 but I don’t see a way to restore!

I don’t mind losing a day or two of data but resetting the monitor and losing more than a year is not a solution.

Thanks for your help

Attachments
Production-peak.png
Statistics.png
5 Answers
0 Vote Up Vote Down
3 years ago

Didn’t found the root cause but restoration through SD card format with the backup went smouthly.

The only weird thing is the cache of the app that keep showing me the peak in my production.

3 years ago

There is now a known issue for Modbus TCP with the timeout published for 12.0.2.23 but I’have the same bug with 12.0.2.24:
https://docs.google.com/document/d/1pOcIBq3jUUmhR_Fii33rWs8Gp7iTeMxa2EzvcvXjWtM/edit

0 Vote Up Vote Down
3 years ago

I have the same? whats the solution?

0 Vote Up Vote Down
3 years ago

Same problem here.

Is there a way to alter the wrong values manually? E.g. via FTP directly on the SD card?

0 Vote Up Vote Down
3 years ago

I got no more wrong value with a timeout of 1000ms on the Modbus Server parameters.

There is no way to correct the values in the statistics. The only possibility is to wait for the end of the month and trash the archive of the corresponding month…

The bigger problem is if the value was an absolute energy value used with an energy monitor block. Then the block will not see any new energy consumption.

The only solution is to restore a backup. Fortunately I had a Loxberry that do daily backup to recover from that situation.

Without backup, you have to start over…

It was already a bad situation to be with a user configuration error but it’s even worse when it’s coming with an update and now way to recover properly from the situation!

3 years ago

Thanks for your reply. This is indeed the case, I’m using a absolute value and the block won’t see any new production in my case.. I’ll re-install a backup and change the timeout to 1000ms… Luckily I made a backup before the upgrade. Thanks again.

0 Vote Up Vote Down
3 years ago

when does this problem going to be fixed?

1000ms timeout should work right now.