Does it work with high voltage inverters?

[bsafh]

I presume this does not work with SUN-10K-SG01HP3-EU-AM2 ?

That's a high voltage inverter, serial no. starts with 23xxx, so presumably it's not protocol Version 5, but 4? Or another?

Futhermore the sensors/registers are different for the HV inverters...

[davidrapan]

Hi, first I have to ask where are you coming from? Are you a "first time user" or you are already using implementation from the @StephanJoubert? Cause theoretically this integration should work for all the same devices.

That being sad, it's really tested only for the device I own. So it has to be tried to be really sure.

On the other hand if definition file for your device is missing but you have the registry list i could try to add it. ;)

Wish I could help you more.

Have fun.

[bsafh]

I'm trying to use the implementation from the @StephanJoubert, but that does not work for me either.

Over in his repository there is a discussion about that, and someone has supplied an incomplete custom_parameters.yaml for the high voltage inverters (everything related to time of use is missing, e.g.)

But I can't get that far, as the integration does not connect to the wifi dongle at all, the serial number of the inverter starts with 23xx, the serial number of the dongle starts with 29xx - both are not listed as working with protocol V5 in the readme from https://github.com/StephanJoubert. There is an omnious remark to try v4, but it's not explained anywhere how to do this.

The inverter is registered with Solarman Business App, and all values show up there.

[bsafh]

Inverter information
Inverter serial number 2312122xxx
Firmware version (main)
Firmware version (slave)

Device information
Device serial number  2908548xxx
Firmware version LSW3_15_FFFF_1.0.9E

[davidrapan]

Ok, so try it with my integration, turn on debug logging (you'll see it when you open integration detail view in the menu on the right, last item) and then restart HA. Give it few minutes and then send me the log (It will download the file when you then turn off the debugging).

Then we will know more. 😉

Have fun.

[bsafh]

I'll try tomorrow ...

[bsafh]

I don't have the register list directly, but the definitions can be found in https://github.com/kellerza/sunsynk/blob/main/src/sunsynk/definitions/three_phase_common.py and https://github.com/kellerza/sunsynk/blob/main/src/sunsynk/definitions/three_phase_hv.py combined.

[bsafh]

And there is someting here:

• https://github.com/kbialek/deye-inverter-mqtt/blob/main/docs/metric_group_deye_sg01hp3.md
• https://github.com/kbialek/deye-inverter-mqtt/blob/main/docs/metric_group_deye_sg01hp3_battery.md
• https://github.com/kbialek/deye-inverter-mqtt/blob/main/docs/metric_group_deye_sg01hp3_bms.md
• https://github.com/kbialek/deye-inverter-mqtt/blob/main/docs/metric_group_deye_sg01hp3_ups.md
• https://github.com/kbialek/deye-inverter-mqtt/blob/main/docs/metric_group_settings.md

[bsafh]

Actually I found the register list

MODBUSRTU三相高压储能通信规约V104（高压）(3)(1)1111_SG01-HP3-AM2.pdf

[davidrapan]

Great, I'll try to integrate it as soon as I can but we still need to find out if there is even any communication happening (cause of that V5 or V4 matter).

[davidrapan]

@bsafh I added file for your device in: b53e902

[bsafh]

tested it, using "main" in the version dialog (HACS download): protocol 5 works!

But ... config flow is ... not commentet, so I have no idea what to fill in:

[bsafh]

I managed to get around this by just copying the file deye_sg01hp3.yaml over custom_parameters.yaml (which was alread configured from the now overwritten config flow from @StephanJoubert 's version.

It does recognize the inverter :-) And it does read the new definitions.

But it does not contain any "Time of use" information, neither the switcg for that nor the timetable itself. And there are no switches (e..g switch priority_load on and off - oops, priority_load is not even there?)

[davidrapan]

Time of Use is not read as far as I know in any of the inverter definition files yet.

Instead of reconfiguring, try remove and then add device again. I'll look into why configuring flow is missing the description of config values.

But I'm glad that it at least tries to read any values, that's a good sign.

Edit: So yeah, those descriptions of configuration items when you click on the "Configure" button never worked. it's simply not there. So I advise to you really re add the device.

[bsafh]

So I advise to you really re add the device.

how do I get rid of the old devices?

For the switches I have found this:

deye-modbus.zip

[davidrapan]

It's really not about the registry addresses but about implementation in the integration. There are not entities for it. I do want to eventually add support for as much things as possible but my focus was currently on the connection stability.

Anyway for removing the device:

[Mights001]

Hi i use this integration for a HV 50KW Deye too, works very well. Some Entitys you have to set a other Scale is in the Documentation. I will attached this new Version what i get from Deye since 2 Weeks. 【b】30240301001287-使用说明书-储能三相-sun-(25-50)k-sg01hp3-eu-bm4-德业英文-封面彩印-封面封底157g-内页70g铜版纸-142.5x210mm-ver2.2.pdf

[davidrapan]

Hi there, thanks for your comment. I was trying to adjust the scaling according to the previus doc but is possible that I missed some of them so if that's the case let me know which one and I'll correct them. 😉

[Mights001]

for Example

• Battery Voltage LV 0.01 - Battery Voltage HV 0.1

You can find it in the Manual on the 5t Row

Also what i add to your Config is the Gen Port, because a many useres from my side need this for the Micro Grid Input.