Ethernet connection doesn't seem to be sending any data

We have a complex commercial setup with several subnets. The 3phase 11kW Gen 3 hybrid inverter is connected via ethernet to our BMS network. I can ping the IP and connect to the HF-A21 web interface. However if I point the mobile app or GivTcp to the IP address no data is received.

If we connect the HF-A21 via WiFi instead it works locally. And the cloud connection is working via ethernet.

We don’t want to use WiFi as we need to connect physically to our BMS network.

Is this a config issue, or is the HF-A21 incapable of sending data locally via ethernet?

Cheers

Are the dipswitch set correctly?

They are set to “LAN” e.g 1-1-1-0 although there’s nothing in the manual other than this picture so I’m not entirely sure what purpose is just assuming that’s correct.

If you are using several different networks - do you have a firewall between the subnets ?

I think port 8899 (TCP) is used. so perhaps test that - you can run the command below to test it’s open

powershell tnc <your inverter ip> -p 8899

image

you could also just do :frowning:

telnet <inverter ip> 8899

And then if it’s working it well get lots a stuff scrolling on your screen

I can connect fine, it’s just not sending any data. e.g. if I connect the mobile app, it’s successful but everything reads 0kw.

Just tried out of interest. TCP test works, Telnet shows nothing. Interestingly telnet on the default port presents with a user/pass login, which works and leaves me with a CMD> prompt.

So I can connect to it just fine but it won’t send any data

I’m familiar with or can understand the rest of the settings on the HF-A21, but I don’t know what the UART settings should be. They haven’t been changed to my mind, but does anyone know what they should be?

the uart settings are the same as mine - and mine works,

My only other suggestion would be to confirm that you have a default gateway configured

I have also given mine a “Static IP” so that it never changes ( DHCP can change over time )

if that is already in place I’d suggest a reboot ( standard helpdesk answer )