I would appreciate any suggestions on the following issue, please.
I am running GivTCP as a container alongside Home Assistant. Up until a couple of days ago this was working. I am now continuously getting the following errors:
2024-04-06 12:07:49,324 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.215, 8899) failed: timed out
2024-04-06 12:07:51,828 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.215, 8899) failed: timed out
2024-04-06 12:07:54,330 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.215, 8899) failed: timed out
2024-04-06 12:07:56,834 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.215, 8899) failed: timed out
2024-04-06 12:07:59,337 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.215, 8899) failed: timed out
2024-04-06 12:08:00,640 - Inv1 - read - [ERROR ] - 10 failed inverter reads in a row so removing regCache to force update...
I have had these occasionally before when the inverter drops off the network, but these are now persistant.
My inverter is on the network at that IP address and listening on port 8899:
$ nmap -p 8899 192.168.0.215
Starting Nmap 7.80 ( https://nmap.org ) at 2024-04-06 12:24 BST
Nmap scan report for 192.168.0.215
Host is up (0.023s latency).
PORT STATE SERVICE
8899/tcp open ospf-lite
Nmap done: 1 IP address (1 host up) scanned in 0.10 seconds
In case this was a corruption issue, I deleted the container and image and re-ran docker compose, but the issue remains.
"6345:6345" # REST (add increments for each inverter)
"3000:3000" # This should match the WEB_DASH_PORT ENV below
environment:
Critical to update
NUMINVERTORS=1 # Set this to the number of Inverters in your setup, then replicate the next two lines for each inverter (changing the last number of the ENV)
INVERTOR_IP_1=192.168.0.215 # Set this to the IP address of your Inverter on your local network
NUMBATTERIES_1=1 # Number of battery modules installed and connected to the above inverter
MQTT_OUTPUT=True # "True" if you want to publish your data to MQTT, "False" otherwise
MQTT_ADDRESS=192.168.0.40 # IP address of an existing MQTT broker, or leave as "127.0.0.1" to use the internal broker
MQTT_USERNAME=[redacted] # Username of your existing broker, if needed. Not required for internal broker
MQTT_PASSWORD=[redacted] # Password of your existing broker, if needed. Not required for internal broker
HOSTIP=192.168.0.40 # External IP address of the docker host (needed for web dashboard)
CACHELOCATION=/config/GivTCP # Location of cache data, this folder can be mapped to a persistence storage outside the container
TZ=Europe/London # Set to your Timezone
Optional
DAYRATE=0.33787 # Price in £/$ for your daytime electricity per kWh
NIGHTRATE=0.095 # Price in £/$ for your night time electricity per kWh
EXPORTRATE=0.165 # Price in £/$ for your export electricity per kWh
DAYRATESTART=07:00 # Time in HH:MM when your day time\expensive tariff kicks in
NIGHTRATESTART=00:00 # Time in HH:MM when your night time\cheap tariff kicks in
I would appreciate any suggestions on the following issue, please.
I am running GivTCP as a container alongside Home Assistant. Up until a couple of days ago this was working. I am now continuously getting the following errors:
2024-04-06 12:07:49,324 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.215, 8899) failed: timed out 2024-04-06 12:07:51,828 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.215, 8899) failed: timed out 2024-04-06 12:07:54,330 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.215, 8899) failed: timed out 2024-04-06 12:07:56,834 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.215, 8899) failed: timed out 2024-04-06 12:07:59,337 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.215, 8899) failed: timed out 2024-04-06 12:08:00,640 - Inv1 - read - [ERROR ] - 10 failed inverter reads in a row so removing regCache to force update...
I have had these occasionally before when the inverter drops off the network, but these are now persistant.
My inverter is on the network at that IP address and listening on port 8899:
$ nmap -p 8899 192.168.0.215 Starting Nmap 7.80 ( https://nmap.org ) at 2024-04-06 12:24 BST Nmap scan report for 192.168.0.215 Host is up (0.023s latency).
PORT STATE SERVICE 8899/tcp open ospf-lite
Nmap done: 1 IP address (1 host up) scanned in 0.10 seconds
In case this was a corruption issue, I deleted the container and image and re-ran docker compose, but the issue remains.
This is my docker compose config:
givenergy: container_name: givenergy image: britkat/giv_tcp-ma ports:
Critical to update
Optional
API Key for the GivEnergy Cloud
restart: always privileged: true volumes: