Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing Values on MOD 7000TL3-XH with Battery #85

Open
schlidda83 opened this issue Sep 7, 2024 · 19 comments
Open

Missing Values on MOD 7000TL3-XH with Battery #85

schlidda83 opened this issue Sep 7, 2024 · 19 comments
Labels
stale There has not been activity on this issue or PR for quite some time.

Comments

@schlidda83
Copy link

Hi @egguy

i´ve already created issues with Johann and Chris. Seems both are unable to help.
here: johanmeijer/grott#587
and
muppet3000/homeassistant-grott#98 (comment)

No Matter what i do enter in the config... i do not get the battrery values unless i enter "MIN" but that is obviously wrong as i have a MOD one.

at the moment i have this set up
I have not entered the Serial of the inverter because i will only receive wrong values then
image

therefore the log is saying
`

  • Grott automatic protocol detection
    • Grott data record length 585

    • layout : T060104X

    • no matching record layout found, try generic

    • Record layout used : T06NNNNX

    • Growatt data decrypted V2

    • Grott Growatt data decrypted

    • Growatt plain data:
      04bf000602410104475a4c3044413735453600000000000000000000000000000000000000005
      1414c30434739304455000000000000000000000000000000000000000018090710180d020bb8
      0c340001000053e90afc0031000035d20b25001b00001e1700000000000000000000000000000
      000000054bb000001e000004b95138308fe001c0000192d090b001b0000186a08f0001b000018
      210f960f880f7400000000000043eb000010d0027a0656000000c400015ab700016b570000008
      00000c7a5000000700000a3b2000000000000000000000000000000810000008b000011840000
      004500015a020000000000000000000000f000000000fffa003502d30240000118f9015f02060
      152000001a00c960c624e20001b00011170000000000000000000000000000000000000000000
      00003c00000000000100000000000010d0000000d00c350cb10000001a000004e60000003a000
      00538000000000000000100016f1a0000004600015d9500000000000000000000000000000000
      00000000000000000000000000000000000000002710000018960000000b0201000002bf3e5c0
      001006418f60eaf0002000201680000000000be00000000000004e600000538000000020a4700
      0c00010000013f012c0002000c000000000001000000320032000000000000000000000000000
      000000000000100040000000000643e58000001c7000009c40000006442903750000000001eeb
      000000000d020cff3e58000000020000000d0000000002bc5528f8d4000000000000000000000
      0000000000098fe
      **- Possible Inverter serial QAL0CG90DU

    • Inverter serial not recognised - using inverter type default**

    • Growatt new layout processing

      • decrypt : True
      • offset : 6
      • record layout : T06NNNNX
    • Grott data record date/time processing started

    • date-time: 2024-09-07T16:24:13

    • Grott values retrieved:

      • datalogserial : GZL0DA75E6
      • pvserial : QAL0CG90DU
      • pvstatus : 1
      • pvpowerin : 2148.1
      • pv1voltage : 281.2
      • pv1current : 4.9
      • pv1watt : 1377.8
      • pv2voltage : 285.3
      • pv2current : 2.7
      • pv2watt : 770.3
      • pvpowerout : 1934.9
      • pvfrequentie : 50.0
      • pvgridvoltage : 230.2
      • pvgridcurrent : 2.8
      • pvgridpower : 644.5
      • pvgridvoltage2 : 231.5
      • pvgridcurrent2 : 2.7
      • pvgridpower2 : 625.0
      • pvgridvoltage3 : 228.8
      • pvgridcurrent3 : 2.7
      • pvgridpower3 : 617.7
      • totworktime : 5771.0
      • pvenergytoday : 19.6
      • pvenergytotal : 8875.9
      • epvtotal : 9301.5
      • epv1today : 12.8
      • epv1total : 5110.9
      • epv2today : 11.2
      • epv2total : 4190.6
      • pvtemperature : 35.1
      • pvipmtemperature : 41.6
    • MQTT jsonmsg:
      {"device": "QAL0CG90DU", "time": "2024-09-07T16:24:13", "buffered": "no",
      "values": {"datalogserial": "GZL0DA75E6", "pvserial": "QAL0CG90DU",
      "pvstatus": 1, "pvpowerin": 21481, "pv1voltage": 2812, "pv1current": 49,
      "pv1watt": 13778, "pv2voltage": 2853, "pv2current": 27, "pv2watt": 7703,
      "pvpowerout": 19349, "pvfrequentie": 4995, "pvgridvoltage": 2302,
      "pvgridcurrent": 28, "pvgridpower": 6445, "pvgridvoltage2": 2315,
      "pvgridcurrent2": 27, "pvgridpower2": 6250, "pvgridvoltage3": 2288,
      "pvgridcurrent3": 27, "pvgridpower3": 6177, "totworktime": 41551446,
      "pvenergytoday": 196, "pvenergytotal": 88759, "epvtotal": 93015,
      "epv1today": 128, "epv1total": 51109, "epv2today": 112, "epv2total": 41906,
      "pvtemperature": 351, "pvipmtemperature": 416}}

    • Grott MQTT topic used : energy/growatt

    • MQTT message message sent

    • Grott Send data to PVOutput disabled

    • Grott Send data to Influx disabled

    • Grott extension processing disabled

`

