Compatible inverters

[kbialek]

Please report here inverter models that work with this tool. This will let me build a database of compatible inverters. Thanks!

Please report:

1. Inverter model
2. Used metric groups

[aresius]

It seems to work with Model: Deye SUN300G3-EU-230 Firmware: MW3_16U_5406_1.53 Metric groups: micro

Thank you very much!

[UltimateGER]

It seems to work with Model: Deye SUN600G3-EU-230 Firmware: MW3_16U_5406_1.56

Thank you very much!

[parkpirat]

1. Deye SUN1600G3-EU-230
2. micro

-> in general working, not finally tested all collected data Did you use the file below as base for the different parameters? This file I've received from Deye service last time.

DEYE_Modbus储能-组串-微逆宁波德业V118.pdf

[kbialek]

Did you use the file below as base for the different parameters? This file I've received from Deye service last time.

Yes, exactly

[K3vb3rt]

Model: Deye SUN800G3-EU-230 Firmware: MW3_16U_5406_1.57

Thanks!

[ivanK0dy]

Hi @kbialek,

As inverters are just rebranded but same HW, I tested on FU-SUN-5K-G05 (Fuji Solar) and get most of information but I miss data from Mobus connected Meter which data are on registers 150-218: PDF Document for Deye by "[parkpirat]" few posts earlier..

Registers dec 150 - 218 ? As I can see your script only pull range 003c-0075. If i try to read it with your toll I get: Day Load Power: docker run --rm --env-file config.env ghcr.io/kbialek/deye-inverter-mqtt r 200 int: 1194, l: 170, h: 4

Meter active power: registers 203 (low) and 204(high) I get: int: 65027, l: 3, h: 254 int: 65535, l: 255, h: 255

How to pull this second range? Or I should create new instance with new range and only read new registers from that range. Thank you

[edvandreas]

Logger Model: Stick Logger LSW-3 (Wifi)

Inverter Model: Deye Sun 12K SG04LP3 EU Firmware: 2005-1128-1807

Works great, reading the data every 10 seconds without problems. Thank you!

[devil33]

Works here with

Model: Deye SUN600G3-EU-230 Firmware: MW3_16U_5406_1.57

Thank you so much!

[RafaelDuncan]

Logger Model: Stick Logger LSW-3 (Wifi)

Inverter Model: Deye Sun 12K SG04LP3 EU Firmware: 2005-1128-1807

Works great, reading the data every 10 seconds without problems. Thank you!

Hello, is it also possible to write data to the Deye Sun 12K SG04LP3 EU? I want to be able to control the adjustments from Home Assistant

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[marcniedersachsen]

Thank you very much for this great implementation. I have successfully tested these two ("brand new ?") Micro Inverters:

Deye SUN-M60g3-EU-230 and Deye SUN-M80g3-EU-230

