adding these rules from ssh(I had to break the No command-line rules) partially fixed the issue. Even though I made a mistake in the first rule, my router IP wasn't correct.
Connect it to your ISP router via ethernet. This will change the IP to something in the router’s subnet range. e.g if your ISP’s router Ip is 192.168.1.1 then your OpenWrt's router IP will be 192.168.1.24 (anything in between 192.168.1.2 to 192.168.1.100)
Connect to your Huwaei Sun2000 inverter’s wifi as a client via 2.4Ghz radio.
double click on the “network” and copy-paste the following code at the end of the files. remember to set defaultroute '0" as mentioned in the GitHub wiki.
config interface 'wlan'
option proto 'dhcp'
option defaultroute '0'
7. repeat the process with “wireless” files by adding the following code to the end of the wireless file. changing according to your inverter’s AP’s Name and BSSID
Verify connectivity, Before continuing with the setup of the integration, you should test whether you can ping the inverter on 192.168.200.1. You can use one of the SSH/Terminal add-ons of HA, or use a terminal in the VSCode add-on.
Install this integration with HACS, or copy the contents of this repository into the custom_components/huawei_solar directory
Restart HA
Start the configuration flow:
Or: Go to Configuration -> Integrations and click the + Add Integration. Select Huawei Solar from the list
Choose whether you want to connect via serial or network connection. In this case we will choose network
Enter the IP address of your inverter (192.168.200.1). The slave id is typically 0. You should only check the Advanced: elevate permissions checkbox if you intend to dynamically change your battery settings.
When using the elevate permissions feature, you might be asked to enter the credentials to the installer account in the next step. These are the credentials used to connect to the inverter in the "Device Commissioning" section of the FusionSolar App. The default password is 00000a..
@eduperez@trendy@slh@frollic@pavelgl Sorry for bothering you all.
Is this the correct configuration correct? It is working fine but does it fulfil proper networking criteria? Or do you suggest any changes?
At least one user reported this as working even with v22.03.0-rc4.
Opening this after one year, on 23.05rc2/snapshot I am facing this strange issue. Can't access the internet with the above config.
logs
Sat Jul 8 17:27:07 2023 daemon.notice netifd: wlan (2329): udhcpc: broadcasting select for 192.168.200.2, server 192.168.200.1
Sat Jul 8 17:30:01 2023 daemon.err uhttpd[1454]: [info] luci: accepted login on /admin/system/reboot for root from 192.168.18.126