Skip to content

Navigation Menu

Sign in
Sign up

What hardware are you running SEM with? #103

traktore-org started this conversation in Polls
Discussion options

We'd love to know what setups are out there! This helps us prioritize testing and new features.

Please comment with:

Inverter: (e.g. Huawei SUN2000, GoodWe ET, Fronius Symo GEN24, Enphase IQ7+, SMA Tripower, SolaX X3, DEYE SUN-12K, ...)

Battery: (e.g. Huawei LUNA2000 10kWh, BYD HVS 10.2, Tesla Powerwall 2, Sonnen eco8, LG RESU, ...)

EV Charger: (e.g. KEBA P30, Easee Home, Wallbox Pulsar Plus, go-eCharger Gemini, Zaptec Pro, ...)

EV: (e.g. VW ID.4, Tesla Model 3, Hyundai Ioniq 5, ...)

Tariff: (e.g. static, Tibber, Nordpool, aWATTar, Groupe E Vario, ...)

Country:

SEM version:

What works well?

Any issues?


Example:

Inverter: Huawei SUN2000 10KTL
Battery: LUNA2000 15kWh
EV Charger: KEBA P30
EV: VW ID.4 Pro
Tariff: Static (EKZ, Switzerland)
Country: Switzerland
SEM version: v1.2.3
Works well: Solar surplus charging, dashboard, notifications
Issues: None

You must be logged in to vote

Replies: 9 comments 3 replies

Comment options

I would like to use this integration with m y Shelly EM monitor (capturing Solar Power produced) and a SmartEVSE; both running MQTT towards Homeassistant.
Unfortunately, this config doesn't seem to be supported.
Apart from this (and not my first priority in this), are 2 Anker Solix Solarbanks 3.

You must be logged in to vote
0 replies
Comment options

Hi @Ton-O,

That setup should work fine! SEM reads its data from the Home Assistant Energy Dashboard, so it doesn't matter how your sensors connect — MQTT, API, native integration — as long as they show up in Settings → Dashboards → Energy, SEM will pick them up automatically.

I actually use a Shelly myself, works great with SEM.

For getting started, check out the Quick Start Guide and Setup Guide. If you run into issues specific to SEM, feel free to open an issue.

You must be logged in to vote
2 replies
Comment options

Thanks for the fast reply.
I followed the setup guide, but it did not autodetect anything, so had to manually fill in the parameters.
During that, some parameters simply weren't (or at least "seemed" to be not) available.
I then abandoned this attempt and created a simple automation that feeds the Shelly MQTT-data into SmartEVSE via Home Assistant.
Works okay, though less fancy compared to SEM;-)
P.s. I think the energy dashboard was actually the issue for me; did not configure that in HA.

Comment options

Hi everyone
Nice integration in deed. My setup is:

Inverter: Solax X3 G4 Hybrid 10 kW
Battery: Solax 12kWh
EV Charger: 2 x Easee
EV: MB B250e + Mazda MX-30
Tariff: Dynamic Nordpool/Tibber
Country: Sweden
SEM version: v1.6.12
Works well: Just installed, still don't know
Issues: Only one EV charger in dashboard. I'm not sure which entity manage my battery. I use Solax modbus due several scripts.

Comment options

Hi @traktore-org / Guido

Just to be sure that you know what I use:

2 Inverters: Growatt MOD9000TL3-X and a Growatt MIC2500TL-X
2 Batteries: Sessy 5Kwh (both, so total 10Kwh)
2 EV Chargers: Both are Wallbox Pulsar Plus
EV: Audi Q8 etron and a Mni SE
Tariff: Dynamic NL Tibber
Country: Netherlands
SEM version: v1.4.6
Works well: Solar surplus charging, dashboard, notifications
Issues: Translation issues

You must be logged in to vote
0 replies
Comment options

v1.5.0 Released!

Thanks everyone for sharing your setups — it directly helps us improve SEM!

