This is a custom component, you can download on it from my github and install it in your home assistant directory.
Now it works. Many thanks for this Integration and help. I have access to my wallbox 
Just installed a wallbox (pulsar plus) and this just what Iâm looking for. Great work. But, Iâm stuck.
I have copied all files in \custom_components\wallbox from github to the same directory on the HA server (RPi). That should be enough?
Of course I have restarted HA (several times).
I have warnings in the log about the wallbox integration, but no errors.
I have other custom components running. But still I cannot make the mywallbox integration show up under Configuration -> Integrations.
What am I missing?
what is the full directory path where the component is located? for me it looks like this:
Thank you for picking this up. Yes that is exactly what it looks like.
As usual with Home Assistant, with enough trail and error everything is possible.
I did a few more hours of clearing browser cache, restarting and dances around the table and got it working. I donât know what made it work, but it does!
Fabulous. The only thing missing now is the car ⌠Expected delivery next month.
@hesselonline do you have any plans to get this added to HA officially? Have a Pulsar Plus here & love your integration, but would like to avoid HACS use.
hi, you donât really need HACS, just copy the component files in the correct directory and restart HA. Iâm not using HACS as well. Regarding your question, I have thought about it, however, it would first need some additional cleaning up etc. Also, I havenât contributed directly to the HA project, so I donât really know the requirements etc.
1 Like
This is really good! Looking forward to try it with the car connected (patience âŚ).
One small thing, it seems that the current limit did not get a unit assigned?
I donât have a current limit sensor in HA? Did you change the name in HA? More in general, I gave unit types to sensors of which I knew (or thought I knew) what the type was. So the âunknownsâ are indeed without a unit. If you know what something should be, give me the name of the sensor and unit and I will see what I can do.
Also, Iâm trying to get this component added to HA Core. Its a lot of work, code needs to comply to different standards and everything needs a unit-test. Also, it is a requirement that you add only 1 platform in a Pull Request. So, for now, I have a working pull request for only the sensor component (https://github.com/home-assistant/core/pull/48082). It seems that the HA team is pretty backed up, so if some of you know how to, please contribute by reviewing the pull request
what car have you ordered? Iâm impatiently waiting for my Skoda Enyaq 
You are right I did rename it.
It is the ânumber.wallbox_portal_max_charging_currentâ.
When I click it on the glance card, I get the detail and I can set it. I donât think I will ever need it because I have a power booster (strange name for a current limiter) with a Carlo Gavazzi EM112 set up at 50A to limit the total mains current.
While Iâm at it:
The sensor âsensor.wallbox_portal_max_available_powerâ strictly spoken has the wrong name since it reports the available current, not the available power. Iâm hoping to see this number change when the power booster (current limiter) becomes active.
Thanks again for this great integration.
I have a Polestar 2 on order.
Good that we have home assistant to keep us busy while we impatiently wait 
Nice car!, yep, something to keep us busy between installing a charger and waiting for the car
Yes, I do see that the number component doesnât have a unit. I might add that later on (bit busy now with trying to get it integrated in HA core)
For some reason my SoC is not availiable, so it returns âUnknownâ. Would it be an idea to let it return a number to make the Gauge Card happy? (added as issue on Github too)
I also wondered, OCPP is availiable now, any plans on following that route? GREAT work anyway, thank you for making it possible at all!
There is a solution for that. In the configuration.yaml define a new numeric sensor that takes its value from the state of charge sensor. Like so:
#Sensors
sensor:
# Wallbox
- platform: template
sensors:
wallbox_portal_state_of_charge_numeric:
value_template: "{{ states('sensor.wallbox_portal_state_of_charge') | float | round(0) }}"
unit_of_measurement: "%"
I use this for my SoC gauge (that is always on zero because I am still waiting for my car âŚ)
I would rather not have the existing sensor changed because it works better in the glance card like this.
PS
Not my invention. Had the same issue with the some sensors of my SMA solar inverter and found the answer in the forum.
Regarding the State of Charge question, my car isnât here yet, so I have no real world examples. However, the sensor is formatted as a percentage with no rounding. If you can show me some examples / explain the exact issue I might be able to change something there.
@Krolykke, you also left a question regarding charge time on github. I donât think that HH:MM is an existing format type / unit type in HA. I could make a text sensor with that value, but that would make it quite limited in its use. If you have an example of another integration that shows the data this way, let me know. I could of course change seconds into minutes.
New version on github. The number entity is now formatted as Amperes, duration is in minutes.
1 Like
My five cents worth about the State of Charge; There is nothing wrong with the way it is defined. Sensor values in HA are reported as a string (I read somewhere in the documentation). That is why in the in the glance card it can show up as âUnknownâ, which is correct, no vehicle is connected. The gauge card however needs a number and struggles with âUnknownâ. Therefore the work around by generating a numeric version of the sensor value for the gauge card.
I had a look at the data coming out of the api. The state of charge sensor is, for my wallbox, None. This is an empty value in python and shows up as unknown in HA. So, technically this is correct, however, it might not be useful for daily use. We could convert it on the fly and replace None/unknown with a 0. Would that work for you?