Wallbox Pulsar Plus momentary power or current readings?

[andre-richter]

Hi all,

due to network connectivity reasons, I am currently stuck with SW version 5.3.20 on the Pulsar Plus. I never got 5.5.10 running to date.

With 5.3.20, the only metering sensor values I get are energy sensors:

Any current or power sensors are either 0 or Unknown. So I wonder if this is expected, or if 5.5.10, which I couldn't get to work yet, would offer some more?

Thanks a lot!

[GrantKeymer]

Hi all,

due to network connectivity reasons, I am currently stuck with SW version 5.3.20 on the Pulsar Plus. I never got 5.5.10 running to date.

With 5.3.20, the only metering sensor values I get are energy sensors:

Any current or power sensors are either 0 or Unknown. So I wonder if this is expected, or if 5.5.10, which I couldn't get to work yet, would offer some more?

Thanks a lot!

Have a look at the bottom of this page and you will see the useful Metrics (sensors) which work for me with V5.5.10...

https://github.com/lbbrhzn/ocpp/wiki/user-guide

[andre-richter]

Thanks, good to know Power Active Import works on your side.

It is constant 0 on my side unfortunately.

[miqm]

For me I also have Power Active Import set to 0. However I've a 3-phase model. could this be the reason? I assume to calculate proper power, It'd need voltage and current. but it does calculate energy properly 🤔

[Strixx76]

Works for me as well.

The reason I change from the "official" Wallbox integration using the myWallbox cloud service was that the momentary power readings wasn't working correct. It only showed the power in the beginning of each session and then it went down to 0. I saw the same behavior in the Wallbox portal.

I now have both of them running, and I see that it still behaves the same in the "official" integration, but this integration (OCPP) works perfect!

[GrantKeymer]

Yes, I've found the same thing with the power readings dropping to 0. The Wallbox app is poorly written and the Wallbox portal isn't much better. The only thing I use them for is Session Data, with the monthly graphs being quite handy.