grott_ha and MIN-TL-XH inverter

[shampeon]

I have a MIN-12000TL-XH inverter and ARO battery, and tried using the grott_ha component in my Docker container without success.

The error message is:

	[Grott HA] 0.0.7-rc6 Can't configure device: BGJ0B1202H
	 - Grott extension processing ended :  7

But I can see in the code that's just a catch all.

Any ideas why it fails?

Grott settings:
:
	version:     	 2.6.1g
	verbose:     	 True
	trace:       	 False
	config file: 	 grott.ini
	minrecl:     	 100
	decrypt:     	 True
	compat:      	 False
	invtype:     	 default
	include_all: 	 False
	blockcmd:    	 False
	noipf:       	 False
	time:        	 auto
	sendbuf:     	 True
	timezone:    	 local
	valueoffset: 	 6
	offset:      	 6
	inverterid:  	 automatic
	mode:        	 proxy
	grottip      	 default
	grottport    	 5279
_MQTT:
	nomqtt       	 False
	mqttip:      	 172.17.0.1
	mqttport:    	 1883
	mqtttopic:   	 energy/growatt
	mqtttauth:   	 True
	mqttuser:    	 hass
	mqttpsw:     	 **secret**
_Growatt server:
	growattip:   	 47.251.35.20
	growattport: 	 5279
_PVOutput:
	pvoutput:    	 False
	pvurl:       	 https://pvoutput.org/service/r2/addstatus.jsp
	pvapikey:    	 yourapikey
	pvinverters: 	 1
	pvsystemid:  	 systemid1
_Influxdb:
	influx:      	 False
	influx2:     	 False
	database:    	 grottdb
	ip:          	 localhost
	port:        	 8086
	user:        	 grott
	password:    	 **secret**
	organization:	 grottorg
	bucket:      	 grottdb
	token:       	 **secret**
_Extension:
	extension:   	 True
	extname:     	 grott_ha
	extvar:      	 {'ha_mqtt_host': '172.17.0.1', 'ha_mqtt_port': '1883', 'ha_mqtt_user': 'hass', 'ha_mqtt_password': 'xxxxxxx'}
Grott proxy mode started
Hostname : bd0fec53f7c8
IP :  172.18.0.9 , port :  5279 
	 - ('192.168.0.140', 49162) has connected
	 - Growatt packet received:
		  <socket.socket fd=4, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('172.18.0.9', 55498), raddr=('47.251.35.20', 5279)>
	 - Data less then minimum record length, data not processed
	 - Growatt packet received:
		  <socket.socket fd=5, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('172.18.0.9', 5279), raddr=('192.168.0.140', 49162)>
	 - Data less then minimum record length, data not processed
	 - Growatt packet received:
		  <socket.socket fd=5, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('172.18.0.9', 5279), raddr=('192.168.0.140', 49162)>
	 - Data less then minimum record length, data not processed
	 - Growatt packet received:
		  <socket.socket fd=4, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('172.18.0.9', 55498), raddr=('47.251.35.20', 5279)>
	 - Growatt original Data:
snip
	 - 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:
snip
	 - Growatt new layout processing
		 - decrypt       :  True
		 - offset        :  6
		 - record layout :  T06NNNNX
	 - Grott data record date/time processing started
	 - date-time:  2023-04-11T17:02:45
	 - Grott values retrieved:
		 -  pvserial             :  BGJ0B1202H
		 -  recortype1           :  3000
		 -  recortype2           :  3124
		 -  pvstatus             :  1
		 -  pvpowerin            :  0.0
		 -  pv1voltage           :  0.0
		 -  pv1current           :  0.0
		 -  pv1watt              :  0.0
		 -  pv2voltage           :  0.0
		 -  pv2current           :  0.0
		 -  pv2watt              :  0.0
		 -  pvpowerout           :  -21.0
		 -  pvfrequentie         :  60.0
		 -  pvgridvoltage        :  246.1
		 -  pvgridcurrent        :  0.2
		 -  pvgridpower          :  24.8
		 -  pvgridvoltage2       :  0.0
		 -  pvgridcurrent2       :  0.0
		 -  pvgridpower2         :  0.0
		 -  pvgridvoltage3       :  0.0
		 -  pvgridcurrent3       :  0.0
		 -  pvgridpower3         :  0.0
		 -  totworktime          :  10017.8
		 -  pvenergytoday        :  0.1
		 -  pvenergytotal        :  474.3
		 -  epvtotal             :  2.4
		 -  epv1today            :  0.0
		 -  epv1total            :  0.6
		 -  epv2today            :  0.0
		 -  epv2total            :  0.2
		 -  pvtemperature        :  31.2
		 -  pvipmtemperature     :  39.6
	 - MQTT jsonmsg: 
			 {"device": "BGJ0B1202H", "time": "2023-04-11T17:02:45", "buffered": "no",
			 "values": {"recortype1": 3000, "recortype2": 3124, "pvstatus": 1,
			 "pvpowerin": 0, "pv1voltage": 0, "pv1current": 0, "pv1watt": 0,
			 "pv2voltage": 0, "pv2current": 0, "pv2watt": 0, "pvpowerout": -210,
			 "pvfrequentie": 5999, "pvgridvoltage": 2461, "pvgridcurrent": 2,
			 "pvgridpower": 248, "pvgridvoltage2": 0, "pvgridcurrent2": 0,
			 "pvgridpower2": 0, "pvgridvoltage3": 0, "pvgridcurrent3": 0, "pvgridpower3":
			 0, "totworktime": 72128255, "pvenergytoday": 1, "pvenergytotal": 4743,
			 "epvtotal": 24, "epv1today": 0, "epv1total": 6, "epv2today": 0, "epv2total":
			 2, "pvtemperature": 312, "pvipmtemperature": 396}}
	 - MQTT message message sent
	 - Grott Send data to PVOutput disabled 
	 - Grott Send data to Influx disabled 
	 - Grott extension processing started :  grott_ha
	[Grott HA] 0.0.7-rc6 Can't configure device: BGJ0B1202H
	 - Grott extension processing ended :  7

[shampeon]

I updated grott manually to use the T06NNNNXMIN.json config for my MIN inverter, as described in another thread.

I still am getting the grott_ha error, though.

[daath]

Sounds a bit like my experience for an unrealated problem - did you use

image: ledidobe/grottrpi:beta

and not

image: ledidobe/grottrpi

?

[shampeon]

Just ledidobe/grott since it's on my x64 home server.

[daath]

OK, not sure if you still need :beta or not ... For the rpi you seem to need it ... :)

[johanmeijer]

I would say use the beta version. That is an actual copy of the master from Github. I still have to change this is docker hub.

The min layout will also be added to the next docker beta image.

[daath]

Not sure where to put it, but in the grott_ha.py that I use:

    "p1charge1": {
        "name": "Battery charge",
        "device_class": "power",
        "unit_of_measurement": "kW",
        "state_class": "measurement",
        "icon": "mdi:battery-arrow-up",
    },

unit_of_measurement should be W and not kW - right now my GBLI6532 batteries looks like they are charging at 2995 kW :)