Dacia Spring + GoodWe GW10K-ET Inverter

[andreicocari]

🔧 Issues with Battery Emulator + Growatt GW10K-ET Inverter + Dacia Spring Battery

Hi everyone,
I'm helping my uncle set up the following system:

🛠️ System Specs:

• Inverter: Growatt GW10K-ET (3-phase)
• Solar Array: 10kWh
• Battery: Dacia Spring EV battery
• Battery Emulator: GitHub project running on LilyGo T7 (ESP32)

🔌 Power Supply:

• Lily board: 5V 1.5A
• BMS: 12V 5A

👨🏻‍💻 Code wise:

We activated

• #define CMFA_EV_BATTERY (as per the Dacia Spring wiki)
• #define BYD_CAN (as per the GoodWe inverter wiki)
• #define HW_LILYGO
• #define PRECHARGE_TIME_MS 500
• #define CONTACTOR_CONTROL

---

✅ What’s Working:

• Inverter detects the battery and shows Battery Status: Normal but always Battery Type = N/A. Sometimes, it shows as BYD HVS but for brief periods of times before it disappears.
• Solar production is working normally.
• Once, the system discharged the battery and powered the house for a few hours only when Battery Type = N/A.
• When BYD HVS briefly appeared as the battery type, discharge stopped.

---

❌ Issues We're Facing:

1. Emulator stays in yellow state

• Lily LED blinks yellow after boot.
• After a soft reset (2s press), LED blinks green for a moment, then turns yellow again.
• Emulator screen stays yellow, no charging or discharging occurs.

---

2. Inverter can't lock onto battery

• Inverter briefly detects BYD HVS, then reverts to Battery Type: N/A.
• Selecting BYD HVS via Quick Setting makes it search and then silently fail.
• BYD HVM shows up and asks for confirmation, but no charging/discharging happens after selecting.
• Same for BYD HVL — selectable, but doesn't work.

---

3. Relay control pins do not work

• GPIO 25, 32, and 33 are connected per Dacia Spring schematic.
• Emulator does not activate battery relays.
• No electrical activity on those pins (confirmed via measurement).
• Currently hardwired the relays to stay closed so the inverter sees the battery.

---

4. SoC and voltage mismatch

• Battery started at 285V, which should be ~65% SoC.
• After running for a while, Lily showed 0% SoC at 244V.
• Spring battery profile (approx.):
  • 0% SoC @ ~218V
  • 100% SoC @ ~300V
• BYD HVS profile:
  • 0% @ ~250V
  • 100% @ ~350V
• → These ranges are not compatible, causing false readings.

---

5. Battery is now stuck

• No longer charging or discharging.
• Charging voltage = 0V, SoC = 0% in Lily, battery at 244V.
• Tried SoC offset -10%, now reads 9.9%, but still not charging, nor discharging.

---

❓ Questions:

1. How can we configure a custom SoC curve for the Spring battery (218V–300V)?
2. What causes the emulator to remain in the yellow state?
3. Why aren't GPIO 25/32/33 controlling the relays? Bug or config?
4. Should we use a custom battery config instead of BYD?
5. Has anyone successfully used the emulator with Growatt GW10K-ET?

---

Thanks in advance for your support — amazing project, hope to get this working! 🙏

[cristianiftodewdt81]

Hi Andrei!
Have you managed to solve the problem? Can we find an older firmware version somewhere? Some people have encountered issues with the newer firmware updates.
I received the inverter like this as well—it doesn’t detect the battery in the app, even though the ESP LED is green.
If you happen to find any firmware, please email it to me or let me know here.
Thanks in advance!
Cristian cristianiftode@wdt81.online

[bellapanko]

I have exactly the same set up, same inverter and same battery, communication is working and also the precharge and poles contactors are being activated regularly, so perhaps with the latest updates it works, but i still have one issue, the inverter receives a charge and discharge max limit to 0A and doesn't use the battery, without this limitation it should work properly, in order to workaround this problem, i set up the inverter to be used with a lead acid battery (you can do it only with Solargo app version 5.1.3), and configured the BE inverter setup on NONE, in the solargo APP i configured the battery as 5blocks 294V charging voltage and 90% discharge deepth) now looks working well, (since yesterday). but i will try further to have all the communication working properly