Welcome Andrew. I wonder if during the process of trying so many integrations, things have become messed up somehow. Did you by any chance make a backup before you installed the first Wallbox integration? I find it’s always a good idea to do that, just in case things go awry.
If you have such a backup, restore from it and then install this ‘unofficial’ integration directly through HACS, using the Repo link you posted earlier (hesselonline).
After reading about the limitations of the official one, I never bothered with it, coming straight to this one via HACS. Upon starting the integration, the Configuration menu appeared which is where I was asked for serial number, password etc.
If you don’t have a backup, you may be able to start from scratch by first removing the integration via Configuration | Devices and Services, then go to HACS and Remove it completely from there.
Once you’ve got everything running correctly, I strongly encourage you to install the ‘Google Drive Backup’ integration, which keeps a copy of the latest 4 (or whatever number you choose) backups in the cloud, just in case your SD card, SSD or whatever gets trashed and you need to start again. Having invested so much time in learning the ropes of HA, developing a Pulsar Plus Dashboard in Node-RED, I don’t want to have to start again from scratch.
Hi Grant - Thank you… I have made some backups, but I think I will get a blank SD card tomorrow and start again. Once I have the WallBox integration working I will slowly add everything else. By pure chance I have the Solar Analytics solar monitoring system, and have 5 minute data points from that - so should be able to control the charger for an eco charge using Home Assistant (I hope)…
Redback Technologies (Australia) who provided my system, weren’t so forthcoming, only giving me access to a crippled API after weeks of waiting. Worst thing is, the Session Tokens expire after an hour and have to be renewed manually
So I gave up on that approach and installed my own Energy Meter in the switchboard, now connected to HA. Not the ideal solution, but it will allow me to automate charging according to excess solar power.
Yep, would be really great if all companies were happy to allow access to ‘our’ data… being able to control devices based on solar production is a great use of automation. Mind you, not much solar around here at the moment
Just a different opinion on the use of the official version versus HACS. I believe the limitations no longer exist and maintaining the official version is easier. So I strongly prefer, and now only use, the official integration. All functions work for me.
I found it helpful to start development with just a list of all available entities on the dashboard. Even if not all the entities make sense (added range), or even give data (state of charge).
Tried to change the integration - making the switch available on “Eco-smart waiting” is a piece of cake; however when triggering the switch an error appears:
File "/usr/local/lib/python3.9/site-packages/requests/models.py", line 960, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://api.wall-box.com/v3/chargers/MyChargerID/remote-action
A closer look at the my.wallbox portal shows that, through the cloud, the pause/resume button is not available either / greyed out, eg. this functionality seems to be not supported by the API. On the android app however, via bluetooth, the button is available and it is possible to override eco mode.
Are any of the wallbox team on this forum? Perhaps they can comment
I noticed they did make a contribution to the wallbox repo.
If I try moving the charge current slider, I get the error as my post 286 above. Interestingly, I can ‘move’ the slider and when I release it I get the error. It then jumps back to the old value. BUT, my phone app now shows the new charge current! So for sure the integration is talking to the charger.
If I then go to integrations and ‘reload’ WallBox, I get this (note: I changed the max charge current using the WallBox integration before ‘reloading’ - it did this with an error as explained)
Additionally, the lock button is not working in HA - but if I lock the WallBox using the phone app AND then ‘reload’ WallBox in HA, the charger status correctly shows locked.
Any ideas? This is a clean install of HA 8.1 64bit on a RPi4. The only think I have done is added the official WallBox integration. Thank you!
The problems you’ve encountered are the reasons why I’m sticking with the Unofficial (custom components) version for now at least. Also, I’m still running HassOS 7.0 and I’m not wanting to upgrade just yet. I prefer to stay a few releases behind the ‘bleeding edge’.
I’m using the official integration and the current slider works! I also added a sensor with a more realistic Added km for my IONIQ 5. Screenshot_20220608-083418|316x500
I have installed HA 7.0, and trying to install WallBox from GitHub. I have enabled ssh, and copied custom_components/wallbox to HA. After a restart I see no indication of a new integration available. Any thoughts?
I also tried (again, from a new 7.0 install) installing HACS, and then loading wallbox as a custom repo. The files are appropriately copied to custom_components, there is a wallbox tile in HACS, but nothing in it and nothing to configure, etc
This is the only integration I have had issues with (so far ) - I am using a RPi4 - could my issues be hardware related? Is there a better hardware choice for running HA?
I have also tried a clean install of 8.1, updated to 2022.6.4 - then the official wallbox integration installed.
Do these log errors help?
Error doing job: Task exception was never retrieved
2:09:23 PM – (ERROR) components/wallbox/sensor.py - message first occurred at 2:08:52 PM and shows up 2 times
Error while setting up wallbox platform for number
2:08:22 PM – (ERROR) Number
Error adding entities for domain sensor with platform wallbox
2:08:21 PM – (ERROR) Sensor - message first occurred at 2:08:21 PM and shows up 2 times
2022-06-08 14:09:23 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 137, in _handle_refresh_interval
await self._async_refresh(log_failures=True, scheduled=True)
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 270, in _async_refresh
update_callback()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 330, in _handle_coordinator_update
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 533, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 571, in _async_write_ha_state
state = self._stringify_state(available)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 539, in _stringify_state
if (state := self.state) is None:
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 388, in state
value = self.native_value
File "/usr/src/homeassistant/homeassistant/components/wallbox/sensor.py", line 174, in native_value
round(self.coordinator.data[self.entity_description.key], sensor_round),
TypeError: type NoneType doesn't define __round__ method
Andrew, I’m at a loss to understand what’s going on with your system and why this integration is causing you so many problems. This is only the 3rd integration I’ve tried and 2 of them needed HACS, so I’ve had to get to grips with it to some extent.
I’m also using a Raspberry Pi4 and made this choice after asking advice from users of the first integration I started with. The consensus was that it’s not the most powerful platform out there, but it’s capable of running fanless for light duties (such as this integration) and it’s a very simple way to get started with HassOS. So far, I’m very happy with my choice as I don’t intend using HA for much more than controlling my Pulsar Plus, running a few Shelly devices etc.
I have an Intel NUC running my weather station and video surveillance, and that would be my choice if the Raspberry Pi4 runs out of grunt. The NUC has been running faultlessly for almost 5 years now, but does have a tiny fan which is almost inaudible.
So I think your choice of hardware is not the issue. Are you running other integrations which require HACS, or only this one?
On my original installation I had GPIO on the RPi working with a HACS integration. Currently just a blank slate, trying to get WallBox working. I have now tried the official + github installations of wallbox on ‘blank’ versions of 7.0 and 8.1 with no success. There is communication with the charger - when I move the current slider on the integration dashboard I see the charge current change on the wallbox app on my phone - but HA throws an error, and does not display the new value. If I restart the wallbox integration, it then displays the new current value correctly.
OK, it’s good to know you’ve successfully used HACS for another integration. Did this other integration include a ‘Config Flow’ for its setup parameters?
No, I am not familiar with config flow… From memory in HACS, custom repositories, add the WallBox github link, restart, then go to integrations, SHIFT-Ctrl-R, then + add integration, search for WallBox and add. Does that sound right?
Yes, I think so, I would need to know the exact status description on which you want the button to be available. Please first test that this indeed works when using the wallbox app (to prevent enabling a flow that won’t work in practice)
Please only use the official integration from this moment forwards, it should offer a similar amount of capabilities. The ‘custom’ version is no longer being maintained.
