Sunsynk Power Flow Card for Huawei (WLCRS)

[Roving-Ronin]

Moving the discussion from #631

Yes that is what I am doing currently, so all users of WLCRS can add the SunSynk card in HACS, then go to the documentation site https://slipx06.github.io/sunsynk-power-flow-card/examples/huawei.html and choose from 1 of 5 examples (combinations of 1phase or 3phase inverters with 1 or 2 inverters and 1 or 2 batteries) and copy the yaml into the card on the HA dashboard, then place two files into your packages directory that have the derived sensors.

These derviced sensors have the logic built into them so that if you don't have a battery(s) or only 1 string etc they won't cause your HA to stop, at worst they'll have a (!) icon in the entities list and if that bothers you can you just disable them. At least this means there's ONE version of the sensors file that works for everyone (I was originally writing 4 versions and then thought ...what the xxxxx).

The other file is one with some default example sensors (actually my GPO for the UPS with all my servers and another for the Network Kit in my place, given they are the biggest constant draw). Instead of using the AUX to show generators by default I've used that to show two major users of power (the green boxes above the house icon) that then show their combined Active Power and above that their Daily kWh usage.
For Non-Essential Load I've used my HVAC, Oven and Clothes Dryer (if you have a battery you can only show 2 though, due to space on the card), with these summing up their draw. Basically when finished you just need to modify the AUX and Non-Essential groups created in HA to contain the devices you have/want to monitor and then you end up with it working out their Active Power, and from that deducting that so the purple box (Active Power into house) reflects the total less these others that are already shown .

Note: The colours can be changed. The thickness of the lines from the PV to Inverter / Inverter to Battery / To Grid is proportional, i.e. more active kW then it is thicker. The battery outline changes colour to reflect its' status and/or the source of energy when charging. The house changes colour proportionally to show the source of its power (i.e. will be 50/50 yellow and red, if powering from solar and grid). The 'balls' on the lines move in the direction of the power flow and move faster/slower based on the volume.

Examples:

2 x L1 5kW (1 phase) Inverters with 1 x 15kWh LUNA S0 ESS - System currently charging and importing (58W) from the grid.

Battery fully charged and floating, whilst excess kW are exported to the power grid.

---

2 x M1 6kW (3 phase) Inverters with NO battery - System currently producing and exporting to the grid.

[spelzl]

Yiehpiehyeah!
Great!
Thank you so much!

[Roving-Ronin]

@spelzl
No definitely works, here's another users HA who graciously gave me remote access to allow the development and testing of the card with Huawei. He has a single LUNA 15kWh and it shows the temperature fine, from the 'batteries' (plural) sensor.

I'm hopeful to get an update from @serbat this weekend, but last weekend he had the temperature working fine also. His setup is 2 x 15kWh LUNA ESS (I'm jealous) ;-)

Can you double check the card yaml to confirm no typos? i.e.

battery_temp_182: sensor.batteries_temperature

Whilst the card config and sensors for Huawei is written with the intent that one set of derived sensor yaml files will cater for all users (1 or 2 inverters and with 0, 1 or 2 batteries) you could always change your card yaml to (let me know if you do and send me a screenshot of the card please):

battery_temp_182: battery_battery_1_temperature

and just remember to change to the inverterS sensor if you ever get 2 or more batteries (BTW the new LUNA 7/14/21kWh S1 allows running up to 4 x 21kWh batteries in parallel off 1 inverter for a total of 84kWh .... now if only the ESS prices would drop !) and/or the WLCRS name of the battery sensor changes (I have an issue open to fix how its naming format is still 'pre v1.3.1' and not the current format) that would see it be:

Battery 1 Entity Name = sensor.battery_temperature
Battery 2 Entity Name = sensor.battery_temperature_2

Edit:

If you have a battery you can't add a 3rd non essential entity to the card, given the battery uses the space on the card.

[spelzl]

Hi @Roving-Ronin ,
I can set the value of sensor.batteries_temperature in the developer tools and see the change reflected in the dashcard.
But obviously that isn't dynamic but static.

The individual temp sensors below seem to be unavailable for some reason.

I am at my wits' end what else I could try.

I also tried to add a third non-essential load. But it does not appear on the dashcard. Any advice here?

Your support is appreciated!

[Roving-Ronin]

@spelzl did you update to WLCRS v1.3.3 ? If so, have you reinstalled the modified sensor.py that adds support for the battery temperature?

[spelzl]

@Roving-Ronin
Yes, I did both.
I am not sure what else might be missing.
Still didn't get the third non-essential load to show up in the dashcard.
I wonder why the designer adds the decimal points for the voltage values but doesn't for the PV energy.

[Roving-Ronin]

@spelzl contact me if you want me to have a look ?

[serbat]

No, I have never seen a guide, only in Italian. I followed the instructions for installing HACS, then I copied the files into it, the most difficult thing is the installation from HACS but on the dedicated page it is quite understandable even for me who don't speak English https://www.vincenzocaputo.com/home_assistant/sunsynk-power-flow-monitoraggio-energetico-spettacolare-per-home-assistant-974

…

Il 25/02/2024 15:13 CET spelzl ***@***.***> ha scritto: Is there a guide how to setup the card within HA, which I can forward to friend? — Reply to this email directly, view it on GitHub #632 (reply in thread), or unsubscribe https://github.com/notifications/unsubscribe-auth/AT2PEL6NUZQYMNR5EWGXH6TYVNBKBAVCNFSM6AAAAABDYB5O5KVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DKOBTGI3TE. You are receiving this because you were mentioned.Message ID: ***@***.***>

[spelzl]

Hi @Roving-Ronin,
is it right that the value of the battery charge power is wrongly indicated, i.e. with - when the battery is charged and without - (i.e. positive value) when the battery is discharged?

[Roving-Ronin]

No, it moves from the battery towards the inverter when discharging and conversely the other way when charging.

Se in the example configs Ove posted, the 'inverted' is true for the Huawei battery.

[spelzl]

@Roving-Ronin You are right. I meanwhile realised the dot movement is correct.
However, the charge discharge value apars to be wrong negative vs. positive.
I have re-edited my initial question above accorsingly.

[Roving-Ronin]

@spelzl
Can you check if 'show_absolute' under the battery is set to true or false on your HA ?

FYI the card on the left has 'show_absolute: true', whilst the card on the righ has 'show_absolute: false'. Sensors showed the battery was actually charging, that should show as '44W' (not '-44W) on the card.

I might have to check this in 12hr's (when the sun is up on the location where I have remote access to a battery). At the moment that battery is only doing charge/discharge in 1-2 digit numbers, making it not 100% clear for validating things.

[spelzl]

@Roving-Ronin where would I need to look for if the absolute is set to true or false?

What does it take to grant remote access?

[Roving-Ronin]

@spelzl if you edit the dashboard and then edit the sunsynk card, switch to the editor (not the graphical editor) and it will be in the 'battery' section of the card yaml code.

Simplest way for remote access is if you have either of:

1. You have the remote access setup with the NABU CASA cloud access, then create and username/password and share those and the URL.

2. Port forward tcp port 8123 on your firewall to your HA server, and preferably lock it down to the remote IP that can access it from (or publish using a reverse proxy like NGINX Proxy Manager / Traefik). Then provide a HA username/password to login.