EcoFlow BLE (Unofficial)

@c7pher You are not alone, I do have the same problem with my Ecoflow delta pro.
When I try to add the delta pro to the EcoFlow BLE integration, the bluetooth symbol on the ecoflow display stops blinking, some seconds later the integration prints an error “Device disconnected before it could authenticate - check logs for more info”
I tried pressing the pairing button or to reset iot.
No change.
I am also unable to pair the delta pro, using bt, with my iPhone.

My be bluetooth on the device is broken, or do you have any other idea?

1 Like

@MatthewJB2022 You probably figured that that was referring to STREAM Ultra X, not DPU X.

@Expalmi Hang on, since you didn’t provide any info in the discussion, I assumed that you can’t even see it, but getting an actual error is a different story. Can you post the full error into that discussion?

@GnoX ok, I come back to the original discussion

Hi to all.
I`m quite new to HA and maybe have a silly question. I have installed the EcoFlow BLE and ESP Builder with 2pcs ESP32, connections work all fine exept the delta pro but there i have to do some research befor asking. Now the question:
Is there no possibility to set between smart plug and smart meter? Idea: 1 powerstream has a delta pro with extra battery and 1 powerstream has an old delta max. I want the max to take over as soon as the pro is empty, both with the smart meter.
Greetings from Switzerland

If you have the right switches in the right places to interrupt the load, yes this will work. I do something similar myself.

Something to consider though, the ESP BT devices typically max out at 3 BT connections and are very low powered. The 2 power steams and the 2 deltas will be very chatty and will probably max out your 2 ESP BT proxies by themselves. Go slow and make sure you have good RSSI values before you get to far along.

I can`t find the function in home assistant to adjust between smart plug & smart meter. As the powerstreams are in different rooms, each ESP only has to manage 2 devices. :slight_smile:

I dont think i understand what you are asking for then… sorry bout that.

No problem :slight_smile: I have a shelly 3em so the powerstream adjusts the power output automaticly. I would like to turn that on/off so that i either have 0W output or automatic over the shelly.

ok, maybe i do?… slightly different config but…
On my D3 plus i have a shelly 1 gen4 wired to each of xt60 solar/car/mppt dc inputs. The cables themselves only carry 12v, so i think my setup maybe a bit simpler than yours.
I use the EF ble integration and HA automations to adjust the amps on the solar/car dc inputs on the EF unit itself, but i have an automation for when i set the solar/car dc inputs max amps to 0 that also turns the the attached shelly 1 off.

I still think what you are trying to do is possible, probably with just creating an automation in Home Assistant.
Is it the automation part you are struggling with or is there something else i’m missing?

I’ve been using this integration successfully for quite some time with a shp2 and a delta pro ultra. There is one thing I’ve been missing that I haven’t figured out yet. With the shp2 I can see point in time power comsumption of a circuit, but I’m not finding any entities to track energy that I can add to the Energy dashboard. Is there a way to accomplish this?

EF units and the EF integration output amps, volts and watts. but not energy. (wh)

Amps - measure the flow of electric current
Volts - measure the pressure of electricity
Watts - measure the power being used (calculated as volts multiplied by amps).

You’re not seeing any EF devices/enties in the Energy Dash board because watt-hours (Wh) measure the total energy consumed over time is not provided by the unit nor the integration.

This is how you calculate energy consumed over time from the metrics the unit and the integration provide in HA so you have metrics needed for the Energy Dash board (wh)
If you have a sensor that returns instantaneous power readings (W or kW), then to add a sensor that returns energy usage or generation (kWh), refer to the Riemann sum integral integration.

More discussion is available here:

Thanks. This is somewhat of an awkward solution, but thanks for sharing the thread which goes into further discussion about it. I note that the ecoflow [android] app does include consumption measured in kWh. I’m not sure if this is a new addition, but I don’t think it would be responsible for collecting samples and calculating these values as I don’t keep it running all the time and it still seems to contain the correct data. Maybe there is now a set of consumption values per circuit that could be polled by this integration rather than needing the integral integration?

