Ecoflow river 3 BLE breaks without Wifi

[aik]

Ecoflow river 3, EF-R3PN0371. Installed their app, configured, added to HA with this addon, enable BLE, all good.

Now, I block internet for this Ecoflow on my router. Soon after BLE stops connecting (below are example messages). The bluetooth integration works, the EF-R3PN0371 is in the list of advertised devices.

The only way to reconnect BLE is allow the Ecoflow to go to the internet. Which defeats the purpose of BLE (which is supposed to provide the data when the internet is off), does not it? Do I miss something here? Thanks,

custom_components.ef_ble.eflib.exceptions.AuthErrors.KeyInfoReqFailed: Received type of KeyInfo is != 0x02, need to dig into: 010000e40f3617b5c774e2fd87bbecd3df7a5edae7f4d854ae24351ff234e503818b5d56ceebbfd997807b

2026-09-02 07:18:39.689 ERROR (MainThread) [custom_components.ef_ble.eflib.connection - E4:B3:23:8D:C1:32] Failed to connect to the device: EF-R3PN0371 - E4:B3:23:8D:C1:32: Failed to connect after 10 attempt(s): No backend with an available connection slot that can reach address E4:B3:23:8D:C1:32 was found: only in non-connectable history (no connectable path); 1 sca
nner(s) registered, 1 scanning, 1 connectable; last advertisement 64s ago via hci0 (00:DB:DF:84:80:13): The proxy/adapter is out of connection slots or the device is no longer reachable; Add additional proxies (https://esphome.github.io/bluetooth-proxies/) near this device                                                                                                

[GnoX]

Note

Quick first pass from an AI agent working in the maintainer's repo, so this doesn't have to wait for his next free evening: it has the full history, his notes and the protocol reverse-engineering material to work from, and strict instructions on what it may change, publish and claim. GnoX reviews these and corrects anything that turns out wrong.

You are not missing anything about how this is supposed to work - Bluetooth should keep working with the device offline, that is rather the point. But there are two different errors in what you posted, and they need separating before we can say much.

First, which version of the integration are you running? It matters, because 1.1.0 has a known authentication bug that affects every device, and your first error is its exact signature:

KeyInfoReqFailed: Received type of KeyInfo is != 0x02

If you are on 1.1.0, please roll back to 1.0.4 and try again - in HACS, three-dots menu on the integration → Redownload → pick 1.0.4, then restart Home Assistant. That version predates the bug. A fix is in testing and will land in a release, so this is temporary. (If you would rather help test the fix instead, there is a pre-release build on the maintainer's fork, but downgrading is the sensible default.)

Second, and this one is more interesting, because it is not that bug:

only in non-connectable history (no connectable path);
1 scanner(s) registered, 1 scanning, 1 connectable

That is Home Assistant saying it can see your River 3 advertising, but has never seen it advertise as connectable. Bluetooth advertisements carry a flag saying whether the device is accepting connections, and without it Home Assistant will not even try. The message's advice about adding proxies is generic and probably not your problem - you have one adapter and it is working.

What would help is knowing which of the two errors you get while the internet is blocked. If it is the "no connectable path" one, that would suggest your River 3 stops advertising as connectable when it loses its cloud connection - which would be behaviour in the device's firmware rather than anything we can fix, though it would be very useful to know. If it is the authentication one, the version question above is the likely answer.

So: version first, roll back if you are on 1.1.0, and then tell us which error survives with the internet still blocked.

---

🤖 AI-generated comment (Claude Code, model Claude Opus 5).
Prefer to wait for a human? React 👎 to this comment or reply /no-ai, and this thread gets no further automated replies.