Thx for double checking, i’ve only seen those values available through mqtt or cloudapi. Seeing RuntimePropertyUpload in the mr521.proto got my hopes up.
It isn’t picked up anywhere in Home Assistant. Here are the signal properties of the Delta Pro, maybe someone finds the cause. It’ is transmitting a signal, but the ble isnt picking it up.
I posted 2 more screenshots in the Github discussion, as I’m limited to one here.
I just recently switched over a Delta 2 from using the Cloud integration to the BLE integration (v0.8.5), and noticed an anomaly since doing so, with DC Output Power. I have DC Output turned off, and nothing connected to the DC ports, but I’m still getting power values:
As background, this Delta 2 is connected to some leftover solar panels, which charge it during the day, and the AC Input to the Delta 2 is cut off between 4pm-9pm (where my energy tariffs are higher), and I just run off the battery during that period. Power comes back on at 9pm (but Backup Reserve is set to 10% until midnight, when it is restored to 50%), so these DC Output Power values really look a lot like the AC Input values:
Is this a bug in the integration, or perhaps this is illustrative of what is going on behind the scenes? For example, is that AC input getting turned into DC output even though I"m not using the DC ports?
Just a very brief note: heall yeah, what a great project and integration - really happy to switch over from cloud to bluetooth (D2Max & powerstream) 
Thank you!
I want to connect my PowerStream using BLE. I got the Ecoflow User ID, but on connection there’s just this message:
Authentication failed - Device needs to be bound via the EcoFlow app first
What does that mean? The PowerStream is connected to my account (cloud access is working). What else do I have to do?
Good looking integration, can’t wait to get some charts and graphs and fun stuff. When trying to add a Delta Pro 3 on the latest firmware (V7.65.92.17), it shows up as an unsupported, unidentified device despite being supported according to the wiki. I’m gonna guess this is because my DP3 is on newer firmware. Should I go ahead and add it so as to collect data for you?
Absolutely love this integration. 5 proxies and all my DPU’s work flawlessly! Has anyone been able to control a 50 Amp Hub using the integration?
Not works with Delta 2, FW 1.0.2.176 or some else have any idea?
@jaydisc Delta 2 messages are annoying to work with because they use fixed length encoding and the byte sequence does depend on the firmware. This encoding means that if we misidentify one field, everything after it can shift and will report incorrect values - I think in your case it is reporting DC Input Power, not output power - input power field is right next to output power, just shifted 4 bytes left. If you create an issue on github and provide some diagnostics data, we can look at it.
@cs42 Microinverter devices (PowerStream and STREAM Microinverter at the time of writing) do sometimes need to be rebound to the account to work properly in this integration, see PowerStream: Authentication fails with NeedBindInstallFirst (0x04) and WrongKey (0x06) · Issue #279 · rabits/ha-ef-ble · GitHub. We don't know why this is happening yet.
@CavemanJoe Showing up as unsupported means one of two things either your bluetooth adapter receives mangled advertisement data or more likely, your device has a new serial number that we didn't add yet. Can you provide first 4 letters of your device's serial number to confirm?
@4rth4X Can you create an issue on github and provide some more details, such as logs with connection requests logging option enabled? It could be few things, we need some more info to identify what to check for. We know that Delta 2 devices did have at least 2 versions of auth procedure and we don't support the early one yet.
FYI - I don't actively watch this thread so prefer issues or discussions on github if you find a bug or have a feature request, it is easier for us to track and I'm faster to respond there.
1 Like
do sometimes need to be rebound to the account to work properly in this integration
This did indeed work. Thanks (maybe add this to the documentation 
).
I've added those digits to a report on github, thanks!