Ecoflow devices transmit different data over BT than they do over wifi to the cloud.
There is a separate integration to pull EF data from the cloud. From the cloud integration notes it does pull energy metrics from the shp2 and delta pro ultra. You have options… and i run both and i use integrals to get the data i want how i want it. Both projects are community driven, you are welcome to contribute your skills as well.

From the cloud integration notes it does pull energy metrics from the shp2 and delta pro ultra.

One correction - I don’t think it pulls it from the device - I can’t find a field that represents energy for either of these devices which means that it does not calculate energy internally - it only integrates while connected to the cloud (I know this is the case for Delta 3s as it says Statistics are estimated based on cloud data generated while the device is online in the EF app).

FYI - for cloud integration SHP2 and DPU, the integral is calculated in HA from power sensors - it does not pull it from cloud/device so it does exactly the same thing as manual integral, it just saves you few clicks. We could do the same thing, but I find these sensors a bit misleading.

Anyone notice the R3 USB ports no longer report watts after the 6.30.49.79 FW update?

I don’t think this is an integration issue as my logs clearly show the USB ports stoped reporting right after the FW update. Their app even shows 0w when it should not.

I’m opening a support case to roll the FW back and was just curios if anyone else noticed this too.

Am I correct in thinking TYPEC_OUT, USBA_OUT, and AC_IN should have statistics content?

display_statistics_sum {
  list_info {
    statistics_object: STATISTICS_OBJECT_AC_OUT_ENERGY
    statistics_content: 1932
  }
  list_info {
    statistics_object: STATISTICS_OBJECT_DC12V_OUT_ENERGY
    statistics_content: 442
  }
  list_info {
    statistics_object: STATISTICS_OBJECT_TYPEC_OUT_ENERGY
  }
  list_info {
    statistics_object: STATISTICS_OBJECT_USBA_OUT_ENERGY
  }
  list_info {
    statistics_object: STATISTICS_OBJECT_AC_IN_ENERGY
  }
  list_info {
    statistics_object: STATISTICS_OBJECT_PV_IN_ENERGY
    statistics_content: 7119
  }

Yeah, we confirmed that USB data is missing in [Bug]: USB A/C power unknown River 3 Plus max · Issue #271 · rabits/ha-ef-ble · GitHub.

I am still on a very old firmware as I don’t have anything to gain from upgrading - it’s been running for full 7 months without interruption.

Well crap, Yup 1.33.81.60 does the same thing to the R3 plus too. I didn’t even notice. All the release notes states is “Fixes some known issues” :rofl: Well, let me get a support ticket open to get that one rolled back too. THX for the link.

While we are on the topic 7.73.86.37 breaks stuff on the D3+. 7.73.86.22 restores functionality.

I think once I get my functionality back to my units there will be no more EF updates for a long, long time.

For anyone this helps, i can confirm downgrading a R3 to 6.30.49.76 and R3 plus to 1.33.81.57 restores expected behavior. The USB ports report watts again.

@GnoX and @Rabit,
When i enable debugging mode on a DP3 and i see all the message types are from mr521.DisplayPropertyUpload but the properties i’m looking for are:

message RuntimePropertyUpload {
  optional float plug_in_info_pv_h_vol = 41;
  optional float plug_in_info_pv_h_amp = 221;
  optional float plug_in_info_pv_l_vol = 44;
  optional float plug_in_info_pv_l_amp = 222;
}

Am I not seeing them in the logs because the D3P does not send RuntimePropertyUpload over BT or was it not added cause there are very few weirdos who would find the RuntimePropertyUpload info useful and it’s a lot of data?

That RuntimePropertyUpload message is probably only exclusive to cloud - I didn’t find any evidence that you can get it over bluetooth in the app. I did try sending some dev options to the device to see if I can enable it or control the interval of messages, but it did nothing. If you can’t see those values in the EF app, it is most likely not possible to get it over bluetooth.