-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration stops working #85
Comments
Check the version of firmware on your inverter. If your inverter has been upgraded recently this will be the problem. It appears Huawei have disabled the MODBUS port on the home wifi connection in firmware newer than 114. See this thread: |
@scoggins Any solution for this? |
I set up a raspberryPi that connects to the wifi SSID SUN2000-HSV... and has nginx stream proxy for the modbus port onto my home network via Ethernet. Only solution I've found so far. |
Oh my... that's just a big workaround, which probably also means that each time you want to connect to the inverter via the Soler Fusion app to do some settings, you need to disconnect that raspberryPi, right? Also, it works until they decide there's no Modbus at all available via their own wifi. |
Yeah. If you want to go via device commissioning. You need to disable the nginx proxy or it won't let you connect.
Cloud upload still works fine.
…Sent from my iPhone
On 2 Jul 2022, at 19:32, Marco Almeida ***@***.***> wrote:
Oh my... that's just a big workaround, which probably also means that each time you want to connect to the inverter via the Soler Fusion app to do some settings, you need to disconnect that raspberryPi, right? Also, it works until they decide there's no Modbus at all available via their own wifi.
Is it still sending information to their cloud?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
@scoggins Any tutorial to do it? I have a Rpi1 and a Rpi3 layin' around. |
Don't really have a tutorial. I'd imagine there is one out here somewhere. But the short run down of what I did was:
network:
ethernets:
eth0:
dhcp4: true
optional: true
version: 2
wifis:
wlan0:
access-points:
"SUN2000-HV<serial>":
password: "<password>"
dhcp4: yes
dhcp6: yes
optional: true
stream {
server {
listen 0.0.0.0:6607;
proxy_pass 192.168.200.1:6607;
proxy_connect_timeout 2s;
proxy_timeout 30s;
}
}
That should give you a nginx thats running a stream proxy for port 6607. You should then be able to point home assistant at port 6607 and the IP of your raspberry pi on your home network (I normally reserve the IP in DHCP or you can change (2) so that the netplan sets a static IP Netplan Config Examples. |
I've implemented the nginx proxy and can successfully telnet to it. Also, from the rpi client to the huawei inverter I can telnet to the 6607 port on the inverter, so it seems services are running both on the inverter and the "proxy" machine. nmap from the proxy rpi to the inverter: nmap from my computer to the proxy rpi: When I use a modbus client to test the connection I get an error: Any specific settings on the inverter @scoggins |
Yes, you need to follow the instructions at https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/789585-100027 that show how to enable the modbus port again. Firmware above 115 disable it by default and you need to re-enable it. |
I've been having some issues with this setup and the proxying of the connection would just stop. The end solution I came up with was I now have a raspberry PI running ubuntu that has ethernet to my home network, and connects to the WIFI SUN2000 of the inverter. I've the configured the rPI Ubuntu box to be a gateway and to NAT (via iptables) the traffic to the SUN2000xxxx wifi network. Then I added a static route on my router to send 192.168.200.0/24 to the rPI. This means that my HA box can now talk directly to 192.168.200.1 without the need for a proxy. It also means the inverter can't talk back into my home network via it's internal interface. |
I have the integration running for a few months now and now is the third time that it stops working, last time I waited for a couple of days and then it started working again without me doing something to fix it.
Is there any know problem that looks like this, or is it an option to look into it, if yes, please tell me which information i should provide to do the troubleshooting.
Best regards,
steven
The text was updated successfully, but these errors were encountered: