Adding Wallbox features

[mraether1988]

Hello and thx very much for your great work, works fine. Can you add the features for the official Sungrow wallbox (adding loading category and seeing actually loading data?

[stargoose77]

That would be awesome, i have the modbus protocol for the wallbox ac011e-01 and can make it available for whoever wants to implement it.

By the way, there is a single-phase/three-phase swichting function via modbus, this is not yet officially available in the app!

So i think that would make a big change for many users using home assistant.

[Louisbertelsmann]

Here it is. Hopefully SunGrow doesn't come after me
AC011E-01_Modbus_Protocol_V1.0.16_EN_Confidential.pdf

[Louisbertelsmann]

It's a bit complicated. We have to either use the IP of the wallbox directly to use modbus or integrate it into the sungrow_modbus.yaml, which takes a bit of time and maintaining.

[btota]

okay, trying these settings in secrets.yaml

wallbox_modbus_host_ip: 192.168.178.159 (wb ip on fritzbox )
wallbox_modbus_port: 502 (same port?)
wallbox_modbus_slave: 248 (?)

causes connection error, trying 192.168.178.158 (sh10rt) causes modbus pipe error (too much connections I think), but yea as u said takes time :)

[SunnyCrockett]

@stargoose77 is there a chance, that there is a never version of the Sungrow documentation? I am searching for the registers for charging mode (fast charging / scheduled charging / surplus charging / ...) like in the iClodSolar app.

[stargoose77]

@SunnyCrockett You could try it by opening a ticket in iSolarcloud and ask the support to provide you the latest version. It took 4-6 weeks until I got an answer. But finally they gave me the document :-)
I think sungrow supports projects like this and hopefully you will get it faster than I did.

[mkaiser]

I am happy to integrate it, when the yaml generator is finished.

Then we can annotate your wallbox sensors above and generate a customized YAML.

It is still work in progress. Unfortunately, I have not much free time at the moment... So if anyone likes to help, text me in discord :)
https://github.com/mkaiser/modbus_sungrow_yaml_generator

[btota]

which makes you all to unique items, thanks again!

[GolfOWL]

Hi @mkaiser ,

lieben Gruß aus Bad Lippspringe. Ich möchte mich bei Ihnen für Ihre tolle Arbeit bedanken. Dank Ihrer HA-Integration konnte ich meinen Technikern zeigen, was im Moment noch nicht wirklich gut eingestellt ist. :-)

Ich würde mich gerne auch gerne mit einer kleinen "Spende" an Ihrem bisherigen Engagement beteiligen. Wie kann ich das machen?

Sie können mich gerne über [email protected] mal kurz kontaktieren. Ich fände das sehr nett.

MfG, Thomas

[GolfOWL]

Hi,

that is one function that I only miss til now. A big thank you in advance to all of you for build a solution.

Thomas

[SunnyCrockett]

Moin
I was able to get the wallbox integration of Louisbertelsmann running together with this mkaiser integration. The key was to use the LAN port (WLAN not tested) of the dongle and not the ModBus LAN port. Additionally I had to use slave id 3 instead of 248. On the web interface of the dongle you can see a list with all connected devices, there the wallbox has for me 248 (maybe internal id?) and 3.
At the moment, I am using ModBus LAN port IP with slave id 1 for mkaiser and dongle LAN port IP with slave id 3 for louisbertelsmann integration, both with port 502 (ModBus proxy not needed for my case).

Cheers Sunny

[btota]

Then in secrets.yaml needs to be:

wallbox_modbus_host_ip: 192.168.178.150
wallbox_modbus_port: 502
wallbox_modbus_slave: 3

... a second yaml beside mkaiser exists? current modbus_wallbox.yaml from https://github.com/Louisbertelsmann/Sungrow-Wallbox-Modbus-HomeAssistant/blob/main/modbus_wallbox.yaml

Don´t forget to restart HA, empty cache etc.

[GolfOWL]

@btota First - thank you very much for your support. I is good to know that there is an community for this project ;-)

I tried the following values

secrets.yaml