Metric group = Micro, (I haven't tested ",settings". Guess that will work too :-)

[lpunkt66]

Works for me with version 2023.06.2 👍

Model: Deye SUN800G3-EU-230 Firmware: MW3_16U_5406_1.57 Metric group: micro

Device serial number 3912xxxxxx Inverter serial number 2303xxxxxx

Did't work with 2023.05.4

Thanks very much!!!

[fakehec]

Model:Deye 30kW SUN-30K-SG01HP3-EU-BM3 hybrid with battery Metric: deye_sg04lp3, deye_sg04lp3_battery,deye_sg04lp3_ups

Logger serial number: 2770xxxxxx Inverter serial number: 2304xxxxxx Works ok everything except data from PV3

Please implement PV3 line data in deye_sg04lp3

[Verkalets]

@kbialek thanks!

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[toleabivol]

DEYE SUN-8K-SG04LP3-EU Metrics : deye_sg04lp3,deye_sg04lp3_battery

[Harry4711]

Hi congratulation to the project. Model: Deye SUN800G3-EU-230 Firmware: MW3_16U_5406_2.32-D1 I did create a "deye_sensors_deye_2mppt.py" with the appropriate Value for the above model and intergrated it in your "deye_sensors.py" file as you did with other "deye_sensorsdeye*.py" files. It worked well in an Home Automation environment developed with FHEM If you are intereset, I could upload the file and send further information. I did create own groups to not have to use the "micro" one to be more specific for this model. Best regard

[fschwanzara]

Model: Deye SUN600G3-EU-230 Firmware: MW3_16U_5406_2.32-D1 Metric Group: Micro

Error:

DeyeModbusTcp - ERROR - Response frame has invalid starting byte
DeyeTcpConnector - DEBUG - Received response frame in 1. attempt: 41542b595a434d505645523d4d57335f3136555f353430365f322e33322d44310d0a0d0a
DeyeTcpConnector - DEBUG - Request frame: a51700104500008fde70e90200000000000000000000000000000103003c003945d4c615
DeyeDaemon - INFO - Reading registers [metrics group: micro, range: 003c-0074]
DeyeDaemon - INFO - Reading start

I just wanted to get the MQTT messages to send it over to influxDB/Grafana I let the container run on my Synology - MQTT is on my RasPi.

Update

With setting to Logger Mode AT it works now:

DEYE_LOGGER_PROTOCOL=at
DEYE_LOGGER_PORT=48899

Thank you so much for this Project !!!!

[Harry4711]

TCP ist Not supported any more with this Software version, pleased use AT !! See documentation

Am 12. Oktober 2023 09:56:02 WESZ schrieb Florian @.***>:

Model: Deye SUN600G3-EU-230 Firmware: MW3_16U_5406_2.32-D1 Metric Group: Micro

Error:

DeyeModbusTcp - ERROR - Response frame has invalid starting byte
DeyeTcpConnector - DEBUG - Received response frame in 1. attempt: 41542b595a434d505645523d4d57335f3136555f353430365f322e33322d44310d0a0d0a
DeyeTcpConnector - DEBUG - Request frame: a51700104500008fde70e90200000000000000000000000000000103003c003945d4c615
DeyeDaemon - INFO - Reading registers [metrics group: micro, range: 003c-0074]
DeyeDaemon - INFO - Reading start

I just wanted to get the MQTT messages to send it over to influxDB/Grafana

-- Reply to this email directly or view it on GitHub: https://github.com/kbialek/deye-inverter-mqtt/issues/41#issuecomment-1759206644 You are receiving this because you commented.

Message ID: @.***> -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[voipmonitor]

Hello,

I have SUN-50K-SG01HP3-EU-BM4 which has 4 strings - I have two battery towers with two BMS - I have modified deye_sensors_deye_sg01hp3.py and added BMS1, BMS2, bettery1 and battery2 registry and fixed one signed/unsigned parameter. deye_sensors_deye_sg01hp3.zip

[mrlordziemniak]

Hi i have DTSD422-D3 i can read data, but for example current CT1 when energy is with - value there is still + how to mengae this? and on all Total Positive Energy CT1 CT2 etc is not correct value, any ideas why? PL: Udało się zrobić odczyt z tego licznika, ale nie wiem dlaczego wartości prądu jak są z minusem to dalej pokazuje jak z plusem, tj nie pojawia się minus, oraz pod rejestrami od total positive energy są jakieś głupoty

[xGDNAx]

WR BW-MI600 Bosswerk MW3_16U_5406_2.32-D1

Micro, settings

[omgfreezeur]

Deye SUN-M160G4-EU-Q0 SW: MW3_16U_5406_1.59

Micro, settings

Got it also in HA integraded and can set all the active power througth HA

[xGDNAx]

https://github.com/kbialek/deye-inverter-mqtt/issues/154

[SandimL]

Its working with:

Model: Deye SUN-4K-G Firmware: LSW3_15_FFFF_1.0.9E Metric groups: string, micro

Thank you!

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[jpgnz]

Model: Deye SUN-16K-SG01LP1-EU DEYE_METRIC_GROUPS=deye_hybrid,deye_hybrid_battery,deye_hybrid_timeofuse,settings

Looks to be complete, have left all features at defaults, eg haven't tried writes:

# DEYE_FEATURE_MQTT_PUBLISHER=true
# DEYE_FEATURE_TIME_OF_USE=false
# DEYE_FEATURE_ACTIVE_POWER_REGULATION=false
# DEYE_FEATURE_SET_TIME=false

[matt-kubica]

Deye SUN-20K-SG01HP3-EU-AM2 (version of SUN-6/8/10/12/15/20K-SG01HP3-EU-AM2) seems to be working fine with deye_sg01hp3, deye_sg01hp3_battery, deye_sg01hp3_bms, deye_sg01hp3_ups, settings metric groups.

Haven't tried writes and features besides mqtt reporting. Configuration was mostly default (apart from the envs I had to change).

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.