In it’s simplest form the communication between an AC charger and the car is very limited, and the SoC is not communicated from the car to the charger.
The car communicates it’s state with the charger by means of the pull-up voltage.
For DC charging the protocol has much more functionality, including communicating the SoC. An AC charger can use the extended protocol, but I there is no real reason to do so.
So unless the Wallbox uses the extended protocol we will never see a SoC reading. It could be found out if the Wallbox uses the extended protocol by reading the PWM duty cycle on the control pin while charging. But it not so easy to access it. Maybe when I have some real time on my hands.
All, great news, the Wallbox integration has just been merged into the ‘dev’ version of HomeAssistant. That means it will probably be there for the next release as an out of the box component in HA. For the moment this version only includes the sensors (HA rules, one platform per Pull Request), but I will try to add the number component next.
So, I’m super excited, was a lot of work (a lot of rewrites and changes in the past days)
Skoda drives great, its really roomy and with the wallbox at home no range anxiety at all (so far I haven’t really charged anywhere else). So, really pleased with the move to an EV, how is the polestar?
The wallbox component consists of 4 separate parts, 1. sensors (so, everything that produces the data), 2. lock (the ability to lock/unlock the charger, 3. number component (pass a number to the unit, in this case the max current available) 4. switch (the pause resume switch). These 4 are separate because of the way HA works and I can only add them 1 at a time. So for now, I started with the sensors and I will add the rest in the future (but you can of course just use the custom component for now)
Thank you for the explanation. I use the custom component, it works great as it is.
Polestar is great. Charging at home with free excess solar works like a charm. But I make quite a few longer multiday trips for work, and I must say that charging in the wild (75% of energy charged) is not great. Far too many issues. Needs planning and then improvisation because the plan always falls apart.
Ive got a wallbox pulsar plus coming in a few weeks, we went for the powerboost option to potentially balance the supply if we ever reached 100A. Probably a waste of money but its a gadget so I couldn’t resist!
Is there anyway to pull data from the energy monitoring device it uses for this function? This would be a great addition.
today I received my wallbox Pulsar + and the integration was quite smooth.
Wondering why I’m not able to control the max current, isn’t supposed to be capable of editing this field?
Just realized that this seems to be related with my HA build. I have the latest one avialable for Docker where the field is not editable at all, but if I do the same integration on other HA version based on RasperyPi, it works as expected:
There is something special on the docker version that doesn’t support this number entity ? Let me know if someone else has the same issue. Happy to provide any aditional information you may need.
I don’t know about differences for the docker version. However, there is a basic version of this integration (without the number entity) integrated in the latest HA release. This version only has the wallbox sensors (so, no lock, pause and number), if this is the cause of your problem, just install the custom component and restart HA (then the custom component should take precedent).
Appreciate your feedback. No, I’m using the full custom integration as you see in the 1st picture, the problem is that the number entity slider doesn’t work for docker based images apparently . Do I need to costumize something under the yaml to full use this or its just go into the integrations and install it and list all entities as I, doing already?
OK, than double check that you are indeed referring to the ‘number component’ (I think there is also a sensor version that just shows the value). Also, choose the right lovelace card.
You can always go to the developer options / entities and click on the number component. You should be able to change it there.
The entity name looks to be the correct one:
But when I get back to the lovelace card, as you see when I hover the mouse on top of the field, I do not get the ability to shift up\down the value which would be something really nice:
But as refered the same exact configuration on a RaspberryPi4 HA image works correctly, therefore I’m saying the number entity has issues with docker based images. As alternate option for the number entity and the developer options (it’s not practical to change the number here for instance when you’re on the phone). Do you have other way to set the charnging A value via UI ? Already tested with a simple node red flow and it’s working without any problems, but I want to control it manually as well any inputs? Appreciate the great work you have done here…so I do understand if you don’t have by now a proper recommendation here.
I have the same set up, with a constraint of 50A total, so the powerboost option may come in handy. I also have the intention to read data from the power monitor.
I have not tried yet, but it should be possible to read data from the RS485 bus that is used for communication between the power monitor to the wallbox. There is a HA implementation for RS485. It will need a node (could be the RPi running HA, or some ESP, or …). I did not get any further than that yet because I’m very limited on time at the moment.
it’s not working at all independently the card you chose, I believe the issue is indeed related with the docker image, since as I told before within a RB4 HA image the number value works as expected(I mean I can select the charger). To workaround I have used nodered to set the value as soon it see the change on other side I had to the layout:
Quick question tought, since I don’t have the car yet to test. The charging protocol allows us to change the A’s freely without setting the Wallbox state to pause to change the value ? Meaning during the charging process, I’m able to change the A’s as many times I wish?
Hi Stein,
Hard to say, I currently have a PR open that adds the number component. After that gets merged I’ll work on the remaining 2 components (switch and lock).
Gr. Hessel
