[APP][Pro] Sigenergy - Home energy powered by AI

Yes, you’re absolute right, last refresh was 15 days ago.

Did change the Modbus Native address 247 into 1, now is looking better.

I should clarify, this makes most sense to check for values that change frequently like power. Semi static values that rarely change shows the last time the capability got a new value. But charging state should change pretty frequently anyhow, so 15 days is off. Mine is 1h currently while power is a few seconds ago.

There is one user on the Sigenergy Sweden Facebook page that claims that this works for him, even in AI mode. It’s really strange, the only difference between our setup is that he has Retrofit and I’m not. We both have the integrated inverter.

But for me and many others that have commented, it doesn’t work with the exact same settings as the author of this post.

I have added more actions in the test version of the app and update the first post of this thread. Keen on understanding if this approach works for setups without retrofit.

Hi Rickard. I am the user that made the Facebook post that @Jens_Edberg is refering to. I can use the charge/discharge settings in your app even when the Sigenstor is in AI Mode. If i can be of any help by providing some data, just reach out.

I just tried (installed your latest test version earlier), no change for me. It still doesn’t work.

Hello,

I’m having the same issue as other people are reporting with the battery discharge limit not working.

I just did a test and sent in a report.

Diagnostic ID: 8428bd4a-fa21-4be7-9b77-9fe58204fc85

My system is in AI mode, and no retrofit. Other control like limiting export works fine though.

/Hass

Thanks for the diagnostic report, it helped!

The log shows the app wrote the 0 kW discharge limit to the inverter at 18:36:11, and the inverter accepted it without an error. The limit was removed again at 18:36:51, though, so it was only active for about 40 seconds. The inverter may need longer than that to react. Could you try again and leave the limit on for a few minutes?

Another user has reported that the limit is ignored while the system is in AI mode, so it may not work for you either. If it doesn’t, use remote EMS on the Plant device:

  • When you want to hold the battery (for example while the car charges): Set remote EMS control mode → Standby. The battery stops charging and discharging.
  • When you’re done: Turn remote EMS off.

Note that when remote EMS is turned off, Sigenergy goes back to Max self consumption, not AI mode. Its Modbus interface has no way to select AI mode, so you’ll need to switch back in the mySigen app afterwards. So essentially this is useless :smiling_face_with_tear:

Version 0.6.5 (in certification now) logs the limit the inverter actually stores. If you test with it, a new diagnostic report would show exactly what happens.

Thank you for the quick reply Richard :slight_smile:

You’re right, I created another flow to remove any limits being stored.

I just did a new test and report with a longer testing time:

20:54 - Created a testflow and set the battery discharge limit to 0 (flow card indicates success, no errors).
20:59 - Did a final check in Sigenergy to verify if the limit applied. It did not, and discharged continued without seeming to pause at any point.
21:00 - Report generated.

Report ID: 0e72b3e8-2958-4c68-b93a-6d33f868122e

Please let me know if there’s anything else I should test :slight_smile:

Thanks for testing again, this report gave a clear answer.

With 0.6.5 the app reads the limit back from the inverter after writing it. Your log shows:
Set ESS max discharging power to 0 kW (readback 0 kW, EMS work mode: AI mode)

So the inverter stored the 0 kW limit, but in AI mode it doesn’t enforce it. AI mode manages the battery itself and ignores the limit. Nothing more the app can do there.

Think we need to ask Sigenergy support for answers…

How is it that it works for @Niklas_Wannebring in AI mode? Is it because he has a retrofit installation?

Your guess is as good as mine. No clue why, but it’s a known difference between the installations, which may explain the different behaviour.

Sigenergy’s Modbus implementation is pretty subpar, as if they gave ownership to a junior and told them they weren’t allowed to use AI.

Regarding my first question. I’ve got it working with a workaround. But i think the following had something to do with it, see attached screenshot. The minimum Cell Temperature hasn’t updated in like 4 months.

Right, this is another example of the quality of Sigenergy’s Modbus implementation. The field is in the spec and described the same as the maximum cell temperature, but it doesn’t work. I have never gotten a reading from it, but kept thinking it would start working someday - but I guess we can remove the capability.

9 months ago (since installation) :sweat_smile:

It seemed to have worked at @Undutchable ?

Both min. and max. cell temperatures are updating for me frequently. It’s been like this since day one of using the app. Please don’t remove it! :sweat_smile:

This is literally the last thing I’m waiting for and that I need from this app. Hopefully it will be possible in the future.

Do you have a retrofit installation?

Hi,

Not sure what you mean by “retrofit”? If I had a previous installation?

I started with SolarEdge inverter and 6.6 kW of panels, no battery. Then a year ago I added 24 kWh Sigenergy with another 7 kW of panels. The old SolarEdge (and panels connected to it) are AC coupled to Sigenergy inverter and the newly added panels are DC coupled. As a result I see two sets of solar in the MySigen Android app. But I’m not sure how all of that could affect the battery cells temperature readings(?).