Integration Solar inverter huawei 2000L

OK so bit of an update looks like I got it working and TBH I am not sure how :smiley:

First I reset my systems, I went through the same process again and it worked.
however one thing i did not notice was that i needed to install both at the same time as where previously i did one at a time. so using 1,2 on ID is probably what did it :smiley:

Now the documentations says that you are supposed to get a request for the installation password but I did not get this request soā€¦ lets see if that makes a difference later.
image

One more question for the forum. I live in DK and instead of Pound and pence it is dkk and Ćøre

So, I receive spot prices from Noordpool and when energy spot prices is < 0.05 Ćøre (at this price it actuallycost me to send to grid) I would like to set both my system to Zero Export Limitation, and when I do this manually I know I need to do this from the Dongle configuration. Is this possible at the moment through do do this with Home assistant.

FYI I have limited coding so not much hope me building this myself :frowning:

I have the same issue, hat to downgrade the battery software to V100R002C00SPC116 and looks ok for now

Hi there,
I canā€™t get the connection to my inverter working.
Iā€™ve tried all possibly combinations of port 502/6607 and slave 0/1, the IP is the right one.
Port scan responded that port 502 is open which makes me believe itā€™s the right one.
Modbus is activated unrestricted.

Iā€™m connected to the dongle via LAN/FE.

When pulling the logs from HA this is what I get.
What other device might interrupt?

software versions:
V100R001C00SPC130
V100R001C00SPC153

Good evening,

I successfully setup the bridge connection between the inverter and my local network and Iā€™m able to ping 192.168.200.100 but I canā€™t ping my inverterā€¦

image

I can however ping 192.168.200.1 just fine in OpenWrt, so iā€™m really confused whatā€™s going on here and how I can fix it. I followed all the comments in this thread to the letter, even found some people with the same symptom but never a conclusive answer how they fixed itā€¦

Your installer needs to activate modbus TCP on your inverter settings.

I somehow managed to get it to work.
I reinstalled the integration in HACS (for the 10th time or so) then it got connected :smiley:

1 Like

I have this now also, feels like it happens a few times a week.

Hopefully itā€™s back online soon, usually I donā€™t do anything.

Ofcourse this time it have not recovered.
Have anything changed?

I am trying to re-install the add-on but its not connecting as before, have the Dongle support been removed again so I need to enable to local direct connect network I have?

ā€œFailed to connectā€ when I try the IP, tried both 502 and 6607 and slave 0 and 1.

Hi guys!

I want to thank the author of this integration for a fantastically easy product to use.

I got everything to work after changing the Wi-Fi network the adapter was connected to. I stupidly enough connected it to my guest network at first (that donā€™t have any access to the rest of my network) wish didnā€™t work at first. After changing to the correct one I got everything to work.

One question though:

Is it possible to change the update interval? At the moment it updates every 30 seconds for me. Can I change this to update more often? Eg every 10-15 seconds?

Best regards and thanks for the fantastic work!

1 Like

I also would like to say thank you.
I have everything connected over a wired connection to a SDongle, and am charging my battery in cheap-time using forecast solar generation.
I should sort out a homeassistant dashboard, but for the time being I have achieved my objective!

2 Likes

Thanks for the integration, itā€™s not working for me though,

I get the following error when loading HACS, didnā€™t have this problem before installing the integration:

Logger: homeassistant.config_entries
Source: custom_components/hacs/__init__.py:171
Integration: HACS (documentation, issues)
First occurred: 15:56:45 (2 occurrences)
Last logged: 16:05:47

