It SHOULD. I agree. Fact is: It does once. Once you disconnect it won’t connect anymore. It may be an issue with network manager as well. No idea.
Hi, I’m connected to inverter via internal AP. But since that i notice that in fusionsolar page there appear a lot of communication alarm. Is it normal because of connection via internal AP? Do you have similar?
I never saw any communication alarm/error. I’m connecting to internal AP for 1,5 year.
Hello,
This is a fantastic solution.
I’m a beginner, but that would be very important to me, too.
Can you give a description or code on how to do this? I can do the network solution anyway. I don’t know how to do home assistant integration.
at what step you are stuck?
Hi all,
I am buying a HUAWEI SUN2000-6KTL-L1 with HUAWEI STORAGE Luna 2000, could be them integrated in HA?
Do I need any additional hardware?
Thanks
Hi
I Have the same error…
Do you remember what the issue was?
Sorry found the solution above.
This is my first Home automation project.
Now my configuration is ok but how do I add this to my dashboard?
yes, it can be.
after instaling the new update version d22770b from HACS I don’t see my inverter .when downgrade work again .any information,suggestion ??
Entity name was changed in my case, but I don’t have total and daily yeild in attributes. I tested also async version, but there is much less attributes then in normal versin.
thanks .i will leave the older version .all work like a charm
Daily and total yield are working but they are not in attribute but as another sensors.
2 Likes
I have made the storage_total_charge and storage_total_discharge separate sensors in the new version. Let me know if anything doesn’t work.
Hi all,
I have been struggling all day to get a RP3 set up as the bridge, without success. I have been using this guide, given here some time ago, How To: Wifi to Ethernet Bridge(Updated for RPi 3) - Raspberry Pi Forums
Other than not having the sensor set up in HA, can anyone help me by explaining exactly how I check if the bridge is working? I am 99% sure the problem must lie here and not with the component itself.
Thanks.
I’ve got the same issue, no entity at all, have reinstalled and double checked the config and no joy. Not seeing anything in the logs either. One strange thing is when restarting the core I get the error
invalid syntax (sensor.py, line 347)
This has been fixed in the latest git revision.
In an effort to be more helpful, I offer this from the pi:
pi@raspberrypi:~ $ ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.24.1.1 netmask 255.255.255.0 broadcast 172.24.1.255
inet6 fe80::a61e:b9ba:33ff:eaf1 prefixlen 64 scopeid 0x20
ether b8:27:eb:93:79:68 txqueuelen 1000 (Ethernet)
RX packets 345 bytes 59567 (58.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 87 bytes 13683 (13.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 105 bytes 9995 (9.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 105 bytes 9995 (9.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.8.100 netmask 255.255.255.0 broadcast 192.168.8.255
inet6 fe80::276c:a122:364b:9176 prefixlen 64 scopeid 0x20
ether b8:27:eb:c6:2c:3d txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 25 bytes 3699 (3.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Thanks for the heads up. This is actually great news.
Thanks Emilv2 the storage sensors are working, but I did notice that this fields are not visible anymore:
* total_yield
* daily_yield
EDIT: Looks like the total and daily yield sensors are now seperate sensors… so I can use them directly.