EcoFlow BLE (Unofficial)

Sooo despite ugly errors I did not catch in my last change (most probably happening due to unreliable connection to the device) - it looks like your esp32 proxy have some issues, that what I can think of on top of my mind:

  • Maybe it is far away from the devices? Mine one is within 2 meters and there is nothing in between.
  • There is some sort of interference with high-power devices? I see mine start to feel weird if something running close by.
  • Power issues: ESP32 WiFi/BT chip is quite hungry and if you use long power cable or too weak 5v power adapter - it could cause issues. Countless times I debugged the thing to figure out the cable is too long (because wifi chip likes to cause spikes in power consumption and if cable is too long - it drains too fast and gives not enough current to prevent the voltage drop).
  • Old esphome firmware? Maybe I was lucky to install the latest one and it just works?
  • Maybe the esp devkit you using is v2 (I heard there is some issues with it)

Also you can check the logs on the ble-proxy - maybe there is something useful like “broken connection” or whatever… You can get those logs in the esphome addon wirelessly.

So that will be great if you can check every bit of the path on the road of signal from HA to the ecoflow device. Especially take care of the power - use shortest cables possible (I use cable ~5cm long) and 5v adapter (at least 1A) - check different ones and hopefully you will get much more stability out of it.

For me it looks like that: Usually everything is fine, but suddenly a couple of disconnects and then it’s fine again… And I have 3 ecoflow devices on the same proxy (2xSHP and 1xDPU).

...
2025-01-07 02:33:41.225 WARNING (MainThread) [custom_components.ef_ble.eflib.connection] E8:6B:EA:CC:FB:5E: Disconnected from device
2025-01-07 02:33:41.227 WARNING (MainThread) [custom_components.ef_ble.eflib.connection] E8:6B:EA:CC:FB:5E: Reconnecting to the device in 10 second
s...
2025-01-07 02:33:51.228 INFO (MainThread) [custom_components.ef_ble.eflib.connection] E8:6B:EA:CC:FB:5E: Reconnecting to device
2025-01-07 02:33:51.670 INFO (MainThread) [custom_components.ef_ble.eflib.connection] E8:6B:EA:CC:FB:5E: Connected
2025-01-07 02:33:51.670 INFO (MainThread) [custom_components.ef_ble.eflib.connection] E8:6B:EA:CC:FB:5E: Init completed, starting auth routine...
2025-01-07 02:33:52.938 INFO (MainThread) [custom_components.ef_ble.eflib.connection] E8:6B:EA:CC:FB:5E: Auth completed, everything is fine
2025-01-07 02:33:57.915 WARNING (MainThread) [custom_components.ef_ble.eflib.connection] E8:6B:EA:CC:FB:5E: Disconnected from device
2025-01-07 02:33:57.916 WARNING (MainThread) [custom_components.ef_ble.eflib.connection] E8:6B:EA:CC:FB:5E: Reconnecting to the device in 10 second
s...
2025-01-07 02:34:07.917 INFO (MainThread) [custom_components.ef_ble.eflib.connection] E8:6B:EA:CC:FB:5E: Reconnecting to device
2025-01-07 02:34:08.382 INFO (MainThread) [custom_components.ef_ble.eflib.connection] E8:6B:EA:CC:FB:5E: Connected
2025-01-07 02:34:08.382 INFO (MainThread) [custom_components.ef_ble.eflib.connection] E8:6B:EA:CC:FB:5E: Init completed, starting auth routine...
2025-01-07 02:34:09.909 INFO (MainThread) [custom_components.ef_ble.eflib.connection] E8:6B:EA:CC:FB:5E: Auth completed, everything is fine
...

On my end I will add more checks for the data - initially I had no idea that data could be corrupted on receive side and thought BLE will handle that, but apparently not or it’s happening on WiFi side with esphome custom protocol who knows…

Here how it looks on my end since ytd - no issues whatsoever except 8PM where I tested the fixes: