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

Has anyone been able to create a flow where the battery automatically charges whenever the EV charger is plugged in?

When I start the flow with the EV charger, when I select “then” the Sig battery is not listed…

New to homey so go easy on me :sweat_smile:

Unfortunately there is no support for “Then”-cards for the battery in the Sigenergy-app. However, if you want to charge the Sigen-battery with the car (EVDC) there is manual modes in mySigen to do this. And for information, Sigenergy recently confirmed that AI-integration of EVDC is going to be released in August.

Hopefully EVDC will be much more user-friendly after this.

Ah thanks for letting me know.

I am aware of the manual control however, as I am with octopus which dynamically schedules my cars charging schedule, it would mean an awful lot of legwork for me to manually force the battery to also charge…

You mention about Sig introducing an update to the charging, have you got a link regarding this?

Not a link, but this is from Sigenergy’s beta forum in their Community, after the mySigen beta 4.0 was closed (which I was a part of).

I’m hoping that means they can simultaneously charge the EV and home battery…

To me it reads like it’ll do it’s own selective charging slots rather than the above. I hope I’m wrong!

When I want to charge the battery and my car at the same time with for example PV surplus, I manually override AI with Self-consumption and change the charging power on EVDC to example 5kW. If I get 10kW PV surplus, the other 5kW will automatically go to the home battery.

Regarding the AI integration, I just think we will have to wait and see which functions they will bring. The post from the beta forum is more of a confirmation that they finally will focus on EVDC, because it has been neglected way too long already.

I first thought that you meant “charging the home battery with the car battery”, with V2x. Like I do right now..

I have promised another user to look into adding THEN cards after my vacation. But from what I know, currently, there are not many meaningful things you can do. If you via Modbus change mode, for instance, from AI to self consumption, then I’m told it doesn’t work to switch back via Modbus, which makes it pretty useless.

@Richard_B I can’t reach the EV AC Charger anymore. It worked without any issues before, but after a couple of weeks it suddenly lost its Modbus connection.

The EVAC is configured as Slave ID 1. The inverter and battery use Slave ID 2 on the same IP/port and are still working without any problems.

The EVAC itself is online in mySigen, and Sigenergy has confirmed that Modbus Slave ID 1 is enabled.

Homey keeps reporting:

2026-08-08 09:26:28
Error: Device registry read failed: Timeout: Req timed out
at #emitError (/app/lib/base.js:644:36)
at #handleModbusError (/app/lib/base.js:626:24)
at #readDeviceRegistries (/app/lib/base.js:479:42)
at async #pollDevice (/app/lib/base.js:300:13)

I also verified that the IP is reachable and TCP port 502 is open.

Any idea what could cause the EVAC device specifically to time out?

@Richard_B - I have the exact same problem as @Richard_Jarbsjo and everything was connected before. I just changed wifi from a temporary one and now i cannot connect it to Homey anymore.

I have tried to change ip adress on each enitity, and also deleted everything and reinstall, but nothing works.

Seem there no support anymore?

Would love to see an PV forecast card.
That will cover the exact nummer as visible in the Sigen app.

Would be great to calculate/anticipate with such number. Think of dumb ev-charging charging, running DHW-boiler, extra heat in the floor and do on.

Hi all,

Seems the grid value is set to 0 at all time since about 19 sep. Anyone who has the same issue?

Perhaps a new modbus protocol?

Hi Richard! Again, thank you for developing this great app.

It’s working really well, but I’ve run into a limitation regarding dynamic energy tariffs that I hope you can help with.

I am trying to automate my Sigenstor (27 kWh) using Homey Advanced Flows based on dynamic hourly prices (Zonneplan) and weather forecasts for my heat pump. Currently, the app provides excellent action cards to set or remove charge/discharge limits (acting as “brakes”).

However, when my Sigenstor is in ‘Self-Consumption’ mode and the grid price drops below zero during a cloudy day, simply using the card “Remove the max battery charge power limit” doesn’t trigger the battery to start charging from the grid. It just removes the limit and waits for PV power.

To fully utilize dynamic tariffs, Homey needs to be able to act as the “gas pedal” as well. Would it be possible to add the following Modbus action cards (THEN) in a future update?

  1. Force Charge (from grid): An action card to actively command the inverter to start charging from the grid (preferably with a settable kW power rate).

  2. Set Operation Mode: An action card to switch the Sigenstor’s operation mode via Homey (e.g., switching between Self-Consumption, Time of Use, or Fully fed to grid).

Adding these would make the app the ultimate EMS tool for anyone with dynamic tariffs. Let me know if you need any testing or logs from my side. Thanks in advance!

Hi @Richard_B. When I´m using the “discharge limit” for Sigen-battery, the limit doesnt takes effect. I have tried both "0"kW and "0,2"kW but when checking my battery (both in Homey and Sigen-app), the battery discharge limit remains unchanged - battery continous to discharge as normal.

This is also earlier reported in GitHub. Sigenergy v0.6.2 – Battery discharge limit 0 kW not respected · Issue #16 · ricott/homey-com.sigenergy · GitHub

Hi all, i need some help with the following. I want to make a flow that turns on a fan when the battery reaches a temperature above 35 degrees celsius and turns it of again when it drops below 30 degrees celsius. I tried several things but it seems that i have the wrong variable of there is no data coming.

Could someone push me in the right direction ?

Thank you all in advance.

ps. it turns On fine, but Off is the thing i’m having issues with.

The timeout means the inverter answers on Modbus but gets no reply from the charger behind it. Unit 2 works on the same connection, so the network itself is fine. A few things to check: the EVAC device in Homey must use the inverter’s IP, not the charger’s own IP, with the charger’s slave ID. Check in mySigen that the charger’s Modbus address is still set and that it’s still linked to the plant. Restart the charger and the inverter. If you changed Wi‑Fi, make sure the charger is back on the same network as the inverter. If it still fails, please send a diagnostics report from the app.

Sigenergy doesn’t publish the forecast over Modbus. It only exists in their cloud, so the app can’t read it.

The app didn’t change anything around 19 Sep, so this is probably on the Sigen side (a firmware update or the grid sensor). Does mySigen still show grid import and export correctly? Please send a diagnostics report and I’ll check what the sensor returns.

This is possible through Sigen’s “remote EMS” registers. I can add cards for force charge from grid (with a kW limit), standby (hold battery) and max self-consumption. The native TOU and AI modes can’t be set over Modbus. Note that turning on remote EMS overrides the mode you picked in mySigen until you turn it off again. I can post a test version.

The command is accepted by the system but doesn’t seem to take effect in AI or self-consumption mode, even though Sigen’s spec says it should. I’m looking at controlling it through remote EMS instead and will post a test version.

All is okay now!

Thank you for responding and developing this app.

That would be great

One other thing, why is the battery device pointing to a very odd number of SoC?

While the SoC is 7% the battery points out to 18%.

It is available in the test version I released yesterday :+1:

The battery device reads that batteries SoC, the plant device reads the overall plant registry (which could be more than one battery). Assuming the readings are current, i.e., if you click the capability, you can see when it was last updated, then it is a glitch in Sigenergy. Their Modbus implementation is not of the best quality.