Akulatraxas
Does not work on L1 Huawei inverters
I have an Huawei inverter, SUN2000-6KTL-L1, with this version of firmware: V200R001C00SPC146 502 port is not opened in this inverter, only 6607. I already setup my Huawei integration, which works fine from march, this year. However, I wanted to add an energy diverter, which also must connect to inverter to get its production. Because of lacking on connections on this port (only one at a time) I needed a solution, and I found a friend on internet which made the connection successfully, but with an M1 inverter, which is three phases inverter, not mono phase like mine.
I tried to setup the modbus-proxy, changing the ports from 502 to mine, 6607. However, even if it seems to starts well, I cannot make the integration to connect to my HA instance.
these are the parameters of modbus-proxy:
upstreamhost: 192.168.1.103
upstreamport: 6607
listenport: 6607
connection_time: 0.1
timeout: 1
loglevel: INFO
103 is my inverter... So, now I want to change the Huawei integration to connect to my HA ip, which I think must get information from modbus proxy:
Ha integration connection:
host: 192.168.1.11
port: 6607
slave ID: 0
I tried different settings, no one worked.
Please, help!!!
Any error message in the logs? How do you run your HA? Did you check if the port 6607 is open and accessible on your HA Server ?
No error. I am using already the integration of Huawei inverter on port 6607, so the port is ok.
Ok, I tried with a friend, using a remote app, because he didn't believe is not working. Somehow, the plugin tells me that expects connections on 6607 port for my inverter ip port 6607. But if i checked for ha ip, port 6607, using telnet client from my local network windows computer, seems it is not responding, so the port is not opened for haos.
My HAOS runs on a proxmox installation on a server in my local network. I've checked an proxmox firewall for haos is off.
How to check, or what do I have to setup on haos to be able to open and access port 6607 for modbusproxy?
I will let it opened, maybe someone find the issue, or admin closed it.
Meantime I've solved my issue, by installing a new Debian virtual device on my proxmox installation and I've installed the modbus-proxy there, not the HA integration, and now it works like a charm.
Good luck!
Can you show your modbusproxy configuration? I do the same, but in home assistant i got the error message unknown error.
@StefanW86 , as I said, I solved my issue installing modbusproxy into a Debian virtual container, also I've created a service which automatically run the script every time container restarts. I don't need the HA addon for this.
I have a similar problem. I am trying to set up multiple connections on my Huawei WR 10KTLM1. I know that the Huawei dongle is very sensitive when it comes to Modbus connections. When I access the instances individually on the dongle (..46:502) via Modbus, the connections work. When I use the Modbus proxy in between, I get an unexpected error. Unfortunately, there is nothing in the log. When I use the proxy to access my WP, it works. So it must be a special feature of the Huawei dongle. The same thing happens when I run the underlying proxy as a Docker container directly on my Unraid. This would have the advantage that I could address multiple Modbus servers with one container. This would be a suggestion for improvement for the adon.
