[Sensor]: PowerStream Battery Level not reported anymore

[joaster-git]

Pre-submission checks

• I'm running the latest release and the issue still reproduces
• I searched existing issues and this isn't a duplicate

What kind of change are you asking for?

Wrong value (sensor exists but is incorrect)

Device model

PowerStream, FW 1.0.1.288

Sensor / control name

sensor.powerstream_battery_level

What's wrong or what's needed?

The battery level of the extra battery connected to the PowerStream is reported "Unknown" instead of the actual value. All other sensor values are reported via EcoFlow BLE. Via EcoFlow-Cloud the battery level value is reported.

This issues started occurring 6 June 2026 @ 7:31:44, around that time I did the EcoFlow BLE updates* as well: 0.9.2 first and some time later 0.9.3, don't know exact timings.

I can't say for sure it is related to the updates, but it is clear the value of the battery level is currently not reported via EcoFlow BLE while it is via EcoFlow-Cloud.

Integration version

0.9.3

Diagnostics

No response

Anything else?

[GnoX]

@Neewieedo Looks like we have to revert what we discussed in GnoX#79, it seems that field is not available for all PowerStreams. I'll expose the current one as a new sensor.

[joaster-git]

@GnoX, reading GnoX#79 there appear to be 3 fields for SoC. Would be good to see which one does give a readout comparable to the readout via EcoFlow-Cloud exposing all three. About your remark on the difference between PowerStreams, this one is a PowerStream 600W version, maybe it differs from the 800W version.

I did find out that on the time the battery level was not reported anymore I restarted HA to load updated HACS integrations, EcoFlow BLE being one of them. Since EcoFlow BLE versions are not reported as an entity (like host, HA supervisor and HA core versions), I am not sure from which to which EcoFlow BLE version I went, so I can't narrow that down.

Have to say that except from this issue it runs rock solid, great work!

[GnoX]

It was released in 0.9.1.

What I'll do is restore that battery level field to what it was before and expose other battery levels as diagnostics sensors as I noted in that issue.

[joaster-git]

Update: in the latest 0.9.4 release this issue has not been addressed yet. For the ones affected by it, you can downgrade to version 0.9.0 to have it working in the mean time.

[GnoX]

Ah, sorry, I knew I missed something important. I was super busy last 2 weeks and wasn't home this weekend. This is a trivial change, I'll do it right away.

[joaster-git]

Thanks @GnoX. Don't hurry it, there is a workaround. We are happy with all the work you put into it already.