That is the failure of why GoodWe is not on my recommended list - the hardware is robust and well built, and you cannot fault it, but it is let down by very poor documentation of the API and hence ability to integrate into HomeAssistant.
This is the pivot point for me - any HomeAssistant integration written by reverse engineering a vendor protocol with all the guesses that involves is always going to be possibly incomplete, and may overlook some critical firmware update changes. Screen scraping their SEMS portal is always going to introduce lags. Not a problem for a simple device, but not when I am shuffling tens of kilowatts around my house, car and the electricity grid on a minute by minute basis, and making financial choices based on the data being accurate and up to date.
A vendor that documents their API and openly updates it is going to get my money.
GoodWe: Are you listening? You are losing sales by not devoting efforts to document your APIs sufficiently.
I have had a GW9.999K-EHA-G20 and batteries installed last week which came with the Wifi/Lan Kit 2.0 Dongle. With modbus TCP enabled and connected to my IoT SSID, I can connect to it with the home assistant goodwe integration.
Not sure if it is a combination of new firmware and software but it just worked. I was already planning on running a cable but it has a solid connection to my lone AP and has been working fine.
Interestingly, when using the experimental goodwe integration, the Goodwe optional settings show it using UDP rather than TCP, but still on port 502. Unifi confirms it as TCP however.
Just thought I would mention it in case it helps someone else avoid a cable run if not required.
Now I just need to work my way through the configuration options
I experience the same as Flibbles. Standard HA integration works perfectly for my needs so far. The Goodwe is connected to wifi only, in fact it’s actually on a separate SSID, on a separate VLAN, with firewall rules that allow only the HA server to talk with the Goodwe.
The firewall reports traffic using TCP to port 502 on the Goodwe