wallbox_modbus_host_ip: 192.168.178.150
wallbox_modbus_port: 502
wallbox_modbus_slave: 3

In the folder "itregrations" I have two yaml-files:

1. "modbus_sungrow.yaml" from Martin Kaiser (last update: 2023-12-31) and
2. "modbus_wallbox.yaml" from Louisbertelsmann (last update: 2024-02-11)

But I got the error(s)

2024-02-11 16:08:59.057 WARNING (MainThread) [homeassistant.components.modbus.validators] Modbus SungrowACx contains duplicate host/port 192.168.178.150_502, not loaded!
[...]
2024-02-11 16:09:17.511 ERROR (SyncWorker_11) [homeassistant.components.modbus.modbus] Pymodbus: SungrowSHx: Error: device: 1 address: 5725 -> pymodbus returned isError True
[...]
2024-02-11 16:09:27.762 ERROR (SyncWorker_8) [homeassistant.components.modbus.modbus] Pymodbus: SungrowSHx: Error: device: 1 address: 5725 -> pymodbus returned isError True

And the last error then over 120x...

If I take a look to the entities, there are the information, that the entity (for example "sensor.charger_enable" (or other)) are not available.

I don't understand why that doesn't work :-(

[GolfOWL]

I have a completely different suspicion - maybe you have an opinion / idea...

I have two yaml files in the folder "integrations". Could it be that the "wallbox"-file ("modbus_wallbox.yaml") is not being integrated?

I tried to add the following block from the "modbus_wallbox.yaml" to the "modbus_sungrow.yaml":

- name: Wallbox device type code
        unique_id: wb1_dev_number_raw
        slave: !secret wallbox_modbus_slave
        address: 21223 # reg 21224
        input_type: input
        data_type: uint16
        scan_interval: 600

And then I could see the entity with a value in the entity-overwiew...

[GolfOWL]

Now I am totally confused...

Before

After

[btota]

Modbus needs time to read everything, Modbus-proxy https://github.com/mkaiser/Sungrow-SHx-Inverter-Modbus-Home-Assistant/wiki/FAQ:-My-Modbus-connection-always-cuts-out would be better/stable, at least for one device, either inverter or wb.

It seems, something is working, why do you have an duplicate "Modbus SungrowACx contains duplicate host/port 192.168.178.150_502"?

[btota]

@SunnyCrockett great job! I've been trying with dongle ip, but never in constellation with slave=3, awesome!

But really appreciate to have made a bigger step forward 👍

[SunnyCrockett]

I have switched back to the original scan_intervals but let the connection_time in the proxy at 0.2 - we will see :)
In addtition, i have created a new pull request for Louisbertelsmann with some fixed for the "moon values" and added the last charging duration.

[SunnyCrockett]

I have set the modbus proxy connection_time to 0.5, that runs without errors over the night. In addition I have changed the scan_intervals of the wallbox yaml this morging. To have up-to-date data while charging I have added an automation that checks the charging status and updates the charging entities every 10sec if the car is charging. You can check/test it if you like:
https://github.com/SunnyCrockett/Sungrow-Wallbox-Modbus-HomeAssistant/blob/DifferentIntervals/modbus_wallbox.yaml

PS: I could not test it yet, my car is full.

[btota]

Had a short test, automation fast update seems to work 👍 , thx. I didn´t changed modbus proxy connection_time, since I've no issue with that - currently I'm experimenting with a second modbusproxy instance for WB, on a haos container lxc+portainer. Works pretty fine!

[SunnyCrockett]

Thanks for the feedback! I created a pull request for my changes including some documentation.

[stargoose77]

Problem solved!!! :-D

While I was writing about my problem I found the issue:

{% if is_state('input_select.set_wb_charger_enable', "Disable") %}
{{disable}}
{% elif is_state('input_select.set_wb_phase_switch', "Enable") %}
{{enable}}
{% endif %}

You need to replace it to charger_enable

So now it works again!

And it's time to say thank you guys! - That's what I was hoping and waiting for, sorry that I did not find the time to help testing it.

Great work @Louisbertelsmann and @SunnyCrockett