Open rybber78 opened 2 years ago
Indeed a high value. What type of inverter do you have?
I recall having this issue when I forgot to set invtype
I also think that is the issue. That is the reason why I askedfor inverter type
You probably have to specify invtype = sph (or spf) in grott.ini or -e ginvtype= "sph" in docker run command.
Yes, adding the following to docker-compose.yml fixed it:
But I have another problem. Timestamps are wrong. I have Europe/Amsterdam in docker compose. GMt+1 in PVoutput settings, but there is a 6 hour difference from what is sent by Grott?
{'d': '20220908', 't': '07:44', 'v1': 12000, 'v2': 3016.3, 'v6': 235.5}
(local time is 13:44)
Is it possible these are buffered records and the inverter try to catch up?
In you record above the time was 10:18 seems to be okay for me.
As far I can see the time in the data record (from the inverter) is being used.
You can detect if it is a buffered record if in the mqtt Json message buffered : yes is shown.
Challenge with pvoutput is that if there are to much buffered records being sent you reach very fast the limit of 60 message / hour.
That is probably only once. But if it stays the you can disable buffer processing by grott by specifing gsendbuf = "False".
New install. Will not upload to PVoutput because of this error. System size is 9360W in PVoutput.
Grott Docker log: