Hi all,
Wondering if anyone has an encountered a similar issue with their inverter’s connection to the cloud.
We recently had a gen 3 inverter with the built in dongle installed which is connected via LAN to our router (TP link Archer AX73) and a home assistant on the local network.
The home assistant is running GivTCP and can read the inverter / connected 9.5kwh battery, but the cloud connection has been pretty intermittent. It’s now completely dropped off the network for the past 24 hours, while the GivTCP connection has remained stable.
I’ve previously tried adjusting some of the routers settings to help make the connection between the cloud and the inverter stable, which did work at first but now doesn’t seem to be doing anything.
Unfortunately haven’t had a response from GivEnergy or much help from my installer so any advice on what settings may affect the connection would be appreciated.
Odd, mine is rock solid:
I have given it a reserved IP:
I’m also on dongle firmware 206 which has better support for 2.4GHz and 5GHz on the same SSID.
I’ve reserved an IP for it so have a feeling the lack of connection might be due to me tinkering a bit too much with the router settings.
Other than reserving an IP did you need to change any other settings? If not, then I might just need to reset the router and hope for the best.
the inverter ONLY connects on the 2.4GHz wifi network, but once it is connected, it is stable
do you have a mesh network? Sometimes mesh network things like fast roaming can interfere with the dongle working, but as long as you haven’t set any firewall rules up the inverter should be able to make the outgoing connection it needs to the givenergy portal. I’ve had examples of the inverter talking to the portal but not givtcp (fixed by rebooting the inverter) but not heard of the other way around
The inverter is connected via Ethernet. It’s located in our garage so connecting via WiFi would require setting up a mesh network to boost the signal to the 60% signal strength required.
I did try resetting the router last night to see if I had accidentally switched a setting which resulted in the router blocking the dongle from communicating with the internet, but unfortunately that didn’t seem to help. I’ve had the IP address allocated to the inverter (mine seems to sit on 192.168.0.227), but again no luck there either.
Ironically, it the dongle seems to be dropping off the network this morning right after checking the forum so I have a feeling a hard restart of the inverter might be needed…
if its wired then comments about mesh config are clearly not relevant
when you say that the inverter has dropped off the network as far as the portal is concerned, do you see data in the meter data or other sections coming from the inverter? sometimes I have seen my own inverter reporting as disconnected but yet the portal is still receiving data updates OK. I put it down to a portal bug and since I predominately use HA and givtcp (and predbat) I didn’t care about this mis-reporting in the portal
1 Like
Unfortunately not - it’s not providing any data on the GivEnergy cloud. As of last night, it seems to have completely dropped off.
Previously I would get data via GivTCP and not the cloud, but now I’m not getting anything.
It seems to be connect to my router, not upload or download anything for a few minutes then drop off again. Just to check - did you have to change the work mode of your dongle for it to work? I’m not able to change from APSTAETHW mode so I’m not sure if it’s a symptom of a wider issue with the dongle or the cause.
I never changed any settings on my dongle, it just worked with givtcp out of the box from day 1.
Only things I have done on my dongle were to turn off SSID broadcast, add a password, and then when I got a mesh network to change the network id it was looking for.
I have seen the inverter sometimes stop communicating with local modbus, and restarting the inverter fixes that.
Just to confirm, yours is a Gen 3 inverter, not a high voltage? What firmware?
Worth checking the givtcp github issues, there are problems with high voltage inverters that have lots of registerers, givtcp can cause the inverter to lockup after a while because of the amount of data retrieved, and I think there is an issue reported with inverter firmware 620 (may be misremembered) that isn’t working reliably with givtcp. Both of these are reported on github issues
1 Like
Definitely a gen 3 inverter - not entirely sure what software it’s running but hopefully that photo of the cloud page should help.
Think you’re right about the firmware being the cause as I did manage to get the inverter to connect to the cloud this morning, only for it to disconnect once Predbat sent a charge request via GivTCP.
I’ll take a look at GitHub to see if there’s a fix.
1 Like