search

johanmeijer / grott

Growatt inverter monitor
https://github.com/johanmeijer/grott/wiki
397 stars 111 forks source link

Incomplete data points for a day #590

Open Ebrink opened 2 months ago

Ebrink commented 2 months ago

Hi,

I'm using grott (ledidobe/grott:beta) to read data from two MIN 3600 TL-X inverters and then put into influxdb. for some time now, I've had incomplete data: most of the days, I won't get any new data points starting at around 15:00 CEST (see attached image). Next data points start the following morning.

[influx]

Influxdb parameters definitions

influx = True influx2 = True ip = 192.168.1.3 port = 8086 token = redacted org = redacted bucket = redacted timezone = europe/amsterdam

Anyone else experiencing this?

Screenshot 2024-09-05 at 08 20 56 Screenshot 2024-09-05 at 08 24 35 Screenshot 2024-09-05 at 08 24 59
johanmeijer commented 2 months ago

@Ebrink kan you sent a part of the grott log from the time the influx recording seems to stops?

My first thought is that there is a time drift in your datalogger (happens more often) and that the datalogger / inverter date-time is not matching with the real time (datapoint can be generated but in the past or future). When the inverter is restarted in the morning the inverter time is being reset (time update sent from growatt) and everything seem to be oke again.

Of course you can check this by restarting grott (or inverter) after 15:00. If this is the case the time=server parameter in the grott.ini [Generic] segment might help. Then not the inverter/datalogger time is being used but the time from the sserver on which grott is running.

Ebrink commented 1 month ago

Hi @johanmeijer,

Please find the logs attached. I have changed the configuration to reflect the time=server parameter, and that seems to work.

In the logs below, inverter RAL2CJT03G does not have any information in influx after 14:12. detail.log

johanmeijer commented 1 month ago

Hmm strange time values, interesting

The RAL2CJT07T has the last "normal" time @14:15 after that he jumps to 07.10 The RAL2CJT03G never has a "normal" date/time field in this log.

I am not sure what cause the datalogger to insert the wrong time. It can be a firmware issue or a timedrift. Seeing the offset of 7 hours at once I think it is firmware issue.

What type of dataloggers do you use? The shinewifi / shinelan or shinelink with RF dataloggers?

Ebrink commented 1 month ago

Hi @johanmeijer, these are shinewifi-x modules.

johanmeijer commented 1 month ago

Ok. There seems to be more dataloggers with the same problem.

I think the only way to bypass this is to use the time=server parameter or stop/start grott at regular basis.

If you use grottserver it is also possible to set the date/time via the API.

Please also see #595.