Hiya, wonder if anybody is having issues with givtcp2
i have set up my HA and installed the broker with local user and then GIVTCP
However it juts always fails to connect. i can access my GivEnergy locally so i know its there haha and it also exports to the invertor app every 10 secs so i know the data is there. here is my log. if anybody can shed any lite that would be great. i have tried it as a AIO and also using the old firmware toggle
2024-04-01 14:07:53,316 - startup - [CRITICAL] - HA MQTT Service has been found at core-mosquitto
2024-04-01 14:07:53,337 - startup - [INFO] - Supervisor Timezone: Europe/London
2024-04-01 14:07:55,365 - startup - [CRITICAL] - Scanning network for GivEnergy Devices…
2024-04-01 14:07:59,529 - startup - [CRITICAL] - Inverter CE####### which is a Gen 1 - AC has been found at: 10.0.0.14
2024-04-01 14:07:59,531 - startup - [INFO] - Searching for Inverters again
2024-04-01 14:07:59,547 - startup - [CRITICAL] - Running Redis
2024-04-01 14:07:59,566 - startup - [CRITICAL] - Setting up invertor: 1 of 1
2024/04/01 14:07:59 [notice] 69#69: using the “epoll” event method
2024/04/01 14:07:59 [notice] 69#69: nginx/1.20.2
2024/04/01 14:07:59 [notice] 69#69: OS: Linux 6.1.73-haos-raspi
2024/04/01 14:07:59 [notice] 69#69: getrlimit(RLIMIT_NOFILE): 1073741816:1073741816
2024/04/01 14:07:59 [notice] 69#69: start worker processes
2024/04/01 14:07:59 [notice] 69#69: start worker process 74
2024/04/01 14:07:59 [notice] 69#69: start worker process 75
2024/04/01 14:07:59 [notice] 69#69: start worker process 76
2024/04/01 14:07:59 [notice] 69#69: start worker process 77
2024-04-01 14:07:59,950 - startup - [CRITICAL] - Running RQ worker to queue and process givernergy-modbus calls
2024-04-01 14:07:59,951 - startup - [CRITICAL] - Running Invertor (10.0.0.14) read loop every 5s
2024-04-01 14:07:59,966 - startup - [CRITICAL] - Subscribing MQTT Broker for control
2024-04-01 14:07:59,981 - startup - [CRITICAL] - Starting Gunicorn on port 6345
[2024-04-01 14:08:01 +0100] [81] [INFO] Starting gunicorn 21.2.0
[2024-04-01 14:08:01 +0100] [81] [INFO] Listening at: http://0.0.0.0:6345 (81)
[2024-04-01 14:08:01 +0100] [81] [INFO] Using worker: sync
[2024-04-01 14:08:01 +0100] [82] [INFO] Booting worker with pid: 82
[2024-04-01 14:08:01 +0100] [83] [INFO] Booting worker with pid: 83
[2024-04-01 14:08:01 +0100] [84] [INFO] Booting worker with pid: 84
2024-04-01 14:08:05,304 - Inv1 - mqtt_client - [CRITICAL] - Connecting to MQTT broker for control- core-mosquitto
2024-04-01 14:08:12,020 - Inv1 - read - [ERROR ] - 10 failed inverter reads in a row so removing regCache to force update…
2024-04-01 14:09:45,458 - Inv1 - mqtt_client - [ERROR ] - No serial_number found in MQTT queue. MQTT Control not available.
Traceback (most recent call last):
File “/app/GivTCP_1/mqtt_client.py”, line 402, in
client.loop_forever()
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 1756, in loop_forever
rc = self._loop(timeout)
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 1164, in _loop
rc = self.loop_read()
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 1556, in loop_read
rc = self._packet_read()
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 2439, in _packet_read
rc = self._packet_handle()
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 3039, in _packet_handle
return self._handle_connack()
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 3138, in _handle_connack
on_connect(
File “/app/GivTCP_1/mqtt_client.py”, line 386, in on_connect
client.subscribe(MQTT_Topic+“/control/”+GiV_Settings.serial_number+“/#”)
AttributeError: type object ‘GiV_Settings’ has no attribute ‘serial_number’
2024-04-01 14:10:21,902 - Inv1 - read - [ERROR ] - 10 failed inverter reads in a row so removing regCache to force update…
2024-04-01 14:12:36,452 - Inv1 - read - [ERROR ] - 10 failed inverter reads in a row so removing regCache to force
Not providing an answer here, only saying I have exactly the same issue and it occured about the same time as your post.
I also tried toggling the ‘old firmware’ and AIO options in different combinations but that didn’t work either.
I wondered if the IP had changed so it was looking in the wrong direction but that doesn’t seem to have changed.
I hope someone more savvy than us has found a solution!
Same here. I’m using version 2.4.3 if anyones interested and my logs are looking almost identical to this.
It correctly finds the inverters (gateway and AIO), and entered the correct IP (which is reserved n DHCP) plus it can locate core-mosquitto
I’ve tried all combinations but I would have though the correct config is enabling “Is it an AIO?” and disabling “Is it an old firmware?”. None of it works anyway.
Just dropping in to this thread to say “same here”! I’m setting up GivTCP for the first time but I’m generally savvy at such things and have triple checked everything. Has anyone had any joy?
I had a very similar issue with my givtcp/ha setup and at least for me the answer was in the givtcp addon config.
Go into your config and make sure you have the I had a very similar issue with my givtcp/ha setup and at least for me the answer was in the givtcp adding config.
Go into your config and make sure you have the following
Number of inverters 1
Ip for your AIO
Number of batteries 0
Is inverter AIO toggle right for blue
Is inverter on old firmware leave left for off (if you know your firmware is upto date)
This is only applicable if you have the AIO though.
Hope this helps someone
Ah amazing - It was the “Number of batteries 0” that caught me out, I had that set to 1 because the AIO has a battery… changed it to 0 and it looks to be working now. Thank you!
My connection dropped last night, which means that the “charge overnight” commands didn’t get through. Restarted the addon many times this morning, and toggled old firmware and tried in each setting.
Still giving the same error - it’s worked flawlessly for months on end.
Single battery on an AC inverter, so not an AIO thing.
Turns out resetting the inverter, which didn’t change any settings… was enough to kick it back into life.
Tried removig pkl files, reinstalling the add on … but no, resetting (from the GE cloud portal) rather than just restarting the inverter was what it took.
PS - I added tcpdump, but am still not seeing any traffic - yep, terminal runs in it’s own container
Confession: I found a solution to my previous post and did not reply with it (didn’t have a static IP and the digits looked very similar on first glance (think 66 vs 56). Sorted pretty quickly after that.
I actually then had the same symptoms and went to look again but no IP issue. Searched online with the logs and found this thread again, now more populated. While I don’t have AIO, when looking at the battery suggestion (mentioned by tvns) I fould that a recent update must have changed my battery numbers from previous. I have one battery and one inverter but under the “Inverter 2 - How many connected batteries?” and “Inverter 3 - How many connected batteries?” a “1” had appeared. I deleted these, saved the config and restarted it and all is good in the world.
