SolarForecast - Fehlermeldung Data Memory

[rallye]

Hallo!

Ich habe heute folgende Meldung in meinem SolarForecast Modul entdeckt:

Code Auswählen Erweitern

Data Memory There may be '9' incorrect value(s) in the 'con' key of the pvHistory Storage.
See Logfile for detailed information and how these value(s) could be corrected
Eine Suche im Log (ich habe täglich neue Logs) auch über die letzten Tage hat mir keinen Treffer gebracht. Eine Google-Suche ebenfalls nicht. Was mache ich mit dieser Meldung?
Denke & Grüße Rallye

[DS_Starter]

Wenn du den Konfigurationscheck ausführst und diese Meldung erscheint findest du im Log mit verbose 1 so ähnliche Meldungen:

Code Auswählen Erweitern

2025.02.24 22:19:34.029 1: SolCast6 - WARNING - The stored Energy consumption of day/hour 04/14 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolCast6 reset consumptionHistory 04 14'.
2025.02.24 22:19:34.032 1: SolCast6 - WARNING - The stored Energy consumption of day/hour 04/15 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolCast6 reset consumptionHistory 04 15'.
2025.02.24 22:19:34.035 1: SolCast6 - WARNING - The stored Energy consumption of day/hour 18/13 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolCast6 reset consumptionHistory 18 13'.
2025.02.24 22:19:34.037 1: SolCast6 - WARNING - The stored Energy consumption of day/hour 18/16 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolCast6 reset consumptionHistory 18 16'.
2025.02.24 22:19:34.039 1: SolCast6 - WARNING - The stored Energy consumption of day/hour 19/13 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolCast6 reset consumptionHistory 19 13'.
2025.02.24 22:19:34.041 1: SolCast6 - WARNING - The stored Energy consumption of day/hour 19/14 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolCast6 reset consumptionHistory 19 14'.
2025.02.24 22:19:34.042 1: SolCast6 - WARNING - The stored Energy consumption of day/hour 19/15 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolCast6 reset consumptionHistory 19 15'.
2025.02.24 22:19:34.044 1: SolCast6 - WARNING - The stored Energy consumption of day/hour 20/13 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolCast6 reset consumptionHistory 20 13'.
2025.02.24 22:19:34.046 1: SolCast6 - WARNING - The stored Energy consumption of day/hour 23/16 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolCast6 reset consumptionHistory 23 16'.
2025.02.24 22:19:34.048 1: SolCast6 - WARNING - The stored Energy consumption of day/hour 31/15 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolCast6 reset consumptionHistory 31 15'.

Dort steht die Handlungsanweisung zur Problemlösung ebenfalls drin.

Grüße,
Heiko

[rallye]

Danke. Hatte soetwas:

Code Auswählen Erweitern

2025.02.25 13:03:10 1: SolarForecast - WARNING - The stored Energy consumption of day/hour 17/01 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolarForecast reset consumptionHistory 17 01'.
2025.02.25 13:03:10 1: SolarForecast - WARNING - The stored Energy consumption of day/hour 18/01 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolarForecast reset consumptionHistory 18 01'.
2025.02.25 13:03:10 1: SolarForecast - WARNING - The stored Energy consumption of day/hour 18/99 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolarForecast reset consumptionHistory 18 99'.
2025.02.25 13:03:10 1: SolarForecast - WARNING - The stored Energy consumption of day/hour 19/01 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolarForecast reset consumptionHistory 19 01'.
2025.02.25 13:03:10 1: SolarForecast - WARNING - The stored Energy consumption of day/hour 20/01 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolarForecast reset consumptionHistory 20 01'.
2025.02.25 13:03:10 1: SolarForecast - WARNING - The stored Energy consumption of day/hour 21/01 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolarForecast reset consumptionHistory 21 01'.
2025.02.25 13:03:10 1: SolarForecast - WARNING - The stored Energy consumption of day/hour 22/01 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolarForecast reset consumptionHistory 22 01'.
2025.02.25 13:03:10 1: SolarForecast - WARNING - The stored Energy consumption of day/hour 23/01 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolarForecast reset consumptionHistory 23 01'.
2025.02.25 13:03:10 1: SolarForecast - WARNING - The stored Energy consumption of day/hour 24/01 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolarForecast reset consumptionHistory 24 01'.
2025.02.25 13:03:10 1: SolarForecast - WARNING - The stored Energy consumption of day/hour 25/01 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolarForecast reset consumptionHistory 25 01'.
2025.02.25 13:03:10 1: SolarForecast - WARNING - The stored Energy consumption of day/hour 25/99 is negative. This appears to be an error. The incorrect value can be deleted with 'set SolarForecast reset consumptionHistory 25 99'.
Hab die Anweisungen befolgt - Fragt sich nur wo das herkommt

Gruß Rallye

[DS_Starter]

Fragt sich nur wo das herkommt

Es geht hier um den Hausverbrauch.
Erkennbar ist, dass regelmäßig jeden Tag in der Stunde 01 (00:00 bis 00:59) ein negativer Verbrauch auftaucht der sich dann auch in der Summe (Hour 99) manifestiert.
In den Verbrauch gehen mehrere Werte ein. Im Wiki habe ich die Zusammenhänge genauer beschrieben.
Um genauer zu sehen was zu der fraglichen Zeit passiert, müsste man ein ctrlDebug=collectData zwischen 00:00 und 01:00 einschalten (z.B. über ein at) und danach das Ergebnis analysieren. Vermutlich gibt es in einem der beteiligten Devices eine Kontinuitätsverletzung der gelieferten Zählerwerte. 
 

[rallye]

Danke für den Hinweis. Bin ab morgen für 3 Wochen nicht daheim, werde es mir aber auf die Liste setzen und es nach meiner Rückkehr angehen.