@VdR - I’ve checked my app permissions and Location is enabled. I think that’s the only thing needed as the Connectivity option is disabled in my Wallbox app settings.
Is there any other thing I need to enable Bluetooth?
Aha, that’s interesting. I know of many users who requested that option. I don’t care either and in fact I find the Halo lights are a useful feature to have always on.
I don’t think so. Can’t disable BT on the charger or on the app (makes sense as a fallback connection). So when enabled on the phone you should be good.
Yesterday I did have to restart the app to try the BT connection after the WiFi connection was activated. I also find that a power cycle of the Wallbox helps to clear unexpected behaviour (not had any lately).
1 Like
The firmware release of the Pulsar Plus on the firmware page Archives des Pulsar Plus - Wallbox Academy is back to version 5.7.18 dated today 
So it looks like they pulled it, however mine is updated already
Oops. Mine is updated as well. Have not tried charging yet, probably should …
Think it depends on the version. The North American one is on the old fw, Europe is on the new one it seems.
Good to know halo can be turned off, @Oriol_FP can this be controlled through API? Would be great to turn this off at night / control the colour myself.
Issue with charge reporting is hardware. It’s caused by a defective tsensor according to Wallbox. They changed my Pulsar plus. Since that day, no more problem.
That is interesting.
It used to work on my unit, so the sensor has failed in time. Very well possible. But that means some people (with a defective sensor) have the problem, others don’t. I had the impression everybody sees the problem. Well, I guess you do not, so maybe not.
Strange, the reporting still works when connected over BT, but the connection seems independent of a sensor failure. Also, the energy reporting works, and that number must be derived from a power reading.
Or maybe your unit had a sensor failure as an exception. Did you have the correct energy reporting?
Anyway, I’m confused.
@gonheriba Do you have some formal statement from Wallbox so I can use that to have my one replaced.
Thanks
Rien
Hi @RT1080
“Good to know halo can be turned off, @Oriol_FP can this be controlled through API? Would be great to turn this off at night / control the colour myself.” → Not planned. MyWallbox Portal was long ago decided to be targeted for Business segment (Charge Point Operators, small B2B accounts, etc…) while the App is going to be the main interface for Home segment. Thus the functionality range in the Portal is more limited than the App and new functionalities targeted for Home segment most probably will only be deployed in the app. Sorry for the inconvenience but understand that duplicating product capabilities in multiple interfaces is not efficient in terms of deployment agility and maintenance. However, I take note of the request.
Would be interested to know this issue ID with customer service too https://community.home-assistant.io/t/wallbox-pulsar-plus-integration/200339/369?u=oriol_fp @gonheriba
Thanks 
Now charging a car in ‘Green’ mode (the HA implementation, not the Wallbox implementation). The charger works great as usual (no issue with the update). Didn’t expect any different.
This trace shows the max current the HA controller is giving the charger. Drops from 32A to 6A when switching from ‘max’ mode to ‘green mode’, then increases to 15A based on excess solar as soon as the car is connected, then you see it react to some clouds. Neat.
This trace shows the charging power as reported by the Wallbox. The reported value falls to zero if the power did not change for 4 minutes. Fully repeatable. When the value changes the time is reset. I doubt this is a hardware issue. Note that this data is based on a 30 second sampling, so the exact timing may differ.
This is the trace of my fix for the power reporting. The logic ignores a drop to zero if the charger mode is still ‘Charging’.
2 Likes
@VdR - Very interesting indeed to know that the interval between a power change and the reported value dropping to zero is so consistent at 4 minutes. I suspected it was around that time but didn’t know it was so repeatable. I cannot see how this is a hardware issue either.
The trace on your last chart is very close to the true picture. The only significant place where I think it would be misleading is during cell-balancing when the EV is almost full. The actual power fluctuates between zero and 400 - 1000 Watts in a recurring cycle. I think the total period of cell-balancing lasts for 15 to 30 minutes with my Nissan Leaf, but other EVs are probably quite different.
Come on Wallbox - how hard can it be to fix this issue with all the clues you have now?
The only moment the last curve is off from reality is at the end of the charge because it takes a while after the end of charge before the Wallbox reports ‘Waiting for car demand’, which is the signal to the logic to accept the zero value.
I do not see the car demand go below the max at the end of the charge for any considerable time. In any case it cannot go as low as 400-1000 Watt because the minimum current is 6A, so about 1300 Watt. As you say, different cars deal with cell balancing differently.
Also, I do not think we are showing the engineers at Wallbox something they do not already know
1 Like
In any case it cannot go as low as 400-1000 Watt because the minimum current is 6A, so about 1300 Watt.
Well, that’s what I thought too but I have seen it each time I was watching while my Leaf was approaching full. Unless of course, Wallbox is reporting incorrect readings for that condition too??? Next time I must remember to check what my other energy meters are saying.
Sorry. I will check this next week instead of today as I promised. I had a sprain in my ankle playing rugby and I had to work from home these days without access to our testing facilities.
Thanks for sharing. Notes taken.
1 Like
Here’s the proof of what I was saying a few days ago concerning tapering of the charging power during cell-balancing…
This first chart is what was reported by my Shelly EM. The last few steps are as follows…
Watts 1450 | 1090 | 990 | 890 | 790 | 690 | 590 | 150 | 0
This second chart is what was reported by Wallbox. The last few steps are as follows…
Watts 1170 | 870 | 670 | 410
Wallbox misses out some of the steps including the last one where Shelly EM says 150 Watts. The lowest reading I’ve seen on the Wallbox app is 0.4kW which corresponds to 410W reported by HA.
Other readings which correspond directly are as follows…
Shelly Watts 1950 | 1450 | 1090 | 790
Wallbox Watts 1520 | 1170 | 870 | 670
This demonstrates the error of approx 25% between Shelly and Wallbox. Shelly agrees very closely with my Utility Meter (error 0.6%) so I know that Wallbox is reporting the wrong readings.
It’s interesting to note the series of reducing spikes right near the end and also the repeated sets of oscillations between the 590 and 690 Watt levels on the first chart from Shelly. No doubt other EVs would have totally different curves, and probably there are also variations between different software versions from Nissan. Seeing the variation in charging power with time gives a much clearer picture than watching numbers on the Wallbox app.
1 Like
Nice tracing. Interesting. Not seeing anything like that on either of our cars. Different ways to deal with cell balancing.
The charger current limit is minimal 6A, but the car can take whatever it wants below that. So, yes it can do that.
I see the current go from whatever the max is set at to zero end the end of the charge, But sometimes it stay at 350W for a few minutes. I believe that is the cooling fans still going.
1 Like
Hi there,
I’m thinking to purchase one of this wallbox, but i have some doubts.
Already have my home assistant all set with shelly em’s. Knowing how is the energy balance between the house consumption and PV production.
So, for Pulsar Plus automation with node red do i need the Power Boost optional or is the Pulsar Plus fully functional trough Automation with this nice integration?
Thanks in advance
Welcome @MRBetes 
I don’t think you need the extra energy meter from Wallbox which they call Power Boost. I have updates coming in from Shelly EM every 1 second. Then use a Node-RED ‘Smooth’ node to process the readings. Every 10th reading it sends a payload with the average of the previous 10 readings. This provides a stable result which triggers a recalculation of the charging power - Up, Down or Sideways.
Glad to hear you’re using Node-RED rather than the scripting language in HA. It’s much easier to program. If you do decide to buy a Pulsar Plus, I think you’ll be very pleased with what you can do through this automation. My dashboard supports 2 options - Solar-only or Grid and it’s all I need.
The Wallbox is is solid choice. It never let me down on the primary function, that is charge the car(s).
The connection with HA is under development, but mostly working fine as is.
You need the ‘Power Boost’ meter to use the Eco-Smart functions from Wallbox, but these functions currently cannot be controlled from HA. And it is not hard to implement similar functionality with HA and another mains power meter.
However, take note, that you may need the ‘Power Boost’ meter to protect your main fuse (limit the maximum grid current). That is why I have it installed. I would not want to rely on HA to do that for me.