Docker / GivTCP / Window 10 Pro

Hi

Am struggling to get GivTCP to work with my AIO. Firmware: (D0.609-A0.609) Battery Firmware Version:7

Categorically the PC CAN talk to the inverter, ping, telnet and open port on 8899

Am using the command:

docker run --name GivTCP -d -p 6345:6345 -e OLD_FIRMWARE=True -e SERIAL_NUMBER=CHxxxxx -e MQTT_OUTPUT=False -e INVERTOR_IP_1=192.168.xxx.100 -e INVERTOR_AIO_1=True -e NUMINVERTORS=1 -e NUMBATTERIES_1=1 britkat/giv_tcp-ma

Docker starts, tried to detect inverters - fails but continues to

2024-01-02 23:10:57 2024-01-02 23:10:57,812 - startup - [CRITICAL] - Running Invertor (192.168.68.100) read loop every 5s

but after starting some workers settles down to:
2024-01-02 23:13:00 2024-01-02 23:13:00,397 - Inv1 - read - [ERROR ] - 10 failed inverter reads in a row so removing regCache to force update...

Am I hitting a firmware / givTCP issue? Is it windows?

Any guidance?
Thanks in advance

Try setting old firmware attribute to false?

You should have NUMBATTERIES_1=0 (not 1, GivTCP hasn't caught up with the AIO just yet). I also have INVERTOR_AC_1=False in my docker-compose, so you could try that too.

And personally I prefer to specify the version of GivTCP that I want to use (in my case britkat/giv_tcp-ma:2.4.3). I found version 2.2.4 was less fussy about options when I was trying to get it to work the first time.

PianSom this - number of batteries should be 0

Thanks for the feedback. Taking it on board I have amended the command to:

`docker run --name GivTCP -d -p 6345:6345 -e MQTT_OUTPUT=False -e INVERTOR_IP_1=192.168.xx.100 -e INVERTOR_AIO_1=True -e NUMINVERTORS=1 -e NUMBATTERIES_1=0 britkat/giv_tcp-ma:2.4.3

and also tried

docker run --name GivTCP -d -p 6345:6345 -e MQTT_OUTPUT=False -e INVERTOR_IP_1=192.168.xx.100 -e INVERTOR_AIO_1=True -e NUMINVERTORS=1 -e NUMBATTERIES_1=0 britkat/giv_tcp-ma

(obviously the correct IP in when I start)

This gets me further... so a step in the right direction - now the container starts and after:

2024-01-03 09:24:59 2024-01-03 09:24:59,497 - Inv1 - read - [CRITICAL] - First time running so saving AC Charge status

It just seems to hang - nothing further is logged .... it's so close yet...

Sorry to ask again but any further pointers? Or suggestions where to investigate?

Thanks

SnowDeer

That is normal and working. Now you need to add MQTT inside HomeAssistant and then under the MQTT integration you should see the inverter and battery entities created.

SnowDeer
Yup, almost certainly now in working mode. Logs will iirc next produce a generic output at midnight each day.

Congrats!

Arg0t
This person has MQTT_OUTPUT=False so it looks like they don't want to use it!