Cannot get local control to work on Home Assistant

3 comments started 2025-03-19 last 2025-03-19
Home AutomationHome Assistant
R
#1 RG

Been trying a few things now.

The situation:

  • Existing HA install (with many plugins and sensors) on HA 2025.3.3 and HaOS 15.0. It has 3 network interfaces.
  • New GiveEnergy 3-Phase Hybrid inverter GIV-3HY-11 on software DA0.007-DD0.007-A0.007 connected via wired ethernet.

I installed the GivTCP addon and started it. When I navigate to http://[ip]:8099 is see the portal. When I click on “next” the following error message appears below: “ Server Error: INTERNAL SERVER ERROR”. No inverters are found.

In the logs I see:
2025-03-19 11:01:16,727 - startup - [CRITICAL] - Scanning network for GivEnergy Devices...
2025-03-19 11:01:16,727 - startup - [DEBUG] - EVC- Scanning network (1):192.168.106.1
2025-03-19 11:01:17,944 - startup - [DEBUG] - EVC- Scanning network (2):192.168.106.1
2025-03-19 11:01:19,160 - startup - [DEBUG] - INV- Scanning network (1):192.168.106.1
2025-03-19 11:01:20,386 - startup - [DEBUG] - INV- Scanning network (2):192.168.106.1
2025-03-19 11:01:21,608 - startup - [CRITICAL] - No inverters found...
2025-03-19 11:01:21,608 - startup - [DEBUG] - EVC- Scanning network (1):192.168.107.1
2025-03-19 11:01:22,919 - startup - [DEBUG] - EVC- Scanning network (2):192.168.107.1
2025-03-19 11:01:24,228 - startup - [DEBUG] - INV- Scanning network (1):192.168.107.1
2025-03-19 11:01:25,539 - startup - [DEBUG] - 3 Inverters found on 192.168.107.1 - {1: '192.168.107.9', 2: '192.168.107.11', 3: '192.168.107.108'}
2025-03-19 11:01:25,539 - startup - [DEBUG] - Getting inverter stats for: 192.168.107.9
2025-03-19 11:01:27,543 - startup - [ERROR] - Gathering inverter details for 192.168.107.9 failed.
2025-03-19 11:01:27,543 - startup - [ERROR] - Unable to interrogate inverter to get base details
2025-03-19 11:01:29,551 - startup - [ERROR] - Gathering inverter details for 192.168.107.9 failed.
2025-03-19 11:01:29,551 - startup - [ERROR] - Unable to interrogate inverter to get base details
2025-03-19 11:01:29,551 - startup - [DEBUG] - Getting inverter stats for: 192.168.107.11
2025-03-19 11:01:31,556 - startup - [ERROR] - Gathering inverter details for 192.168.107.11 failed.
2025-03-19 11:01:31,556 - startup - [ERROR] - Unable to interrogate inverter to get base details
2025-03-19 11:01:33,559 - startup - [ERROR] - Gathering inverter details for 192.168.107.11 failed.
2025-03-19 11:01:33,559 - startup - [ERROR] - Unable to interrogate inverter to get base details
2025-03-19 11:01:33,559 - startup - [DEBUG] - Getting inverter stats for: 192.168.107.108
2025-03-19 11:01:33,717 - startup - [CRITICAL] - Inverter TC[SERIAL] which is a Gen 1 - Hybrid has been found at: 192.168.107.108
2025-03-19 11:01:33,718 - startup - [DEBUG] - EVC- Scanning network (1):192.168.14.1
2025-03-19 11:01:34,929 - startup - [DEBUG] - EVC- Scanning network (2):192.168.14.1
2025-03-19 11:01:36,140 - startup - [DEBUG] - 3 Inverters found on 192.168.14.1 - {1: '192.168.107.9', 2: '192.168.107.11', 3: '192.168.107.108'}
2025-03-19 11:01:36,140 - startup - [DEBUG] - Getting inverter stats for: 192.168.107.9
2025-03-19 11:01:38,146 - startup - [ERROR] - Gathering inverter details for 192.168.107.9 failed.
2025-03-19 11:01:38,146 - startup - [ERROR] - Unable to interrogate inverter to get base details
2025-03-19 11:01:40,151 - startup - [ERROR] - Gathering inverter details for 192.168.107.9 failed.
2025-03-19 11:01:40,151 - startup - [ERROR] - Unable to interrogate inverter to get base details
2025-03-19 11:01:40,151 - startup - [DEBUG] - Getting inverter stats for: 192.168.107.11
2025-03-19 11:01:42,156 - startup - [ERROR] - Gathering inverter details for 192.168.107.11 failed.
2025-03-19 11:01:42,157 - startup - [ERROR] - Unable to interrogate inverter to get base details
2025-03-19 11:01:44,161 - startup - [ERROR] - Gathering inverter details for 192.168.107.11 failed.
2025-03-19 11:01:44,162 - startup - [ERROR] - Unable to interrogate inverter to get base details
2025-03-19 11:01:44,162 - startup - [DEBUG] - Getting inverter stats for: 192.168.107.108
2025-03-19 11:01:44,317 - startup - [CRITICAL] - Inverter TC[SERIAL] which is a Gen 1 - Hybrid has been found at: 192.168.107.108
2025-03-19 11:01:44,318 - startup - [INFO] - Searching for Inverters again
2025-03-19 11:01:44,318 - startup - [DEBUG] - GivTCP isAddon: True
2025-03-19 11:01:44,318 - startup - [DEBUG] - Config directory already exists
2025-03-19 11:01:44,319 - startup - [CRITICAL] - Running Redis
2025-03-19 11:01:44,320 - startup - [CRITICAL] - Setting up invertor: 1 of 1
2025-03-19 11:01:44,335 - startup - [DEBUG] - Copying in a template settings.json
2025/03/19 11:01:44 [notice] 189#189: using the "epoll" event method
2025/03/19 11:01:44 [notice] 189#189: nginx/1.20.2
2025/03/19 11:01:44 [notice] 189#189: OS: Linux 6.12.18-haos
2025/03/19 11:01:44 [notice] 189#189: getrlimit(RLIMIT_NOFILE): 1073741816:1073741816
2025-03-19 11:01:44,336 - startup - [DEBUG] - Recreating settings.py for invertor 1
2025-03-19 11:01:44,337 - startup - [CRITICAL] - Running RQ worker to queue and process givernergy-modbus calls
2025-03-19 11:01:44,337 - startup - [CRITICAL] - Running Invertor () read loop every 15s
2025/03/19 11:01:44 [notice] 189#189: start worker processes
2025-03-19 11:01:44,338 - startup - [CRITICAL] - Subscribing MQTT Broker for control
2025/03/19 11:01:44 [notice] 189#189: start worker process 196
2025/03/19 11:01:44 [notice] 189#189: start worker process 197
2025-03-19 11:01:44,340 - startup - [CRITICAL] - Starting Gunicorn on port 6345
2025/03/19 11:01:44 [notice] 189#189: start worker process 199
2025/03/19 11:01:44 [notice] 189#189: start worker process 199
2025/03/19 11:01:44 [notice] 189#189: start worker process 200
[2025-03-19 11:01:44 +0100] [198] [INFO] Starting gunicorn 23.0.0
[2025-03-19 11:01:44 +0100] [198] [INFO] Listening at: http://0.0.0.0:6345 (198)
[2025-03-19 11:01:44 +0100] [198] [INFO] Using worker: sync
[2025-03-19 11:01:44 +0100] [201] [INFO] Booting worker with pid: 201
[2025-03-19 11:01:44 +0100] [204] [INFO] Booting worker with pid: 204
2025-03-19 11:01:44,652 - Inv1 - read - [DEBUG ] - ----------------------------Starting----------------------------
2025-03-19 11:01:44,653 - Inv1 - read - [DEBUG ] - Getting All Registers
2025-03-19 11:01:44,653 - Inv1 - read - [DEBUG ] - Connecting to:
2025-03-19 11:01:44,657 - Inv1 - queue - [DEBUG ] - Pushed job fdb01259-e731-451a-9be1-cbefa8ace40e into GivTCP_1
[2025-03-19 11:01:44 +0100] [206] [INFO] Booting worker with pid: 206
2025-03-19 11:01:44,828 - Inv1 - mqtt_client - [CRITICAL] - Connecting to MQTT broker for control- core-mosquitto
2025-03-19 11:01:44,831 - Inv1 - sync - [ERROR ] - Connection to (, 8899) failed: [Errno -2] Name does not resolve
2025-03-19 11:01:45,333 - Inv1 - sync - [ERROR ] - Connection to (, 8899) failed: [Errno -2] Name does not resolve
2025-03-19 11:01:45,834 - Inv1 - sync - [ERROR ] - Connection to (, 8899) failed: [Errno -2] Name does not resolve
2025-03-19 11:01:46,336 - Inv1 - sync - [ERROR ] - Connection to (, 8899) failed: [Errno -2] Name does not resolve
2025-03-19 11:01:46,838 - Inv1 - sync - [ERROR ] - Connection to (, 8899) failed: [Errno -2] Name does not resolve
2025-03-19 11:01:47,339 - Inv1 - sync - [ERROR ] - Connection to (, 8899) failed: [Errno -2] Name does not resolve
2025-03-19 11:01:47,926 - Inv1 - read - [DEBUG ] - ----------------------------Starting----------------------------
2025-03-19 11:01:47,927 - Inv1 - read - [DEBUG ] - Getting All Registers
2025-03-19 11:01:47,927 - Inv1 - read - [DEBUG ] - Connecting to:
2025-03-19 11:01:47,928 - Inv1 - queue - [DEBUG ] - Pushed job 45351421-a647-4e32-b6bd-321d33ada597 into GivTCP_1
2025-03-19 11:01:48,062 - Inv1 - sync - [ERROR ] - Connection to (, 8899) failed: [Errno -2] Name does not resolve
2025-03-19 11:01:48,563 - Inv1 - sync - [ERROR ] - Connection to (, 8899) failed: [Errno -2] Name does not resolve
2025-03-19 11:01:49,064 - Inv1 - sync - [ERROR ] - Connection to (, 8899) failed: [Errno -2] Name does not resolve
2025-03-19 11:01:49,565 - Inv1 - sync - [ERROR ] - Connection to (, 8899) failed: [Errno -2] Name does not resolve
2025-03-19 11:01:50,067 - Inv1 - sync - [ERROR ] - Connection to (, 8899) failed: [Errno -2] Name does not resolve
2025-03-19 11:01:50,569 - Inv1 - sync - [ERROR ] - Connection to (, 8899) failed: [Errno -2] Name does not resolve

It does seem to find the inverter. The .9 and .11 addresses are camera’s by the way and in no way they are the only devices in the network, but somehow they show up here.

When I manually add the IP in de configuration page of the addon, it tries to talk to the Inverter, but it gets 0 bytes returned.

I saw somewhere that I need to add the serial to the apps.yaml file, but where it this located?

G
#2 geoffreycoan

RG what version of GivTCP are you trying to install?

v2 doesn’t work with 3 phase hybrid

v3 partially works but you’ll need to be on the beta or dev release for the latest fixes as 3 phase is still “in progress”

the stuff about apps.yaml is for predbat, which needs some help to get working on the 3 phase, but its getting there (with a couple of automations)

R
#3 RG

geoffreycoan Thanks for the solution; you struck gold. The version was 3.0.4 and since I added the URL of that version of the addon to the HA repository I didn’t see the other versions.

I’m now on the Beta which is 3.1.2. This version is working properly. It spends an awful lot of time detecting that the two camera’s aren’t actually inverters, but it is interrogating the Inverter properly.