GivTCP just stopped working and no idea what to do

5 comments started 2024-02-21 last 2024-02-22
GivEnergy ProductsAC Coupled
P
#1 pacemaker

Hi all

Hoping for some help. GivTCP is no longer connecting to my AC3 inverter. It just ... stopped and I am at a total loss as to what to do. The inverter IP is correct, I haven't touched any settings but it refuses to connect. I've tried stopping the MQTT service and GivTCP service, restarting (MQTT first), but no luck. The app will connect locally but won't return any stats from the inverter.

Some logs:

2024-02-21 12:23:05,575 - startup - [CRITICAL] - HA MQTT Service has been found at core-mosquitto
2024-02-21 12:23:05,594 - startup - [INFO] - Supervisor Timezone: Europe/London
2024-02-21 12:23:07,619 - startup - [CRITICAL] - Scanning network for GivEnergy Devices...
2024-02-21 12:23:14,699 - pymodbus.client.sync - [ERROR] - Connection to (192.168.68.71, 8899) failed: timed out
2024-02-21 12:23:14,700 - startup - [ERROR] - Gathering inverter details for 192.168.68.71 failed.
2024-02-21 12:23:14,701 - startup - [ERROR] - Unable to interrogate inverter to get base details
2024-02-21 12:23:16,705 - pymodbus.client.sync - [ERROR] - Connection to (192.168.68.71, 8899) failed: timed out
2024-02-21 12:23:16,705 - startup - [ERROR] - Gathering inverter details for 192.168.68.71 failed.
2024-02-21 12:23:16,706 - startup - [ERROR] - Unable to interrogate inverter to get base details
2024-02-21 12:23:16,707 - startup - [INFO] - Searching for Inverters again
2024-02-21 12:23:16,708 - startup - [CRITICAL] - Scanning network for GivEnergy Devices...
2024-02-21 12:23:21,853 - startup - [CRITICAL] - No inverters found...
2024-02-21 12:23:21,853 - startup - [INFO] - Searching for Inverters again
2024-02-21 12:23:21,854 - startup - [CRITICAL] - Scanning network for GivEnergy Devices...
2024-02-21 12:23:26,952 - startup - [CRITICAL] - No inverters found...
2024-02-21 12:23:26,961 - startup - [CRITICAL] - Running Redis
2024-02-21 12:23:26,972 - startup - [CRITICAL] - Setting up invertor: 1 of 1
2024/02/21 12:23:26 [notice] 249#249: using the "epoll" event method
2024/02/21 12:23:26 [notice] 249#249: nginx/1.20.2
2024/02/21 12:23:26 [notice] 249#249: OS: Linux 6.1.74-haos
2024/02/21 12:23:26 [notice] 249#249: getrlimit(RLIMIT_NOFILE): 1073741816:1073741816
2024/02/21 12:23:26 [notice] 249#249: start worker processes
2024/02/21 12:23:26 [notice] 249#249: start worker process 254
2024/02/21 12:23:26 [notice] 249#249: start worker process 255
2024/02/21 12:23:26 [notice] 249#249: start worker process 256
2024/02/21 12:23:26 [notice] 249#249: start worker process 257
2024-02-21 12:23:27,090 - startup - [CRITICAL] - Running RQ worker to queue and process givernergy-modbus calls
2024-02-21 12:23:27,091 - startup - [CRITICAL] - Running Invertor (192.168.68.71) read loop every 5s
2024-02-21 12:23:27,101 - startup - [CRITICAL] - Subscribing MQTT Broker for control
2024-02-21 12:23:27,112 - startup - [CRITICAL] - Starting Gunicorn on port 6345
[2024-02-21 12:23:28 +0000] [261] [INFO] Starting gunicorn 21.2.0
[2024-02-21 12:23:28 +0000] [261] [INFO] Listening at: http://0.0.0.0:6345 (261)
[2024-02-21 12:23:28 +0000] [261] [INFO] Using worker: sync
[2024-02-21 12:23:28 +0000] [262] [INFO] Booting worker with pid: 262
[2024-02-21 12:23:28 +0000] [263] [INFO] Booting worker with pid: 263
[2024-02-21 12:23:28 +0000] [264] [INFO] Booting worker with pid: 264
2024-02-21 12:23:31,059 - Inv1 - mqtt_client - [CRITICAL] - Connecting to MQTT broker for control- core-mosquitto
2024-02-21 12:23:33,611 - Inv1 - sync - [ERROR ] - Connection to (192.168.68.71, 8899) failed: timed out
2024-02-21 12:23:39,695 - Inv1 - sync - [ERROR ] - Connection to (192.168.68.71, 8899) failed: timed out
2024-02-21 12:23:42,200 - Inv1 - sync - [ERROR ] - Connection to (192.168.68.71, 8899) failed: timed out
2024-02-21 12:23:44,704 - Inv1 - sync - [ERROR ] - Connection to (192.168.68.71, 8899) failed: timed out
2024-02-21 12:23:47,209 - Inv1 - sync - [ERROR ] - Connection to (192.168.68.71, 8899) failed: timed out

Anyone any advice on what I might try next?

P
#2 pacemaker

Small update, it will sporadically connect - return some data, then disconnect for an indeterminate amount of time. Is there a way to reboot the inverter? Seems like its got some kind of issue...

G
#3 geoffreycoan

pacemaker You can reboot the inverter from the givenergy portal - its called ‘reset’

Or power it off and on again

P
#4 pacemaker

thanks - yeah I am going to try that in the morning. its 50/50 at the moment, at least its connecting now but dropping pings a lot of time

P
#5 pacemaker

I got to the bottom of it. The inverter was connecting to a mesh wifi device that was heavily utilised (bandwidth wise), as well as having a weak signal to its home mesh router. I've forced the GE inverter to connect to the home router instead which is hard wired to the network (and HA), and all the timeouts and weirdness in HA has disappeared.