Giv TCP can't comunicate with inverter

6 comments started 2024-08-15 last 2024-08-25
Home Automation
S
#1 Sandy

My Raspberry Pi overheated and died recently and I have just got everything back online from the backup. Since the restore though GivTCP seems to have lost my inverter which breaks a lot of stuff! Here's the relevant lines from the log

2024-08-15 07:29:41,269 - startup - [ERROR] - Gathering inverter details for 192.168.0.38 failed.
2024-08-15 07:29:41,270 - startup - [ERROR] - Unable to interrogate inverter to get base details

I'm fairly sure the IP address is correct in the configuration, I'm also slightly suspicious of this as the inverter now doesn't display it's IP address in the deco app I use to manage the network, I used the GivEnergy app to pull the IP.

While my system was down I switched the network from a mesh wifi network to an access point network to enable the guest network which I now need and I'm wondering if this could have anything to do with it?

G
#2 geoffreycoan

Sandy If you have changed network its quite possible that the IP address for the inverter has changed.

In the GE app, under settings/Local Monitoring do a scan for inverters and see what it comes back with for your inverter IP

Also, look on your network router config (usually something like 192.168.1.254 or .0.254 or .255) and see what IP address has been allocated to the inverter. Worth setting it to a fixed IP address.

In the givenergy portal does it still report the inverter as online and sending data every 5 minutes? If it isn’t then givtcp isn’t going to work. Start from there, getting the inverter back online

S
#3 Sandy

geoffreycoan Thanks but I tried all of that before posting. I am having this issue after updating the IP address in GivTCP as this was the first thing I tried. It did take a while for the Deco app to see the new IP but it is now showing and matches.

In the GE app everything is fine, I it succesfully finds the inverter locally, I have all the usage history and I can see everything online through the portal too. I really don't think this is an inverter issue and is something local to HA.

Any other ideas?

G
#4 geoffreycoan

Sandy While my system was down I switched the network from a mesh wifi network to an access point network to enable the guest network which I now need and I'm wondering if this could have anything to do with it?

Can you explain a bit more about the network setup? You mentioned a guest network, I'm wondering if your HA is on one network (say your main network) and the inverter is on the guest network and there isn't appropriate routing between the two networks? Although you say the GE app is working and it finds the inverter locally by which I assume you mean it works in Home mode, and that generally needs your phone/tablet to be on the same network as the inverter for that to work.

Did you set the 'is it an AIO' and 'old firmware' switches correctly for your inverter type?

You could delete all the PKL files out of /config/GivTCP, these are cache files and then restart GivTCP. That might cure it?

#5 Dash

Assuming your Giv works in the same way as mine, you should be able to ping the IP address of the inverter to confirm it's as you expect.

Open a command prompt on your computer, and type the command "ping" followed by the ip address and press Enter, e.g.:
ping 192.168.0.38

You should see a series of replies received, which confirms "something" is on that address (hopefully the inverter), if you get time outs, it means there either isn't anything listening on that address, or you have something in the way on your network that's blocking access to it.

S
#6 Sandy

Finally found some time to sit down with this again.

I have it working now, it turned out to be a combination of 2 different things. Firstly, Mosquito MQTT had lost it's user credentials during the restore. It also needed updating and so did GivTCP.

I was also having various network issues because of the VPN tunnel I forgot I changed on my laptop. This was causing all kinds of network problems which once I realised were causing is, was an easy fix, simply turn it off!