System
HomeAssistant on a Synology as docker
grott via HACS
grott custom components from muppet (https://github.com/muppet3000/homeassistant-grott)

do you need any more info?

@typxxi
Copy link

typxxi commented Sep 8, 2024

even though I think that I had read somewhere that the parameters for the inverter mapping should be uppercase I suggest to give "tl-3" a try and then to setup a real grott installation in parallel on a pi 3 or what soever.

You then have to reconfigure the datalogger stick to the ip of the pi 3 with grott (Pi OS)
And then you should be able to get the sensor data from that machine and we would need to compare the logs if the behaviour is still the same or not.

I am expecting the same behaviour cause afaik egguy is not dealing with the decoding template or however they are called. He is simply converting GROTT into an HA Addon and he is not developing his own templates.

If you can show that the grott installation would behave the same then it would be Johans job to look a bit closer. RIght now the ball has been played to egguy but I guess you would get a faster solution with a basic GROTT setup cause then Johan would support you.

VM or another PC or a small pi is enough to run grott, even Pi 2 should be capable if I remember right my beginnings with grott a year ago.

@typxxi
Copy link

typxxi commented Sep 9, 2024

I have called a friend of mine who has had such issues last year before the next grott stable release had been released and when a lot of templates were missing like min 4600 or so.

He said that he got that running with a grott setup from scratch on an old Pi 2 or so.
Back then he had been guided by Johan Meier and everything was fine within hours or so.
Many months later and when I had already migrated to HA he finally migrated to egguys AddOn too in may or june.

@egguy
Copy link
Owner

egguy commented Sep 10, 2024

I will generate a new build with the new JSON layout. I will keep you updated.

Sorry for the delayed response I'm in vacation

@typxxi
Copy link

typxxi commented Sep 11, 2024

Thanks and enjoy the holidays - as we can offer rain and sunshine, wind, clouds and temps from 15 to 30° changing from day to day.

@typxxi
Copy link

typxxi commented Sep 15, 2024

Could you let us more about what went wrong or why it is different (or the same) compared to grott standalone ?

What does new json layout mean, a developement by you or simply upgrading what JOhan had called a template or so ?

thanks

@egguy
Copy link
Owner

egguy commented Sep 16, 2024

The difference is mostly a size optimisation, there is no difference between the code of grott standalone and the addon version.

I was only copying the original source code without the extra in the container to make it smaller (the .py files).

Grott has the ability to load extra inverter layout (mapping of content of packet to values) from JSON files, but I wasn't including it as my assumption all the layouts were already included in the python code.

Some inverters now, like the MOD, are supported by layout defined in the JSON files, e.g johanmeijer/grott@3fa7ef9

I just need to include the file during the build process

@schlidda83
Copy link
Author

alright, thanks @egguy please let us know when we can test it :)

@typxxi
Copy link

typxxi commented Sep 16, 2024

Grott has the ability to load extra inverter layout (mapping of content of packet to values) from JSON files, but I wasn't including it as my assumption all the layouts were already included in the python code.

Some inverters now, like the MOD, are supported by layout defined in the JSON files, e.g johanmeijer/grott@3fa7ef9

ah, and that was a very long ahhhhhh
that I can understand the mystery which also could have been found out by setting up - as I had recommanded - a dedicated pi grott server to solve the question if that is caused by grott or grott ha addon.

Thanks a lot for solving and explaining the details.
I have not yet read johan meiers layout defined json files topic but I guess it becomes more important and could be good to know as I have so many and also different models, just got another SPH4000 and SPH 4600, both used for a few months.

Thanks

@typxxi
Copy link

typxxi commented Sep 17, 2024

Some inverters now, like the MOD, are supported by layout defined in the JSON files, e.g johanmeijer/grott@3fa7ef9

I just need to include the file during the build process

OK,
I have looked for the file , which was in the root directory for whatever reason, while a lot of others can be found here under examples and then Record Layout

I assume that these "inverter model layout" config files listed here are required by grott and that the missing MOD file or maybe the latest version of the MOD file was missing.

I do not have that mod or TL3 inverter, but for sure good to know how things work together cause I had seen different of these layouts in the log which can look very different in the look based on the functioniality of the inverter.

Let me know if I am wrong - and yes , I have not forgotten to help you in 2025 with the documentation parts. That's why I am asking cause still grott can be a big guess work at least for me for example when I had lost one inverter after the other in the past 3 weeks simply due to maintenance during daylight which then "calls the Growatt Cloud back into action" and overwrote my IP adresses again, but only 1 inverter at a time, not all or just some. So far I had only seen that I lost 1 after reboot and usually a different one than before, therefore my assumptions that the growatt cloud empire strikes back.
Screenshot of the other layour records.

image

Final question: where is grott addon HA stored on a HA OS system ?
I can not find the grott.ini file or the one that is used cause those I had found were grott.ini with a size of 0
They were empty. But I did not find anything , no grott directory with files.

@egguy egguy mentioned this issue Sep 29, 2024
@egguy
Copy link
Owner

egguy commented Sep 30, 2024

Hi @schlidda83 I have finally released the add-on with layout on the edge branch: https://github.com/egguy/ha-addons-edge/

You can add the edge repository, stop the stable release, copy your config over to test, and start the edge version.

In case of success, you should see in the log the mention of :

  • T065020
  • T06NNNNXMOD

If you could confirm me everything is working as intented. I will promote this to the stable release

@egguy
Copy link
Owner

egguy commented Sep 30, 2024

Final question: where is grott addon HA stored on a HA OS system ?

If i'm not mistaken, the add-on run in its container. You don't have direct access. I think you can have a better overview by using the portainer add-on

The docker container then mount a custom folder : https://developers.home-assistant.io/docs/add-ons/configuration#add-on-configuration to store the addon configuration. This is where I store the grott.ini (empty by default) you can modify.

I assume that these "inverter model layout" config files listed here are required by grott and that the missing MOD file or maybe the latest version of the MOD file was missing.

