[FEATURE] Official Support of Zendure SolarEdge 3000 Mix AC+

[HenriMatthijssen]

Area of the proposal

Battery communication or driver behavior

What problem would this solve?

The Zendure SolarEdge 3000 Mix AC+ is now officially not supported by the OmniBattery integration. Including it would benefit owners of this battery to use it with the OmniBattery integration in Home-Assistant.

Proposed solution

As the Zendure SolarEdge 4000 Mix AC+ is supported, I guess it should not be hard to include the Zendure SolarEdge 3000 Mix AC+as officially supported.

Example use case

The Zendure SolarEdge 3000 Mix AC+ is very popular because of its price-point and many people are using it. It would be great if we can use it with the OmniBattery integration in Home-Assistant.

Who would benefit from this?

Most Omnibattery users

Alternatives or workarounds

No response

Additional context

No response

Confirmations

• I searched existing discussions and did not find the same proposal.
• This is a general feature idea, not a request to support a new battery brand or model.
• I understand that community interest and technical feasibility influence prioritization, and that no delivery date is guaranteed.
• I removed passwords, tokens, API keys, complete serial numbers, IP addresses, and other sensitive information.

[github-actions[bot]]

Thanks for the suggestion! 🙌

Here's how this works:

• Vote by clicking 👍 on the original post — not in the comments
• The more votes an idea gets, the higher it moves in the priority queue
• I review feature ideas periodically and implement the ones that benefit the most users

If your idea is very specific to your setup, it may not make it into the core integration — I'll try to suggest a workaround in that case.

Feel free to discuss details or alternatives below.

[SnarfW]

I also request support in: #242 (comment)
But since this request is already marked as implemented the request might have be missed. Note that only the 4000 was implemented.

[ffunes]

Added — it will ship in the first 1.5.0 beta.

A note on what was actually wrong, since the battery was never really unsupported: the 3000 Mix AC+ already worked and was being controlled correctly. Its product string (solarFlow3000MixAC+) simply matched no pattern in the driver's model detection, so it fell back to the 2400 AC+ profile — which is why the charge and discharge limits were reported 600 W short in both directions.

It now has its own profile with a 3000 W bidirectional envelope, and the DC solar entities stay hidden since the model is AC-coupled only. Entries added before this change are stored as 2400 AC+, so no reconfiguration is needed: the integration detects the product on the next connect and adopts the right envelope on its own.

@SnarfW, thanks for the /properties/report dump in #242 — that was what made this a four-line change instead of a guess. Your request there was the one that got missed when that discussion was closed after only the 4000 was implemented.

Closing this one as a duplicate of #242, where the tracking already lives.

[HenriMatthijssen]

Thank you very much @ffunes for the descriptive reaction. Looking forward to this!