Error setting up entry for hacs
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/config/custom_components/hacs/__init__.py", line 220, in async_setup_entry
    setup_result = await async_initialize_integration(hass=hass, config_entry=config_entry)
  File "/config/custom_components/hacs/__init__.py", line 206, in async_initialize_integration
    await async_try_startup()
  File "/config/custom_components/hacs/__init__.py", line 193, in async_try_startup
    startup_result = await async_startup()
  File "/config/custom_components/hacs/__init__.py", line 171, in async_startup
    hass.config_entries.async_setup_platforms(
AttributeError: 'ConfigEntries' object has no attribute 'async_setup_platforms'

Apparently itā€™s about the deprecation of: async_setup_platforms which needs now to be changed to async_forward_entry_setups.

Hi. I read all message of this topic. But I donā€™t understand why I have always some problem. This is my situation about my home network:

internet <-> router1(floor 1) <-> router2(floor 0) <-> router3(floor -1) <- Tp-Link Tl-Wr802N -> huawei-inverter.

Every router and Tl-Wr802N are connected to each other by ethernet. Inverter is connected with router3 by wifi(to comunicate with fusion servers). Instead Tp-Link Tl-Wr802N with openwrt comunicate with inverter by wifi in client mode. I use portforward to export 6607 port to get data.

I have the problem that sometimes inverter disconnect from wifi of Tl-Wr802N. Or sometimes inverter is connected but 6607 port is not exported.

This is my last configuration:
/etc/config/wireless

config wifi-device 'radio0'
        option type 'mac80211'
        option path 'platform/10300000.wmac'
        option channel '1'
        option band '2g'
        option htmode 'HT20'
        option cell_density '0'
        option country 'IT'

config wifi-iface 'wifinet1'
        option device 'radio0'
        option mode 'sta'
        option network 'wwan'
        option ssid 'SUN2000-xxxx'
        option bssid 'y:y:y:y:y:y'
        option encryption 'psk2'
        option key 'Changeme'

/etc/config/network

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fdc5:2521:9a76::/48'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'eth0'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option netmask '255.255.255.0'
        option ip6assign '60'
        option ipaddr '192.168.178.146'
        option gateway '192.168.178.1'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '0'

config interface 'wwan'
        option proto 'dhcp'

/etc/config/firewall

config defaults
        option input 'ACCEPT'
        option output 'ACCEPT'
        option synflood_protect '1'
        option forward 'ACCEPT'

config zone
        option name 'lan'
        option input 'ACCEPT'
        option output 'ACCEPT'
        option forward 'ACCEPT'
        list network 'lan'
        option masq '1'

config zone
        option name 'wan'
        option output 'ACCEPT'
        option forward 'REJECT'
        option masq '1'
        option mtu_fix '1'
        list network 'wan'
        list network 'wan6'
        list network 'wwan'
        option input 'ACCEPT'

config forwarding
        option src 'lan'
        option dest 'wan'

config rule
        option name 'Allow-DHCP-Renew'
        option src 'wan'
        option proto 'udp'
        option dest_port '68'
        option target 'ACCEPT'
        option family 'ipv4'

config rule
        option name 'Allow-Ping'
        option src 'wan'
        option proto 'icmp'
        option icmp_type 'echo-request'
        option family 'ipv4'
        option target 'ACCEPT'

config rule
        option name 'Allow-IGMP'
        option src 'wan'
        option proto 'igmp'
        option family 'ipv4'
        option target 'ACCEPT'

config rule
        option name 'Allow-DHCPv6'
        option src 'wan'
        option proto 'udp'
        option dest_port '546'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-MLD'
        option src 'wan'
        option proto 'icmp'
        option src_ip 'fe80::/10'
        list icmp_type '130/0'
        list icmp_type '131/0'
        list icmp_type '132/0'
        list icmp_type '143/0'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-ICMPv6-Input'
        option src 'wan'
        option proto 'icmp'
        list icmp_type 'echo-request'
        list icmp_type 'echo-reply'
        list icmp_type 'destination-unreachable'
        list icmp_type 'packet-too-big'
        list icmp_type 'time-exceeded'
        list icmp_type 'bad-header'
        list icmp_type 'unknown-header-type'
        list icmp_type 'router-solicitation'
        list icmp_type 'neighbour-solicitation'
        list icmp_type 'router-advertisement'
        list icmp_type 'neighbour-advertisement'
        option limit '1000/sec'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-ICMPv6-Forward'
        option src 'wan'
        option dest '*'
        option proto 'icmp'
        list icmp_type 'echo-request'
        list icmp_type 'echo-reply'
        list icmp_type 'destination-unreachable'
        list icmp_type 'packet-too-big'
        list icmp_type 'time-exceeded'
        list icmp_type 'bad-header'
        list icmp_type 'unknown-header-type'
        option limit '1000/sec'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-IPSec-ESP'
        option src 'wan'
        option dest 'lan'
        option proto 'esp'
        option target 'ACCEPT'

config rule
        option name 'Allow-ISAKMP'
        option src 'wan'
        option dest 'lan'
        option dest_port '500'
        option proto 'udp'
        option target 'ACCEPT'

config redirect
        option target 'DNAT'
        option name 'modbus'
        list proto 'tcp'
        option src_dport '6607'
        option dest_ip '192.168.200.1'
        option dest_port '6607'
        option src 'lan'
        option dest 'wan'

Connection between Inverter and router3 is good and i see data by fusion.
The distance from Tl-Wr802N to inverter is about 1m and the signal is good.

I hope somebody can help me.

Hi!
Is it possible to change these names to a ā€œfriendly nameā€

Hello,

is there any way to use Modbus RTU (for my Wallbox) and the Dongel (for the App/Cloud) at the same time?

Best regards,
Hendrik

yes go to Settings - Device & Services - in the Huawei solar box click entities click the cog and then you can change name -


image

Hello,

is there any way to use the SDongle (in order to get the performance Data into the cloud/App) and Modbus RTU at the same time?

If not: I suppose that the network bridge to the Inverter-Internal-Wifi will not be sufficient to get the performance data into the cloud/app, right?

Any other idea?

Best regards,
Hendrik

Hi all,

i just got a Huawei Plant installed at my house and having trouble to get my inverter connected to ma HA.

The following hardware is installed:

  • HA on RPi4
  • Inverter HUAWEI SUN2000 10KTL-M1
  • Battery HUAWEI LUNA2000
  • Dongle HUAWEI SDongleA-05 (FW 125) connceted via Lan to Router
  • HUAWEI Power Smart Meter

the Dongle has a static IP allocated by me but i dont get any connection in the integration.

I dont have any installer access, so no access to parameters or settings i guess.

What is the best way to get my integration working, if you could choose free?

Thanks in advance

Hi All

Any one used this service.

Hi.
Any solution for cascaded inverters, to appear in HA?
Right now only the Master inverter and SmartMeter (2 devices are detected, instead of 3, thru Dongle/ModbusTCP), are visible in HA, using Huawei Solar integration.
Thanks!