EcoFlow asks developers of open Home Assistant integration to stop development

Thank you for the integration anyway and your hard work and many hours of development!

I stopped updating the integration a while ago because it covers my device as far as I like and since it works all properly: Never touch a running system.

Cloud API from EF was not supported for my D3Plus, hence I use this integration. But if EF does a local API, why not, assuming no internet connection is needed.

A couple months ago I cut Internet access to EF. It runs and shall not do a FW update (Which I think must be done with the app). I did one a while back and then it developed a strange behavior with SOC, which I now have solved. So it runs but I do no more updates. There is a FW update available but I don't trust it.

Even if EF does an API, I will stick with my setup, it works just fine. I am very happy and very thankful for your Integration.

Off-Topic:

More detailed explanation of the SOC behavior:

I charge to 86%. Then EF does a cycle itself from 86% to 83%, then recharges to 86% (That is repeatedly done and takes around 7-9 hours). And then after 2 days it starts to make a SOC spike. It charges until 84-ish % and then jumps directly to 86% within seconds.

Thats the part EF is doing itself.

My part in this cycle:

I use it as Home Battery as well, charging it AC by day with overflow solar power from the house and then use this at night for the plugged in devices (Using the self powered mode). I use it from 86% down to 30%, because the other 30% are needed as ups backup power for short net cut outs.

This is done by several automations.

But as mentioned above, after a couple days it starts to do these SOC spikes around 2 to 3 days. When I charge it, it does the SOC spike here as well but with much different outcome. Usually it starts around 72% SOC while charging and then mostly around 77% it jumps extremely fast to 100% SOC. With the automations and dynamic charge power, not reacting to this behavior, it sends more charging speeds and after ~4 new charge speeds set, EF cuts out the AC power. This is a common issue I think. It did it also in TOU-Mode (Set a charge speed while not charging leads EF to cut out AC output power.) a while back. So I did modify the charge automation to recognize these SOC spikes/glitches and therefore if detected, it sets charge speed to 100W and stops all automation. Done. Works good and so I have a running system which is very reliable and I am not eager to do a FW update to find out new problems.

All these SOC spike/glitch is then over after this 100% spike. After this it is completely normal again.

All this is a repeating cycle it repeats every 5 days.

So all good for me here, I hope EF does a step to help users have their control locally.

2 You must be logged in to vote

👍 3

All reactions

👍 3

1 reply

Comment options

Uh oh!

There was an error while loading. Please reload this page.

Something went wrong.

Uh oh!

There was an error while loading. Please reload this page.