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

That is Retrofit. And it seems that it does have impact, the only user so far that for example gets the “battery discharge limit” to be respected with modbus, also has a Retrofit installation.

I honestly can’t see any logical reason why having a third party inverter AC coupled to the Sigenergy system would influence the temperature sensor readings inside the battery cells. I wonder if it could instead be related to differences in inverter or battery hardware revisions, firmware versions, or system configurations done by installers. But I’m certainly no expert, just thinking out loud.

Me either, but the Modbus implementation clearly uses this config for testing, since multiple things work in this setup but not in the “standard” setup.

I see the app was updated 12 hours ago, and the minimum cell temperature has been replaced with “average”. It would be great if the “min” value could be retained alongside “average”, as it was displaying the correct value for some users, including me, before the update. :neutral_face:

Looking for testers for v0.7.0, just released as a test version

Hold the battery while the car charges, without leaving AI mode
Two new flow cards on the Plant device:

  • Hold the battery at its current level: stops the battery discharging.
  • Release the battery hold: lets it discharge normally again.

Unlike the max discharge limit (which AI mode ignores) and remote EMS (which drops you out of AI mode), this keeps AI mode running. It works by raising the battery’s discharge cut-off to just below the current level, and the release card puts your original setting back. The original is saved on the device, so it survives a Homey restart. Solar can still charge the battery while it’s held.

Note that while the battery is held, the house is also supplied from solar and the grid instead of the battery.

Example: When the car starts charging → Hold the battery. When it stops → Release the battery hold.

Thanks to the community tip about the discharge cut-off that made this possible!

Min cell temperature is back
In 0.6.6 I replaced Min cell temp with Average cell temp because it only ever showed 0. It turns out it works on some systems, retrofit installs among them. It now comes back automatically on batteries that report a real value, and stays hidden where it only reads 0.

Awesome Richard, I have downloaded the new test version and will get back to you later today when I have tested the battery hold function :ok_hand:

Unfortunately it did not work this time either. Just the same issue, nothing happens..

Thanks for testing! I found one thing: the hold set the cut-off one percent below the current level, so the battery could still discharge 1–2 % before it stopped. v0.7.1 holds at the current level instead, so it should stop within a percent.

I also added more detail to the log. Could you update to 0.7.1, run the same flow while the car charges, let it run for at least 5–10 minutes, and then send a diagnostic report? The log will show whether your system actually stores the new cut-off and whether the battery keeps discharging during the hold. It would also help to check in mySigen whether the discharge cut-off SOC changes when the hold starts.

Is it ok if I activate the flow manually (test) and then activate my hot water heater instead? It uses 3kW and my house is idling aroung 0,5-1kW without that, so it’s easy to follow the battery power discharge when the heater is on. I have done like this previously since my car is not home for the moment.

Yes, any larger consumer works.
You can also check the Sigenergy app: Settings / System settings / Energy Management settings / Battery level settings. Here you can see the discharge cut off SOC setting - the one this action updates.
After your test you can send me a diag report if it doesnt work.

It worked this time! :partying_face:

I activated the flow and started my hot water heater, and direct checked the Cut-off SoC for the battery in settings, and it instantly changed (see below pics). The first maybe one minute, nothing happened and the Sigenbat continued to discharge at ~3,5kW. But then it stopped (started idling) and netimport ~3,5kW started.

I´m guessing the ~minute for it to stop discharge is because battery SoC was maybe 71,3% and needed to get below 71%?

Then I inactivated the flow, Cut-off SoC went instantly back to 0-100% and Sigenbat started to discharge again :ok_hand:

v0.8.0 is out as a test version

New flow cards on the Plant device:

  • Set max solar power / Remove the max solar power limit. Caps solar production, for example while the feed-in price is negative. Works in AI mode too. Unlike a grid export limit, it also reduces solar charging of the battery.
  • Set backup SOC. The reserve kept for power outages. Note: it does not stop the battery discharging in AI mode. Use the hold card for that.
  • Set charge cut-off SOC. The level the battery stops charging at, for example 80 % in summer.
  • Conditions: Battery is held and EMS mode is ….

Hold the battery now stops discharging within a minute or two. Before, it set the limit a full percent or more below the current level, so the battery kept discharging for a while first, which is what some of you saw. Now the gap is set to 0.2%.

Hi Richard

, thanks for the app (I’m on 0.8.0 test, Plant device, firmware V100R001C21SPC117).

My Sigen normally runs in “Time-based control” (TOU) with a schedule set in mySigen. I tested “Force charge battery from grid”, and it works fine. After the test I used “Turn remote EMS off”, but the plant did not return to TOU: ems_work_mode stayed on “Max self consumption”. I had to switch back to TOU manually in mySigen.

The card “Set remote EMS control mode” only offers the remote EMS modes (Standby, Max self consumption, Charge/Discharge…), so I can’t restore TOU from Homey.

Would it be possible to add one of these:

  1. an action card “Set EMS work mode” (TOU / Max self consumption / AI …), or
  2. an option on “Turn remote EMS off” that restores the previous work mode.

Without this, any flow that uses force charge leaves the system out of TOU. Thanks!

Thanks for testing and for the clear report!

Unfortunately, the app can’t fix this. In Sigenergy’s Modbus protocol, the EMS work mode (TOU, AI mode, Max self consumption, Custom) is read-only. The only mode that can be set over Modbus is remote EMS. When remote EMS is turned off, the firmware falls back to Max self consumption rather than the previous mode. We see the same with AI mode. So neither a “Set EMS work mode” card nor a “restore previous mode” option is possible until Sigenergy exposes the work mode as a writable register.

For me, again, a confirmation that no one really thought through or used the Modbus design they have dreamt up :smiling_face_with_tear:

I sent a lengthy email to Sigenergy support, explaining to them the challenges of using their Modbus API, lets see if I get a reply.