On October 20 the ha-ef-ble project — the community integration that gives EcoFlow hardware local Bluetooth control in Home Assistant, with no cloud involved — switched to maintenance-only mode. The release note says it plainly:
according to agreement with Ecoflow the repository now switched to maintenance-only mode
The repository's own device list puts the consequence in one line: "According to agreement with Ecoflow we can't add new devices after release v1.3.0."
This is the integration my entire setup runs on. A Smart Home Panel 3, a DELTA Pro Ultra and an Ultra X, three ESP32 Bluetooth proxies, and the time-of-use automation behind four straight months at zero on-peak. So this is not a GitHub thread I read about — it is the software my power bill depends on.
What actually happened, with dates
October 1 (v1.2.0). The maintainers reported that EcoFlow had contacted them and "want us to stop the operations on this project, because the integration uses their ble protocol." The same note says EcoFlow told them a local API was being built as a replacement, that the maintainers offered to help with it, and that no reply came back.
October 20 (v1.3.0). Maintenance-only mode, by agreement. Patches continue. Existing functionality stays supported. No new devices, ever.
That is the whole public record, and it comes from one side of it. EcoFlow has said nothing publicly that I can find. Everything above is the maintainers' account of a private conversation, and it deserves to be read as exactly that.
Nothing breaks today
Worth saying early, because the first wave of comment was more alarmed than the facts support.
The repository is not archived. It is not abandoned. Maintenance mode means bugs still get fixed, and devices that worked at v1.3.0 keep working. If you are running a DELTA Pro Ultra, an Ultra X or a Smart Home Panel 3 on it this morning, you will be running it tomorrow, and the maintainer has committed to keeping it that way.
My own three devices are on v1.3.0 with pinned proxies and I have changed nothing.
What does break is your next purchase
Here is the part nobody has connected, and it is the reason this matters commercially rather than just sentimentally.
The TITAN series launched on October 13. The agreement freezing new device support landed on October 20. Seven days.
So the TITAN 5000, the TITAN 5000 Plus, the Classic and the Smart Home Panel 10 are all on the wrong side of that line — and under this agreement they never cross it. Neither does whatever EcoFlow announces next. If you are reading my first look at the TITAN and weighing it against a DELTA Pro Ultra, add this to the column: one of them has local Home Assistant control available today, and the other is permanently excluded from the only project that provides it.
That is a genuine point of difference between an older EcoFlow and a new one, and it runs opposite to the usual direction, where the newer product is the safer buy.
The replacement nobody can find
The justification for shutting down a community project is usually that an official path exists. So I went looking for EcoFlow's local API.
There is no announcement. No developer-portal entry. No release note, no press release, nothing dated 2026 that describes a local API for EcoFlow hardware.
What EcoFlow does publish is a Developer API, and it is cloud-based. The Home Assistant integrations built on it say so without ambiguity — they authenticate against EcoFlow's servers and move data over cloud MQTT. One project's documentation states outright that local control is not available through that route.
Which puts the situation plainly: the thing being withdrawn is local, and the official thing offered in its place is not. Local control is the feature that keeps working when your internet is down, and your internet being down is strongly correlated with the grid being down, which is the entire reason the battery is bolted to your house.
I would be glad to be wrong about this. If EcoFlow ships a genuine local API, it is a better outcome than a reverse-engineered one — supported, documented, and not dependent on a volunteer's weekend. But it has to exist first.
What I changed, and what I had already done
The agreement freezes new devices. It says nothing about the protocol itself, and that is the real exposure: ha-ef-ble reads EcoFlow's Bluetooth protocol, and a firmware update could change that protocol on a Tuesday afternoon without anyone announcing it.
My EcoFlow devices have no internet access. I cut it so they cannot pull automatic firmware updates, and everything runs over local Bluetooth through the integration. That was a decision I made about firmware stability well before any of this — I did not want a device that controls my house silently changing behaviour overnight — but it reads differently now. A device that cannot reach EcoFlow cannot be updated into incompatibility.
I want to be straight about what that costs, because it is not free:
- No security patches. This is the real one. An unpatched device on your network is a deliberate trade, not a clever trick.
- No remote access through EcoFlow's app. Everything is local, which is the point, but it does mean no checking the batteries from a hotel.
- No new features or fixes from EcoFlow, including fixes for firmware bugs you may actually want gone.
- It only works if you do it before an update lands. If your devices have been online and have already taken the update, this is not a rollback.
I run it this way because local control is the thing I am actually buying, and I would rather have a frozen device that behaves predictably than a current one that might not. That calculus is not the same for everyone, and if you are not running Home Assistant it is probably the wrong trade entirely.
If you are buying right now
- If local control matters to you, check the supported-device list at v1.3.0 before you buy, and buy from it. That list is now final.
- If you are choosing between a DELTA Pro Ultra and a TITAN, local Home Assistant control is a real differentiator in favour of the older line, and it will not be fixed later.
- If you are not running Home Assistant, none of this changes anything. The EcoFlow app plus a Smart Home Panel does the core job, and always did.
- If you already have a working setup, do nothing. Maintenance mode is not a countdown.
And if you are weighing the hardware itself rather than the software around it, run your power bill through the analyzer — it sizes a system against your actual usage on any utility, and tells you what it would cost before you talk to an electrician.
The thing I keep coming back to is that the automation on top of this integration is what produced the numbers on this site — two charge cycles a day through winter, zero on-peak kWh four months running, published bills to match. That was built on a volunteer project that a manufacturer could ask to stop at any time, and did.
If you want the full build — proxies, scheduling, the failure modes — it is in how I automate my EcoFlow with Home Assistant. It still works. It just will not grow.
Everything here about EcoFlow's position comes from the maintainers' release notes describing a private conversation. EcoFlow has not commented publicly, and if that changes I will update this post. I may earn a commission from hardware links on this site, at no extra cost to you, at the same rate across every brand — which is why a post like this one costs me nothing to write.