Yes and not. Some layouts are defined in the code (like the TL3, see grottconf.py: https://github.com/johanmeijer/grott/blob/Master/grottconf.py#L1007) so they are already included. Other like the MOD are not defined in the code, they are loaded from the JSON files at the start if they are present in the current directy where grott run.

@schlidda83
Copy link
Author

schlidda83 commented Sep 30, 2024

@egguy first thanks for your support!
It seems to be working,

what is missing:
State of charge
Export to grid today

Log:
`- Grott MQTT topic used : energy/growatt
- MQTT message message sent
- Grott Send data to PVOutput disabled
- Grott Send data to Influx disabled
- Grott extension processing disabled

 - Growatt packet received:
	  <socket.socket fd=4, family=2, type=1, proto=0, laddr=('172.30.33.2', 41402), raddr=('47.254.130.145', 5279)>
 - Growatt original Data:
	 \x02\x58\x00\x06\x01\x0e\x01\x20\x00\x28\x23\x47\x25\x35\x43\x72\x37\x59\x77
	 \x61\x74\x74\x47\x72\x6f\x77\x61\x74\x74\x47\x72\x6f\x77\x61\x74\x74\x47\x72
	 \x3e\x36\x2d\x44\x37\x00\x4b\x5f\x33\x34\x74\x74\x47\x72\x6f\x77\x61\x74\x74
	 \x47\x72\x6f\x77\x61\x74\x74\x47\x72\x6f\x77\x79\x7d\x6a\x55\x5e\x4c\x77\xa9
	 \x74\x74\x47\xf4\x6f\x77\x69\x9b\x74\x47\x7a\x85\x77\x61\x7c\x9a\x47\x72\x6f
	 \x78\x61\x74\x74\x5e\x72\x6f\x77\x6f\x8b\x8b\xba\xc9\x6f\x77\x69\x26\x8b\xb8
	 \x85\x2f\x77\x61\x79\xe2\x47\x72\x79\xfa\x61\x74\x79\x6c\x8d\x90\x83\xbd\x8b
	 \x8b\xaa\xbd\x90\x88\x96\x20\x8b\xb8\x8d\x38\x77\x61\x75\x39\xb8\x8d\x92\x1e
	 \x9e\x8b\x89\x0a\x72\x6f\x45\xd0\x8b\x8b\x9e\x3d\x90\x88\x9e\x96\x74\x47\x73
	 \x9c\x77\x61\x7b\x01\x47\x72\x60\x03\x61\x74\x7b\x3e\x72\x6f\x71\x1d\x74\x74
	 \x58\x5c\x6f\x77\x61\x74\x74\x47\x56\x8a\x77\x61\x40\xce\x47\x72\x4a\xdd\x61
	 \x74\x50\xa2\x72\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\x72\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\x72\x6f\x77\x61\x74\x74\x47\x72\xd2\x0f
 - Grott automatic protocol detection
 - Grott data record length 278
 - layout   :  T060120
 - Record layout used :  T060120
 - Growatt data decrypted V2
 - Grott Growatt data decrypted
 - Growatt plain data:
	 02580006010e0120475a4c3044413735453600000000000000000000000000000000000000005
	 1414c30434739304455000000000000000000000000000000000000000018091e122c2300c800
	 000086000008ef000008ea000008ee0000000f000000190000000efffffdbb00000852fffff74
	 000000d960000168d00000d2bfffff4dcffffedcffffff754ffffff570000014dfffffd69ffff
	 fd4d000032b1ffffd94fffffffe2000001f300000f7500000f7400000f790000067c00001f2e0
	 0000000000024e5000034ba000025aa000024e500000000000000000000000000000000000000
	 00000000000000000000000000000000000000000000000000000000000000000000000000000
	 0000000000000bd78
 - Growatt new layout processing
	 - decrypt       :  True
	 - offset        :  6
	 - record layout :  T060120

 - Grott data record date/time processing started
 - date-time:  2024-09-30T18:44:35
 - Grott values retrieved:
	 -  datalogserial        :  GZL0DA75E6
	 -  pvserial             :  QAL0CG90DU
	 -  voltage_l1           :  228.7
	 -  voltage_l2           :  228.2
	 -  voltage_l3           :  228.6
	 -  Current_l1           :  1.5
	 -  Current_l2           :  2.5
	 -  Current_l3           :  1.4
	 -  act_power_l1         :  -58.1
	 -  act_power_l2         :  213.0
	 -  act_power_l3         :  -224.0
	 -  app_power_l1         :  347.8
	 -  app_power_l2         :  577.3
	 -  app_power_l3         :  337.1
	 -  react_power_l1       :  -285.2
	 -  react_power_l2       :  -465.7
	 -  react_power_l3       :  -222.0
	 -  powerfactor_l1       :  -0.2
	 -  powerfactor_l2       :  0.3
	 -  powerfactor_l3       :  -0.7
	 -  pos_rev_act_power    :  -69.1
	 -  pos_act_power        :  -69.1
	 -  rev_act_power        :  -69.1
	 -  app_power            :  1297.7
	 -  react_power          :  -990.5
	 -  powerfactor          :  -0.0
	 -  frequency            :  49.9
	 -  L1-2_voltage         :  395.7
	 -  L2-3_voltage         :  395.6
	 -  L3-1_voltage         :  396.1
	 -  pos_act_energy       :  166.0
	 -  rev_act_energy       :  798.2
 - MQTT jsonmsg: 
		 {"device": "GZL0DA75E6", "time": "2024-09-30T18:44:35", "buffered": "no",
		 "values": {"datalogserial": "GZL0DA75E6", "pvserial": "QAL0CG90DU",
		 "voltage_l1": 2287, "voltage_l2": 2282, "voltage_l3": 2286, "Current_l1":
		 15, "Current_l2": 25, "Current_l3": 14, "act_power_l1": -581,
		 "act_power_l2": 2130, "act_power_l3": -2240, "app_power_l1": 3478,
		 "app_power_l2": 5773, "app_power_l3": 3371, "react_power_l1": -2852,
		 "react_power_l2": -4657, "react_power_l3": -2220, "powerfactor_l1": -169,
		 "powerfactor_l2": 333, "powerfactor_l3": -663, "pos_rev_act_power": -691,
		 "pos_act_power": -691, "rev_act_power": -691, "app_power": 12977,
		 "react_power": -9905, "powerfactor": -30, "frequency": 499, "L1-2_voltage":
		 3957, "L2-3_voltage": 3956, "L3-1_voltage": 3961, "pos_act_energy": 1660,
		 "rev_act_energy": 7982}}
 - Grott MQTT topic used : energy/growatt
 - MQTT message message sent
 - Grott Send data to PVOutput disabled 
 - Grott Send data to Influx disabled 
 - Grott extension processing disabled 

 - Growatt packet received:
	  <socket.socket fd=5, family=2, type=1, proto=0, laddr=('172.30.33.2', 5279), raddr=('10.190.4.92', 45948)>
 - Data less then minimum record length, data not processed`

log2
- ibb : 3.0 - illc : 3.0 - tempa : 36.9 - tempb : 0.0 - pdischr : 909.0 - pchr : 0.0 - pchrxxxl : 0 - edischrtotalstor : 281.8 - echrtotalstor : 286.8 - bdc1flag : 3 - vbus2low : 257.6 - bmsmaxvoltcellno : 15 - bmsminvoltcellno : 25 - bmsbatteryavgtemp : 0 - bmsmaxcelltemp : 26.9 - bmsbatteryavgtemp2 : 25.0 - bmsmaxcelltemp2 : 2 - bmsbatteryavgtemp3 : 12 - bmsmaxsoc : 0 - bmsminsoc : 0 - parallelbatterynum : 1 - bmsderatereason : 0 - bmsgaugefcc(ah) : 50 - bmsgaugerm(ah) : 50 - bmserror : 0 - bmswarn : 0 - bmsfault : 0 - bmsfault2 : 0 - batisostatus : 0 - battneedchargerequestflag : 0 - bmsstatus : 2 - bmserror2 : 0 - bmswarn2 : 0 - bmssoc : 35 - bmsbatteryvolt : 156.2 - bmsbatterycurr : -5.8 - bmsbatterytemp : 43.0 - bmsmaxcurr : 25.0 - bmsmaxdischrcurr : 25.0 - bmscyclecnt : 0 - bmssoh : 100 - bmschargevoltlimit : 170.4 - bmsdischargevoltlimit : 14160 - bmswarn3 : 0 - bmserror3 : 0 - bmssinglevoltmax : 3261 - bmssinglevoltmin : 3255 - batloadvolt : 156.2 - MQTT jsonmsg: {"device": "QAL0CG90DU", "time": "2024-09-30T18:51:54", "buffered": "no", "values": {"datalogserial": "GZL0DA75E6", "pvserial": "QAL0CG90DU", "pvstatus": 1, "pvpowerin": 0, "pv1voltage": 957, "pv1current": 0, "pv1watt": 0, "pv2voltage": 835, "pv2current": 0, "pv2watt": 0, "pv3voltage": 0, "pv3current": 0, "pv3watt": 0, "pv4voltage": 0, "pv4current": 0, "pv4watt": 0, "pvpowerout": 9300, "qac": 63, "pac": 9064, "pvfrequency": 5000, "pvgridvoltage": 2287, "pvgridcurrent": 14, "pvgridpower": 3201, "pvgridvoltage2": 2298, "pvgridcurrent2": 14, "pvgridpower2": 3217, "pvgridvoltage3": 2273, "pvgridcurrent3": 13, "pvgridpower3": 2954, "vacrs": 3968, "vacst": 3945, "vactr": 3924, "ptousertotal": 0, "ptogridtotal": 0, "ptoloadtotal": 9300, "totworktime": 45520341, "eactoday": 112, "pvenergytoday": 112, "eactotal": 93031, "pvenergytotal": 93031, "epvtotal": 97513, "epv1today": 56, "epv1total": 53771, "epv2today": 59, "epv2total": 43742, "epv3today": 0, "epv3total": 0, "etousertoday": 9, "etousertotal": 329, "etogridtoday": 3, "etogridtotal": 6372, "eloadtoday": 125, "eloadtotal": 91420, "epv4today": 0, "epv4total": 0, "epvtoday": 115, "deratingmode": 0, "iso": -6, "dcir": 154, "dcis": 2006, "dcit": 2249, "gfci": 1, "busvoltage": 6265, "pvtemperature": 309, "pvimptemperature": 473, "boosttemperature": 283, "temp4": 0, "comboardtemperature": 353, "pbusvoltage": 3142, "nbusvoltage": 3121, "ipf": 20000, "realoppercent": 12, "opfullwatt": 70000, "standbyflag": 0, "faultmaincode": 0, "warnmaincode": 0, "faultsubcode": 0, "warnsubcode": 0, "uwpresentfftvaxxxlue[channela]": 0, "bafcistatus": 0, "uwstrength[channela]": 0, "uwselfcheckvalue[channela]": 0, "invstartdelaytime": 60, "bdconoffstate": 1, "drycontactstate": 0, "pself": 9300, "esystoday": 119, "edischrtoday": 68, "edischrtotal": 2818, "echrtoday": 64, "echrtotal": 2868, "eacchrtoday": 0, "eacchrtotal": 1, "esystotal": 98552, "eselftoday": 116, "eselftotal": 92179, "reserved3143": 0, "priority": 0, "epsfac": 0, "epsvac1": 0, "epsiac1": 0, "epspac1": 0, "epsvac2": 0, "epsiac2": 0, "epspac2": 0, "epsvac3": 0, "epsiac3": 0, "epspac3": 0, "epspac": 0, "loadpercent": 0, "pf": 10000, "dcv": 0, "newbdcflag": 0, "bdcderatingmode": 0, "sysstatemode": 513, "faultcode": 0, "warncode": 0, "vbat": 15619, "ibat": 58, "soc": 35, "vbus1": 6261, "vbus2": 3685, "ibb": 30, "illc": 30, "tempa": 369, "tempb": 0, "pdischr": 9090, "pchr": 0, "pchrxxxl": 0, "edischrtotalstor": 2818, "echrtotalstor": 2868, "bdc1flag": 3, "vbus2low": 2576, "bmsmaxvoltcellno": 15, "bmsminvoltcellno": 25, "bmsbatteryavgtemp": 0, "bmsmaxcelltemp": 269, "bmsbatteryavgtemp2": 250, "bmsmaxcelltemp2": 2, "bmsbatteryavgtemp3": 12, "bmsmaxsoc": 0, "bmsminsoc": 0, "parallelbatterynum": 1, "bmsderatereason": 0, "bmsgaugefcc(ah)": 50, "bmsgaugerm(ah)": 50, "bmserror": 0, "bmswarn": 0, "bmsfault": 0, "bmsfault2": 0, "batisostatus": 0, "battneedchargerequestflag": 0, "bmsstatus": 2, "bmserror2": 0, "bmswarn2": 0, "bmssoc": 35, "bmsbatteryvolt": 15620, "bmsbatterycurr": -580, "bmsbatterytemp": 430, "bmsmaxcurr": 2500, "bmsmaxdischrcurr": 2500, "bmscyclecnt": 0, "bmssoh": 100, "bmschargevoltlimit": 17040, "bmsdischargevoltlimit": 14160, "bmswarn3": 0, "bmserror3": 0, "bmssinglevoltmax": 3261, "bmssinglevoltmin": 3255, "batloadvolt": 15620}} - Grott MQTT topic used : energy/growatt - MQTT message message sent - Grott Send data to PVOutput disabled - Grott Send data to Influx disabled - Grott extension processing disabled

image
image

image

image

is the config good enough?

@egguy
Copy link
Owner

egguy commented Oct 3, 2024

The config should be good enough.

One weird thing is the packet you show as an example is shorter than expected, this makes grott use the generic layout instead of the specific one. The returned value seems to make sense.

Copy link

github-actions bot commented Nov 3, 2024

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Nov 3, 2024
@schlidda83
Copy link
Author

Hi @egguy
i have seen that the standard growatt server addon is receiving a lot of more information. how can that be?

@github-actions github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Nov 4, 2024
@egguy
Copy link
Owner

egguy commented Nov 8, 2024

Hi @schlidda83, what is the do you mean by the growatt server add-on?

I need to take a look if the MOD series is not part of the new beta branch of grott. This could explain why it is only giving a limited set of informations.

@schlidda83
Copy link
Author

schlidda83 commented Nov 8, 2024

Hi @egguy

https://www.home-assistant.io/integrations/growatt_server

it is the "official plugin" which provides data from the inverter approx every 15min.

image

image

image

@FlexxFR
Copy link

FlexxFR commented Dec 8, 2024

Hi @egguy , I'm hitting the same issue here with a MOD 8000TL3-XH invertor. All strange values.
I all have latest (regular) versions installed, tried to use the parameter tl3, TL3, min, MIN, mod, MOD, but nothing works.
(Or better, diagnostic values are okay, sensor values give weird numbers)

Reading the comments above, I'm not sure what to do. Do I need to install another version (-edge?)
And then use the MOD as type?

[EDIT]
Tried it anyways and it improves the values a lot. Not all are correct but power/energy seems to be correct.
Grid Frequency, Inverter Output Current / Power phase 1, 2, 3 all wrong.
Is this to be solved in this add-on or by Grott "interpreters" ?

Final question:
Is it okay to stay on edge version or a you planning to include this in the master some day?

Copy link

github-actions bot commented Jan 8, 2025

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale There has not been activity on this issue or PR for quite some time.
Projects
None yet
Development

No branches or pull requests

4 participants