What's new in v1.5.0:

  • GoodWe battery SOC fix — if your battery SOC was showing "unavailable" on GoodWe (or any integration where battery power and SOC sensors have different naming prefixes), this is now fixed with smarter auto-detection via the device registry (Unable to resolve battery Soc #174 )

  • Quality Scale Platinum — the integration now meets all 54 Home Assistant Integration Quality Scale rules. Better error handling, proper async I/O, typed code, and cleaner entity management.

  • Translation improvements — Dutch translations updated (Zelfvoorziening, Laadafvlakking). Help with other languages? See Help wanted: Complete translations for 9 languages (cs, da, fi, hu, no, pl, pt, ro, sv) #179 !

If you're running GoodWe, Growatt, or any non-Huawei hardware — please update to v1.5.0 and let us know if battery SOC detection works correctly. If not, share your diagnostics (Settings → Integrations → SEM → ⋮ → Download Diagnostics) and we'll fix it.

Update via HACS → Updates → Solar Energy Management → Update.

You must be logged in to vote
0 replies
Comment options

Hi, I installed SEM and my system is: Deye Sun12K inverter, with 2x ~17kWh seplos batteries and a tesla with easee charger and hopefully someday also my id buzz when an integration is again available.

SEM looks VERY promising, however for now it is running in read only mode, so I can see how it works.

For some reason SEM doesn't recognize my battery SOC even though SOC is available in the energy dashboard.?
And there doesn't seem to be a way of telling SEM what entity to use for battery SOC?

Other than that, I haven't found any problems so far
Screenshot_20260630_004657_Home Assistant

Screenshot_20260630_010949_Home Assistant
You must be logged in to vote
0 replies
Comment options

Hi @praun — thanks for the detailed write-up, and welcome! Your report turned into a fix.

You were right on both counts: SEM's SOC auto-detection didn't match the Deye Sun12K + Seplos layout, and there was no way to tell SEM which SOC entity to use. That manual override actually existed in the backend but had no control in the UI — so it was unreachable.

Fixed in v1.7.4-beta.7 (just released): the Config tab → Battery section now has a Battery SOC sensor picker. Point it at your SOC entity (the one that shows in the Energy Dashboard) and SEM will use it directly — no need to wait for auto-detection. It takes any sensor, so it works even if your SOC entity doesn't carry a device_class: battery.

It's a pre-release, so enable pre-releases for SEM in HACS to see it (HACS → Solar Energy Management → ⋮ → Redownload → toggle "Show beta versions").

To also get auto-detection working out-of-the-box for Deye/Seplos setups (so future users don't have to set it manually), could you share:

  • the exact entity id of your battery SOC sensor, and
  • your battery power entity id (the one in the Energy Dashboard)?

That'll let me teach the auto-detector your naming pattern. Tracking it in #550. Thanks again!

You must be logged in to vote
1 reply
Comment options

Hi Traktore! I finally got around to write a reply, sorry for taking so long!

So first of all, I want to make clear that I am by no means a coder or developer, so maybe the things I bring up here is just rubbish and doesn't make any sense, so please bare with me. But I have been looking for something like SEM for a very long time, so if I can do anything to support your amazing development, please let me know.

My battery are now showing fine in SEM. So that's awesome.

To answer your question about entities.

So, The Deye inverter has become widely used in Denmark, due to some pretty large group buys by a large Facebook community, sparking many dyi projects, like my own.
To use Dye with HA it's best to use "klatremis" esphome Integration for Deye/HA it communicates via modbus/esphome and is very stable and have fast update frequency, compared to the solarman integration that utilize the Deye cloud.
You can find the klatremis integration here, for info about entities in general.

https://github.com/klatremis/esphome-for-deye

The entity for soc is "battery capacity" it would have different prefix names based on what your esphome device name is I guess.. mine is:
sensor.deye_inverter_sun12k_battery_capacity_2

The battery power sensor from my klatremis is:
sensor.deye_inverter_sun12k_battery_output_power_2

For some reason the battery SOC from klatremis wasn't recognized by the energy dashboard, because of state class or history or something, so I had to make my own sensor to make it work in the energy dashboard. After your fix, I just added the "battery capacity" sensor to SEM and it worked from there on.

Also here in Denmark we have some amazing integrations for electricity and tariff prices
The "energi data service" and "strømligning" integrations maintained by the same person, offer Nordpool prices + local tariffs + extra fees for my electricity dealer. Including a 5 day AI forecast.

Energi Data Service integration (EDS):
https://github.com/MTrab/energidataservice

Strømligning integration:
https://github.com/MTrab/stromligning

I am mentioning this because it seems that SEM only reads the current hour price from my EDS entity and not the coming prices for the day or the forecast, or maybe I am just looking in the wrong place. Maybe see my screenshot:
Screenshot_20260722_122554_Chrome

So tonight and today I took SEM off read only mode, to see if it would work as intended. But I had to put it back on read only mode, because I couldn't get it to charge my car, and I think maybe it was (partly?) because of the missing energy prices?

I had it set to, solar + cheapest hours, but it would only start the charging with excess solar. And I thought that the "time.sem_charger_ev_charger_target_time" was meant to tell SEM when the car had to be done reaching the "charge taget" / "at least" setting. But no matter how I set that setting the charging wouldn't start.
Another thing, I am using the car integration (tesla) to control the charging A and it has the ability to go all the way down to 1A wich is very useful when charging only with excess solar, but it seems that SEM is only made to go down to 6A, maybe this is something, that could be changed someday ?

Also I am very curious about if SEM is able to unload from the home battery to grid, in case the prices are high ?
I have excess battery capacity, and for the price I paid for the batteries I could easily sell from them during some periods of the day. And make the ROI a good bit better. But mostly here in Denmark the prices are much higher in the evening /"cooking zone" i.e from 17 to 21 ish, than in the morning, and it would be awesome if SEM to some extend, could predict how much to sell from the batteries based on expected price, energy needed during the night and next day solar production. I don't know if this is already possible or something you have in mind making?
I have some half baked system for now that sells excess battery capacity in the morning and I am pretty sure SEM would need to know further control entities to be able to force offloading from battery to grid.

If you should need any further details and if I in anyway can help, please don't hesitate to reach out to me.

Comment options

Hi @zlakes01 — thanks for sharing your setup! Both of your points are handled in the current builds (you're on v1.6.12; a lot has moved since). Quick rundown:

Two Easee chargers — both can show on the dashboard.
SEM fully supports multiple chargers (each gets its own card + surplus distribution, per-charger plans, and per-charger vehicle SOC). Seeing only one usually just means only one was added during setup. On the latest build you can add the second one right from the dashboard: Config tab → EV chargers → + Add charger, then wire its entities. No need to go through the native integration flow.

Solax battery — SEM reads it automatically, and you can now see/set the entities.
Solax (solax-modbus) is a supported layout — SEM auto-detects battery power and SOC from your Energy Dashboard. If your SOC ever shows unavailable, the newest build adds a Battery SOC sensor picker (Config tab → Battery) so you can point SEM straight at the entity. The battery discharge/control entity is likewise auto-detected from the Solax modbus number entities and is visible/selectable on the Config tab (Battery section) — so "which entity manages my battery" is answerable right there in the UI.

One thing to do first: update from v1.6.12. The dashboard add-charger button and the battery/SOC pickers landed after your version (they're in the current v1.7.4 pre-releases — enable "Show beta versions" in HACS to get them, or wait for the next stable). If after updating auto-detection still misses your battery SOC or discharge entity, paste the exact entity ids here (or open an issue) and we'll make sure the Solax naming is matched out of the box.

You must be logged in to vote
0 replies
Comment options

Inverter: Solaredge 7SK
Battery: Anker Solarbank Max AC
EV Charger: Zaptec Go2

EV: Hyundai Ioniq5

Tariff: Zonneplan

Country:NL
SEM version: Laters

What works well? discovering

Any issues?

You must be logged in to vote
0 replies
Comment options

Thanks @coppe218 — welcome, and thanks for sharing your setup! SolarEdge 7SK + Anker Solarbank Max AC + Zaptec Go2 on Zonneplan (NL) is noted. SEM reads solar, grid and battery straight from your Home Assistant Energy Dashboard, so those sensors should be picked up automatically once you move past read-only. If anything acts up, open an issue and we'll take a look.

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

AltStyle によって変換されたページ (->オリジナル) /