Hello, really now its necessary the wrt router or similar? I install the new integration (with emilyv2 worked very good) and i view a loto of sensors, but some sensors are offline. I’m lost… 
Hi.
I have the same problem - emilv2 working ok, wclrs error “Reading from the inverter failed.” - do You solve the problem ? I use dd-wrt as the client, maybe there is a key to solve the problem
Just came here to say that after i upgraded inverter and smartdongle to latest version, the integration made by wlcrs works by using the local lan ip of the smartdongle.
In other words, i dont have to connect to the inverters AP. 
However, just like @rotnar i have 12 offline sensors.
1 Like
On what port do you connect?
Standard port (502 if i remember correctly?).
And i had to change slave id to 1 also.
1 Like
It seems you are getting sensors from the inverter itself, not the zero-export device sensors. check whether both devices are enabled in integrations.
These sensors are disabled by default, but can be enabled in the settings if you find them interesting.
1 Like
I summarized in this post. Does it qualify for addition to wiki?
1 Like
it doesn’t matter if you use dd-wrt or OpenWrt or connect using rpi with external wifi and internal wifi, integration will act the same.
You just need strong signals between the device used to connect to the inverter, router or rpi4.
did you enable all 12sensors as wlrcs suggested? can you post the screenshots? which inverter model you have?
Is Your fusion app working too?
Dear all,
I have spent some time reading the wiki/Readme.md on GitHub and more time reading posts in this forum and I’m a bit lost.
In the wiki Connecting to the inverter section, it is written:
Huawei has disabled this port completely in recent firmware versions when you are not using a dongle (eg. 192.168.1.195 in the example without dongle below will not work anymore)
Reading this, I understand that with a dongle, it should work (else why mention this?)
But in the README.md file, one can read instead:
Starting from firmware updates released in December 2021, Huawei has closed the Modbus-TCP interface on the network to which the inverter connects. ie. If the inverter is connected to your home network on 192.168.1.11, it will no longer be possible to connect on that IP. This also applies for connecting via the Dongle.
So, the dongle is of no use here. This is confirmed a bit later:
Note: Having an SDOngle will not remove the requirement of connecting to the WiFi AP of the inverter.
I have spent some time in the (very long) HA forum on the integration but I have failed to get if option B of the “With Dongle” scenario on the wiki Connecting to the inverter is viable (as the wiki says) or not (as the Readme.md says).
In the end, is a wifi Dongle of any use to connect to the ModBus port or should I just buy a small router given that my inverter will be far from my HA instance?
If someone clarifies this, I will be happy to submit a simple PR on the ReadMe/Wiki to remove the apparent inconsistency.
Hello!
I Had the same questions as you and also think the wiki/Readme is somehow missleading here.
I can confirm that a SUN2000-M1 inverter with dongle and newest dongle firmware can communicate with the integration via Modbus TCP (over wired LAN in my case). I have an SUN2000-5KTL-M1 inverter with dongle (dongle firmware is V100R001C00SPC129). Everything works fine on my setup, but it is very important to do the following steps:
- Setup Modus on the inverter with the Fusion App directly connecting to the inverter WLAN
- Manually update the dongle firmware over the Fusion web portal to V100R001C00 SPC127 or newer
- Activate the Modbus communication via the Fusion web portal
Important: All the steps can only be done with install rights, so I had to contact my installer who was very kind and did all the steps for me.
These findings are based on a document for a commercial power management device which is compatible with Huawei inverters. They put a pretty good step by step description of the mentioned tasks on their webpage. Unfortunately this file is German only. If there is any need I would translate it for you.
Link: https://www.smartfox.at/assets/de_huawei-wr-auslesen_tcp_08.06.2022.pdf
Michael
Thanks a lot Michael. I’m a native French und mein Deutsch nicht mehr viel wert. Aber es wird genug sein, um eine Dokumentation (?) zu verstehen :-/
I will look into it. I’m still wondering if an Sdongle with a wifi connection to a main router will work (present the Modbus port to other client of the router). If anyone here knows, please tell me.
I encourage you to edit the Wiki/create a PR for the README once you figure it out. My installation came without an SDongle, and the conflicting accounts for the scenario with the dongle come from different people that came to different conclusions.
I do plan to add support for connecting to the inverter via an USB-to-rs485 dongle that is wired to the RS485_1 and RS485_2 pins, which should hopefully be easier for people to get up and running. Now I have the impression that half this topic is about people struggling with the networking side of things 
So hopefully we can bring that to an end, and have people use cheap (easy to find for less than 3$/€) USB-to-rs485 dongles instead. For those who cannot wait: mbusd looks like a perfect piece of software glue between those cheap dongles and the existing integration that expects ModbusTCP.
beware. with connection to the dongle, we faced a spike reading both me and @ligeza
Did you face the same issue?
I’ve been using emilv2s and now wclrs integration connected to the dongle since January without problems.
Ok that was a lie, problems not created by myself…
Can you share your data or any screenshots?
If you can use Dongle’s wifi to connect that is the best method, bcz most of us are using these inverters with Huwaei dongle, which has long range and already remains connected to the internet for the feeding data to Huwaei server 24x7x365.
No additional hardware will be required and no messing with firewalls.
I bought the old Netgear router from the used market for $9.4 (Pkr 1600), only for connecting to the Huwaei router but now, it is being used for 10 other purposes too e.g it acts as a second ad-guard server beside the HAOS adguard add-on, SQM server and bandwidth monitor etc.
New Release: 1.1.0
New recommended connection option: direct serial RS485
This release features adds support for direct serial connection via the RS485A1 and RS485B1 pins of the COM-port of the SUN2000-inverter. This is the new preferred method of connecting to the inverter, as it is not susceptible to network connectivity issues, and has elevated permissions by default (necessary for retrieving optimizer data and setting battery configuration parameters).
New feature: reading optimizer data
This data is refreshed every 5 minutes, as the inverter does not offer more granular updates.
Exposed entities:
- Input Current
- Input Voltage
- Output Current
- Output Voltage
- Output Power
- Temperature
- Accumulated Energy Yield
- Voltage to Ground (disabled by default)
- Running Status (online/offline/disconnected)
The option “Advanced: elevate permissions” needs to be checked for this to work: the inverter requires elevated permissions to request the optimizer data.
Tip: the easiest way to find the Optimizer “devices” in Home Assistant is via:
- Go to Settings > “Devices & Services”
- click on “X devices” in the “Huawei Solar” tile
You will now see a list of all devices associated with this integration, including one per optimizer:
Clicking on a specific optimizer will show you the entities associated with that specific optimizer. You can now rename them to something more clear for your setup.
4 Likes
Thanks Thijs,
That’s a very nice option. It requires a physical connection to the inverter and so does not directly solve the problems of people that would like to use a wireless connection to the inverter but RS485 to wifi adapters that support both STA and AP modes such as the WIFI HF7211-0 RS485 wifi server should fill-in the gap. To be tested and reported
Great job !
