Huawei

[JohanAlvedal]

Huawei user from Sweden here ready to test.

[johanzander]

Thanks for volunteering to test! Before I start building support, a couple of quick questions so this targets your actual setup:

1. Which battery do you have — Huawei LUNA2000, or LG RESU? The huawei_solar HA integration handles these very differently: LUNA2000 takes an explicit charge/discharge schedule (a good fit for how BESS works), while LG RESU uses a price-bidding scheme where the inverter decides charge/discharge itself from a price signal, not compatible with BESS's own optimizer. Initial support is planned for LUNA2000 only — if you have LG RESU, let me know and we'll figure out a path separately.
2. Which HA integration are you using — huawei_solar (wlcrs)? And roughly what version, if you know?
3. To confirm: local Modbus connection to the inverter (not a cloud-based setup), correct?

No need to install anything yet — there's nothing to install until initial support ships. Once it does, I'll ask you to pull a debug export from BESS so I can validate against your real device registry and lock in a regression test.

[JohanAlvedal]

- *Which battery do you have* — *Huawei LUNA2000* - *Which HA integration are you using* —* huawei_solar (wlcrs) <https://github.com/wlcrs/huawei_solar>? V2.1.1* - To confirm: local Modbus connection to the inverter (not a cloud-based setup), correct?:* Yes* Den ons 22 juli 2026 kl 23:38 skrev johanzander ***@***.***>:

…

*johanzander* left a comment (johanzander/bess-manager#120) <#120 (comment)> Thanks for volunteering to test! Before I start building support, a couple of quick questions so this targets your actual setup: 1. *Which battery do you have* — Huawei LUNA2000, or LG RESU? The huawei_solar HA integration handles these very differently: LUNA2000 takes an explicit charge/discharge schedule (a good fit for how BESS works), while LG RESU uses a price-bidding scheme where the *inverter* decides charge/discharge itself from a price signal, not compatible with BESS's own optimizer. Initial support is planned for *LUNA2000 only* — if you have LG RESU, let me know and we'll figure out a path separately. 2. *Which HA integration are you using* — huawei_solar (wlcrs) <https://github.com/wlcrs/huawei_solar>? And roughly what version, if you know? 3. To confirm: local Modbus connection to the inverter (not a cloud-based setup), correct? No need to install anything yet — there's nothing to install until initial support ships. Once it does, I'll ask you to pull a debug export from BESS so I can validate against your real device registry and lock in a regression test. — Reply to this email directly, view it on GitHub <#120?email_source=notifications&email_token=AGFEGZ3ZBQTFB4RACKYHRVD5GEX33A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBVGE4DKNZYGAYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5051857800>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGFEGZ57TC4YAK6LGIIG4YT5GEX33AVCNFSNUABFKJSXA33TNF2G64TZHM4DQNRSGYYDSNRSHNEXG43VMU5TINRUGQYDANBQHAZ2C5QC> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[johanzander]

Hi @JohanAlvedal — good news, Huawei LUNA2000 support (via huawei_solar, local Modbus) is built and available to test now, as an experimental beta.

To install it:

1. In Home Assistant: Settings → Add-ons → Add-on Store → ⋮ (top-right) → Repositories, and add:
   https://github.com/johanzander/bess-manager-beta
2. Install "BESS Manager (Beta)" from that repository — it's a separate add-on from stable BESS Manager, so you can keep both installed but only run one at a time (stop stable before starting the beta).
3. In the setup wizard, the Huawei platform and your huawei_solar entities should auto-detect from your entity registry.

What would help us most:

• Confirm the wizard finds your LUNA2000/huawei_solar entities correctly and the schedule actually gets written (TOU period list via huawei_solar.set_tou_periods, gated behind the battery's working-mode select).
• Once it's running, export a debug report from the Health tab and post it here — that captures your exact device registry and config, and lets us lock your setup into our automated regression tests so it can't silently break in a future release.

⚠️ This is still experimental — several real bugs have already been found and fixed from other testers' debug logs (sensor auto-discovery gaps, a SOC-limit write bug, TOU write failures behind an EMMA energy manager), so the beta channel has the most complete fix set. Your feedback is exactly what we need to get this graduated to stable.

🛰️ Lifecycle tracker — Huawei LUNA2000 (#120)

• 1. Implemented & shipped experimental — merged to main, shipped stable in v10.0.0, latest fixes on beta v10.1.0b5.
• 2. Your debug log ← we're here — install the beta, then export a debug report from the Health tab and attach it here.
• 3. Lock your config into the regression suite — your real (anonymized) setup becomes a permanent automated test.
• 4. Re-ship beta, CI green — with your config in the test matrix.
• 5. You confirm it works on your hardware.
• 6. Promote to stable — remove the "experimental" label and ship in a normal release (this issue closes then).

Thanks again for volunteering to test — looking forward to your feedback!

[JohanAlvedal]

Hi Johan,

I’ve now tested the Huawei LUNA2000 beta setup.

The wizard auto-detection worked correctly for the Huawei/LUNA2000 setup overall, but Current phase monitoring failed during the health check.

I do have the correct Huawei huawei_solar phase current sensors available in Home Assistant, so this looks like an auto-discovery/mapping issue rather than missing data.

I’ve attached a screenshot showing the correct entities for phase current monitoring when using Huawei’s own Smart Meter.

Apart from that, the Huawei entities were detected correctly so far.

I’ll continue testing the actual TOU schedule writing and huawei_solar.set_tou_periods next, and will export the full debug report from the Health tab once I’ve run it.

Also, sorry — I accidentally closed the issue while using GitHub on my iPad. 😅 you can reopen it now, as the Huawei beta testing is still in progress.

Thanks!
Johan

[JohanAlvedal]

I found a few more things that the System tab keeps insisting are missing, even though they appear to be configured correctly in the Integrations tab. So it looks like there may be some inconsistency between the system health/status checks and the actual integration configuration.

[JohanAlvedal]

I’m not sure if I read somewhere that BESS currently can’t read the TOU charging/discharging periods from Huawei.

However, the TOU periods seem to be available as attributes on:

sensor.batteries_tou_charging_and_discharging_periods

Could these attributes potentially be used by BESS to read the configured Huawei TOU periods?