Growatt 4600TL-XE to PVoutput - no daily reset? #96
Replies: 12 comments 8 replies
-
|
Strange. I have not had an issue with that before. I do not say that it is not a problem with Grott that is always possible of course. I need then a part of the Grott log at the moment this occurs so I can see what data the inverter has produced and how Grott processed that and sent it to PVOutput. Do you think that is possible ? |
Beta Was this translation helpful? Give feedback.
-
|
Do you mean start the command journalctl -u grott at the beginning of such a ‘bad’ day? That should be no problem
…On 7 Feb 2022, 17:02 +0100, Johan Meijer ***@***.***>, wrote:
Strange. I have not had an issue with that before.
I do not say that it is not a problem with Grott that is always possible of course. I need then a part of the Grott log at the moment this occurs so I can see what data the inverter has produced and how Grott processed that and sent it to PVOutput.
Do you think that is possible ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Yes. With data that is sent to pvoutput. So from growatt original data to PVoutput response. Example:
|
Beta Was this translation helpful? Give feedback.
-
|
Hi, problem has not occurred yet. I will report when there’s no reset and send you the grott output
…On 7 Feb 2022, 17:43 +0100, Johan Meijer ***@***.***>, wrote:
Yes. With data that is sent to pvoutput. So from growatt original data to PVoutput response.
Example:
• Growatt original Data:
\x02\x3e\x00\x06\x01\x01\x01\x04\x0d\x22\x2c\x45\x59\x45\x4c\x74\x41\x2d\x77
\x61\x74\x74\x47\x72\x6f\x77\x61\x74\x74\x47\x72\x6f\x77\x61\x74\x74\x47\x72
\x3e\x3a\x23\x46\x4c\x75\x41\x5d\x41\x50\x74\x74\x47\x72\x6f\x77\x61\x74\x74
\x3e\x3a\x23\x46\x4c\x75\x41\x5d\x41\x50\x74\x74\x47\x72\x6f\x77\x61\x74\x74
\x47\x72\x6f\x77\x61\x74\x74\x47\x72\x6f\x77\x77\x76\x73\x56\x57\x6d\x75\x61
\x74\x74\x6b\x72\x6f\x77\x61\x74\x74\x4f\x7f\x6f\x77\x61\x74\x74\x47\x72\x6f
\x77\x61\x74\x74\x47\x72\x6f\x77\x61\x74\x67\xc3\x7b\x47\x77\x61\x74\x74\x47
\x72\x6f\x77\x61\x74\x74\x47\x72\x6f\x77\x61\x74\x74\x47\x72\x6f\x77\x61\x74
\x74\x77\x72\x6f\x86\x79\x71\xd2\xea\x6d\x6f\x9d\x61\x74\x74\x47\x72\x6f\x77
\x61\x74\x74\x47\x72\x6f\x77\x61\x74\x74\x47\x7a\x73\x77\x61\x74\x74\x47\x5f
\x6f\x2e\x2f\x54\x74\x47\x72\x6f\x77\x61\x74\x47\x47\x72\x92\x09\x61\x74\x74
\x47\x72\x6f\x77\x61\x74\x74\xba\x0c\x6f\x77\x61\x74\x74\x47\x72\x6f\x77\x61
\x74\x74\x47\x72\x6f\x77\x61\x74\x74\x47\x72\x6f\x77\x61\x74\x74\x47\x78\x6f
\x76\x6b\x61\x71\x47\x77\x65\x77\x75\x7e\x0d\x07\x06\x6f\x77\x6f\x32\x74\x47
\x7f\xe3\x77\x61\x74\x76\x47\x40\x6f\x77\x61\x74\x74\x47\x72\x6f\x33\x1f
• Grott automatic protocol detection
• Grott data record length 265
• layout : T060104
• no matching record layout found, try generic
• Record layout used : T06NNNN
• Growatt data decrypted V2
• Grott Growatt data decrypted
• Growatt plain data:
023e0006010101044a50433238313833334200000000000000000000000000000000000000005
14d42323832333236310000000000000000000000000000000000000000160207112502020000
002c000000000000080d000000000000000000000000000000000000138409280000000000000
0000000000000000000000000000000000000300000f11805a6ad1f00ea000000000000000000
000000000000000000081c00000000002d00594e2000000000000000330000fd7e00000000000
000000000fd7e0000000000000000000000000000000000000000000000000000000a00010a15
0500050a00140a79407400000e4600000d8c0000000200320000000000000000447e
• Growatt new layout processing
- decrypt : True
- offset : 6
- record layout : T06NNNN
• Grott data record date/time processing started
• date-time: 2022-02-07T17:37:02
• Grott values retrieved:
- datalogserial : xxxxxxxxx
- pvserial : xxxxxxxxx
- pvstatus : 0
- pvpowerin : 0.0
- pv1voltage : 206.1
- pv1current : 0.0
- pv1watt : 0.0
- pv2voltage : 0.0
- pv2current : 0.0
- pv2watt : 0.0
- pvpowerout : 0.0
- pvfrequentie : 50.0
- pvgridvoltage : 234.4
- pvgridcurrent : 0.0
- pvgridpower : 0.0
- pvgridvoltage2 : 0.0
- pvgridcurrent2 : 0.0
- pvgridpower2 : 0.0
- pvgridvoltage3 : 0.0
- pvgridcurrent3 : 0.0
- pvgridpower3 : 0.0
- pvenergytoday : 4.8
- pvenergytotal : 6172.0
- totworktime : 13168.0
- pvtemperature : 23.4
- pvipmtemperature : 0.0
- epv1today : 5.1
- epv1total : 6489.4
- epv2today : 0.0
- epv2total : 0.0
- epvtotal : 6489.4
• MQTT jsonmsg:
{"device": "xxxxxxxxx", "time": "2022-02-07T17:37:02", "buffered": "no",
"values": {"datalogserial": "xxxxxxxxx", "pvserial": "xxxxxxxxx",
"pvstatus": 0, "pvpowerin": 0, "pv1voltage": 2061, "pv1current": 0,
"pv1watt": 0, "pv2voltage": 0, "pv2current": 0, "pv2watt": 0, "pvpowerout":
0, "pvfrequentie": 4996, "pvgridvoltage": 2344, "pvgridcurrent": 0,
"pvgridpower": 0, "pvgridvoltage2": 0, "pvgridcurrent2": 0, "pvgridpower2":
0, "pvgridvoltage3": 0, "pvgridcurrent3": 0, "pvgridpower3": 0,
"pvenergytoday": 48, "pvenergytotal": 61720, "totworktime": 94809375,
"pvtemperature": 234, "pvipmtemperature": 0, "epv1today": 51, "epv1total":
64894, "epv2today": 0, "epv2total": 0, "epvtotal": 64894}}
• Grott MQTT topic used : energy/growatt
• Grott MQTT message retain enabled
• MQTT message message sent
• Grott send data to PVOutput systemid: xxxx for inverter: xxxxxxxxx
• Grott PVOutput send V1 disabled
- {'X-Pvoutput-Apikey': 'xxxxxxxx', 'X-Pvoutput-SystemId': 'xxxxx'}
- {'d': '20220207', 't': '17:37', 'v2': 0.0, 'v6': 234.4, 'v5': 23.4}
• Grott PVOutput response:
- OK 200: Added Status
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Ok. We will wait ;) |
Beta Was this translation helpful? Give feedback.
-
|
Well it went wrong again this morning. Feb 14 08:06:53 DietPi grott[1069]: - Growatt original Data: |
Beta Was this translation helpful? Give feedback.
-
|
@petestorms Hmm ok. It seems that your datalogger (shinelanbox?) has not reset the daily values. So the values are still there from the previous day are still there and are being sent in the datarecord. An other strange thing is that the data record does not contain a date/time value, see message: I am not sure if in a normal situation there is date/time value in the data record. Can you see this? I expect something like this in the log: Is there a possibility to specify date time/time source in your datalogger (it is not possible in a shinewifi)? I have seen this once before but did not realize then that this might give value reset/pvoutput issues. The PVOUTPUT issue might not occur when you use a new feature of version 2.7.1 (2.7 branche). I have put this in on request. Be aware the problem is not gone the wrong values (of the day before) are still being sent to MQTT and INFLUXDB. Do you use the blockcmd command feature of Grott? If you use this we can detect if date/time update configuration commands are sent from growatt to the datalogger. I see this multiple times per day in my log (Grott blocks all command except the datetime updates): Maybe that can give an direction where we have to look for a solution. It is a difficult issue I think and am afraid Grott can not fix it at this moment. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks perhaps we can get further ;-)
no or no valid time/date found, grott server time will be used (buffer records not sent!) This seems to be 'normal'.
Changing source does not seem possible at least that is what I understand.
|
Beta Was this translation helpful? Give feedback.
-
|
The time settings seem to be ok. It is maybe a good idea the run sometime without blockcmd. Maybe Grott is filtering to much (although I expect then more blocked messages). If you have disabled blockcmd maybe you can also perform an update of the software (if available)? How do you use Grott? As a docker container on a RPI? I have not build a new image for RPI because it isn't downloaded that much and to be honest my RPI with docker is somewhere in a box because of a small rebuild of my home office (hobby room). |
Beta Was this translation helpful? Give feedback.
-
|
I unblocked, and will see if there is an update. |
Beta Was this translation helpful? Give feedback.
-
|
Ok. Lets see if the failure still exists with unblocking. If it is gone we (I) have a challenge ;) The 2.7 (beta) branch you can find here: https://github.com/johanmeijer/grott/tree/2.7-(Beta). |
Beta Was this translation helpful? Give feedback.
-
|
The issue came back yesterday and this morning, even when the blocking was on. I just installed the 2.7 version. I did a bit of analyzing, please take a look at the value of pvenergytoday sent from the beginning of the day Feb 21 07:36:59 DietPi grott[6006]: - pvenergytoday : 1.2 So, the first time the value is sent on a new day, it contains the end total of the day before. After this initial error, it is brought back to zero the following dump interval a few minutes later. I see the same goes for epv1today and epv2today which are the basis for pvenergytoday. So, I added the option in the grott.ini to disable sending energytoday. Pvoutput should now do its own clean calculations? I should see an improvement. I hope at least :-) |
Beta Was this translation helpful? Give feedback.
-
|
Yes lets see if that helps. I do understand that the end of day processing in the inverter (datalogger) is done the first thing of the morning of the next day when is start again. What I do not understand that he also sends a record with values of the day before. Normally I expect then a value with a different timestamp but your records does not have a time stamp (that is also not usal but I have seen it before). Can you send detailed information of the first record? Maybe there is an indication in it that is some kind of summary oid.? Maybe in the future if I implement sending commands in Grott sending a time command at regular basis will help. You can emulated this via the growatt server website by hand (and probably also via the API but I have no look deeper in that). |
Beta Was this translation helpful? Give feedback.
-
|
This is the first data from yesterday. Feb 21 07:36:59 DietPi grott[6006]: - Growatt original Data: |
Beta Was this translation helpful? Give feedback.
-
|
A difference I see in the records is that is the "previous day" record. The status is 0 and it is producing no power yet (although there is already a voltage, otherwise the inverter will not start, or is yours always powered on?). Maybe that the reset is being done the moment the cells are really getting the status 1 (on). Now I thinking about is this seem to be a status I had at the end of the day. When it was already a little bit dark and the inverter was switch off and later came back. At that moment the daily values were resetted (a little bit the other way around). If the PVOutput change doesn't help we can try to build in a (optional) filter that filter out those records where status is 0. Maybe that helps. But I really have to see (test) what the side effects of this might be, |
Beta Was this translation helpful? Give feedback.
-
|
I see what you mean. So in my case, the resetting of the pvenergytoday sometimes happened not at the end of the day but after switching on the next day. Why not reset only the first record of the day if it is not zero? |
Beta Was this translation helpful? Give feedback.
-
|
I think maybe there has been a fix in firmware that prevent my problem (reset to early at the end of the day) but resulted in your problem. I have to think about grott resetting the record at the beginning of the day. At this moment grott has no memory (it is stateless) so I do not know if it is the first record or not. And are you sure it is the first and only record? Maybe there are more records that have the same issue? Let's first see if the pvoutput option helps. Hopefully this is a "winter" issue. In somer probably the start energy is enough to perform the reset directly. |
Beta Was this translation helpful? Give feedback.
-
|
No I am not sure if this is the only record, sorry. Let’s see what happens now I installed new sw with extra parameter. |
Beta Was this translation helpful? Give feedback.
-
|
I think it's better to change &v1 energytoday to pvenergytotal. |
Beta Was this translation helpful? Give feedback.
-
|
well, anyway, I am not touching anything anymore. Everything seems to be behaving as it should. Thank you very much! |
Beta Was this translation helpful? Give feedback.
-
Hi first of all thanks for the Grott software. I use it to upload my output every 5 minutes. It does not seem to work perfectly, however. Every new day when new output becomes available (inverter switches on) the cumulative data for the next day is used as a starting point. So in stead of starting at 0 kWh, it already contains data. For example my live data for an specific day:
https://pvoutput.org/intraday.jsp?id=99527&sid=87638&dt=20220206
On this rainy ray I see the output of the day before in green.
Sometimes, however, it does work and there is a reset. So not 100% sure what is going on. First I thought it was a problem with PVoutput but I have not seen the issue mentioned there in de forum. Could it be that there is something going wrong in your script?
Beta Was this translation helpful? Give feedback.
All reactions