I just added the logging and tried both simply restarting or removing and adding the component anew. I don’t see anything specific in the core logs.
What could I be looking for?
Yep I’m on 2023.3.5 and 2023.3 all right.
What do you see? You should see at least some debug logs from the wallbox-ble component
Got it, but still no real reason - simply timeouts and stuff like that:
2023-03-21 10:20:08.192 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:20:15.329 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'bleak.exc.BleakError'>, Not connected to esp-mmwavetest @ 10.10.0.207!
2023-03-21 10:20:16.331 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:20:18.192 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:20:28.192 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:20:31.334 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:20:31.711 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:20:31.711 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:20:32.335 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:20:41.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:20:46.715 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:20:47.338 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:20:47.715 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:20:48.340 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:20:51.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:21:01.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:21:02.720 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:21:03.344 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:21:03.721 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:21:04.345 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:21:11.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:21:18.725 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:21:19.349 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:21:19.727 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:21:20.349 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:21:21.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:21:31.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:21:34.730 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:21:35.353 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:21:35.731 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:21:36.354 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:21:41.142 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:21:50.735 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:21:51.142 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:21:51.356 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:21:51.735 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:21:52.358 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:21:52.599 DEBUG (MainThread) [custom_components.wallbox_ble] Connected!
2023-03-21 10:21:52.600 DEBUG (MainThread) [custom_components.wallbox_ble] Connected!
2023-03-21 10:21:58.137 DEBUG (MainThread) [custom_components.wallbox_ble] Disconnected!
2023-03-21 10:21:58.137 DEBUG (MainThread) [custom_components.wallbox_ble] Disconnected!
2023-03-21 10:21:58.139 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'bleak.exc.BleakError'>, Not connected
2023-03-21 10:21:58.140 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'bleak.exc.BleakError'>, Not connected
2023-03-21 10:21:59.139 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:21:59.141 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:22:01.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:22:11.142 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:22:14.144 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:22:14.145 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:22:15.145 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:22:15.147 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:22:21.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:22:21.461 DEBUG (MainThread) [custom_components.wallbox_ble] Disconnected!
2023-03-21 10:22:21.461 DEBUG (MainThread) [custom_components.wallbox_ble] Disconnected!
2023-03-21 10:22:21.462 DEBUG (MainThread) [custom_components.wallbox_ble] Connected!
2023-03-21 10:22:21.462 DEBUG (MainThread) [custom_components.wallbox_ble] Connected!
2023-03-21 10:22:31.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:22:41.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:22:51.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:22:51.465 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'aioesphomeapi.core.TimeoutAPIError'>, Timeout waiting for response for <class 'api_pb2.BluetoothDeviceRequest'> after 30.0s
2023-03-21 10:22:51.466 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'aioesphomeapi.core.TimeoutAPIError'>, Timeout waiting for response for <class 'api_pb2.BluetoothDeviceRequest'> after 30.0s
2023-03-21 10:22:52.467 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:22:52.468 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:23:01.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:23:07.471 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:23:07.472 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:23:08.471 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:23:08.474 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:23:11.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:23:21.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:23:23.476 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:23:23.476 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:23:24.476 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:23:24.478 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:23:31.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:23:39.480 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:23:39.481 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'asyncio.exceptions.TimeoutError'>, Timeout waiting for connect response while connecting to 84:FD:27:7E:ED:3A after 10.0s, disconnect timed out: True, after 5.0s
2023-03-21 10:23:40.481 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:23:40.483 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:23:41.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:23:46.719 DEBUG (MainThread) [custom_components.wallbox_ble] Disconnected!
2023-03-21 10:23:46.719 DEBUG (MainThread) [custom_components.wallbox_ble] Disconnected!
2023-03-21 10:23:46.720 DEBUG (MainThread) [custom_components.wallbox_ble] Connected!
2023-03-21 10:23:46.720 DEBUG (MainThread) [custom_components.wallbox_ble] Connected!
2023-03-21 10:23:51.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:24:01.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:24:11.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
2023-03-21 10:24:16.725 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'aioesphomeapi.core.TimeoutAPIError'>, Timeout waiting for response for <class 'api_pb2.BluetoothDeviceRequest'> after 30.0s
2023-03-21 10:24:16.727 DEBUG (MainThread) [custom_components.wallbox_ble] Error: <class 'aioesphomeapi.core.TimeoutAPIError'>, Timeout waiting for response for <class 'api_pb2.BluetoothDeviceRequest'> after 30.0s
2023-03-21 10:24:17.727 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:24:17.729 DEBUG (MainThread) [custom_components.wallbox_ble] Connecting...
2023-03-21 10:24:21.143 DEBUG (MainThread) [custom_components.wallbox_ble] Finished fetching wallbox_ble data in 0.000 seconds (success: True)
Weird. Did you try restarting the wallbox? Can your phone connect to it over Bluetooth?
Yes, I can connect to it with the phone and I have tried restarting it, to no avail.
I will continue to test, maybe I can see if I find different ble proxies to use.
So, simple question
I have a few sensors in HA from my solar panel system.
- Current solar production
- Current house consumption
- Current battery solar system battery charge state
My system right now is set up, so that the solar inverter first tries to match the current consumption, then it tries to charge the battery to 100% and then anything in surplus there, goes back to the grid.
I would like an integration where i could set the battery charge state that i want to achieve before beginning to charge, and then after that it would take Solar production minus house usage and just set the charger to whatever is leftover.
Maybe even with a feature that adjusted the desired battery charge state across the day.
I want to get the battery as close to 100% before the day ends, but start off with maybe only 30% before it would start charging, and at noon i would have it bumped to 50% and then at 2 pm to 60 and so on. (It is better for the battery to NOT be fully charged before the afternoon, as my solar panels have a capacity of 7200 watts but the inverter can only do 3600 watt onto the grid and 3600 to the battery, so the more i can use in the beginning, the more i can actually produce during the day. When the battery gets to 100% the inverter can only receive 3600 watt from the panels, no matter how much they produce.).
Also, the logic would have to be intelligent enough to not count what it charges as “house usage” to stop it from starting and then the available wattage drops, and then it would stop and so on.
Can the integration do this…
PS. No i am not capable enough to program a script to do this, sadly. 
When you refer to “the battery” do you mean the car battery or a home battery? Short answer, yes, what you want is possible - not out of the box though; you will need to use ha automations or node red.
House battery…
I need the juice in the house battery for when the sun goes down, so ideally at the end of the day it should be at 100%
Me and Node Red are not good friends, i find it is clunky and needlessly complicated, i have literally spent hours and hours getting pretty simple functions to work…Without any luck.
So to understand your have the following ingredients:
- Solar generation of 7200 watt
- Your house consumption
- Requirement to charge home battery to 100% by the time the day is over
- Use excess solar to charge the car
I imagine you don’t want the car to drain your battery?
Are you able to regulate charging of your home battery? Eg. Reduce charging speed, switch grid/solar priority or force charge/discharge/idle?
If so you could use a solar prediction integration to estimate your expected production for the day, scale the battery charging based on target soc -/- start soc and on that basis turn on/off the car charger.
This integration though will just do that, start/stop charging of the Wallbox and allow a change of charging speed (for a 3phase charger like mine 4 - 11kw)
Hi
No i have no way of controlling the battery, the only way i can slow down the charging of the battery is to consume the power (To charge the car)
No the integration will only be allowed to use surplus solar, energy not the battery.
I need it to be able to adjust but only between 6A and 16A , this is 3600 watt max, single phase. (I believe 6A is the lowest the charger will go ?)
So you will need a combination of ‘charge what you can’ and ‘charge what you need’. Whichever has the highest demand.
The ‘charge what you can’ logic controls the charger using the excess solar power, but allowing the home battery to charge first. So the cut off for the grid current must be higher (allowing more current to go the to grid) than used for the home battery controls.
The ‘charge what you need’ logic must control the charger current based on the energy needed to charge the car from it’s current SoC to its target SoC by the time set to reach the target.
The charger current should be set to whichever demand is higher.
This can be realized in HA with the Wallbox as long as it has the right input. You can control on actual SoC if you have a real time number from your vehicle. Or you can control on charged energy based on the start SoC, target SoC and time, if you do not have access to the real time vehicle SoC.
Hi,
New to Home Assistant, installed it last week and got some integrations running including hte Wallbox one. It seems to be connecting nicely and some data is appearing. But now I have some questions with regards to automation. I have a Copper SB, a Tesla Model Y, Huawei solar pannels and battery. I still need to check the Huawei Solar integrarion and get it working on my setup, but I was wondering if it would be possible to automate a few things like 
- If between 10 AM and 10 PM the Solar battery has > 90% charge, and the car is connected to the Wallbox then start a charging session until solar battery < 40% or car stops charging due to it’s battery being full.
Is that something which would be possilbe ? Any pointers on how I can start working on this ?
Thanks a lot in advance !
Hi Norm,
Sorry to hear you’re still having the same old problem with Charging Power fluctuations. For me, this problem went away several months ago and hasn’t returned. Here is a graph for a recent charging session in ‘Solar Only’ mode…
I’m using Pulsar Plus firmware 5.13.11 and will be sticking with this version indefinitely as I see no reason to change. Perhaps you’ve upgraded to a later version and that is why the problem has returned?
Yep, I’m on version 5.16.37 big mistake updating past your version.
Bummer! Hopefully there’s some way to roll back to the earlier version.
Hi Stefaan,
I am doing something very similar to what you’re wanting to achieve. I don’t have any fixed rules about when the house battery is below 40% or above 90% charge. Instead, I look at how much power is being used to charge the house battery and if it’s more than 1400W, I can take some of it and start charging my EV. The house battery charger usually ends up being left with about half of the available power and the EV gets the other half.
The most important thing for me is to ensure that the House Battery is fully charged before the sun goes down, so if necessary, I can set a timer which stops the EV charger a couple of hours before sunset.
My EV charging dashboard is programmed using Node-RED. I started with the scripting language provided by HA, but it’s very limited in what it can do, and the syntax is really unusual. Node-RED is very flexible and uses a visual programming method, a bit like a flow chart. If you code it properly, your automations will be easy to maintain and you’ll be happy with the result.
“Delayed actions of up to 10 minutes” is causing me a lot of problems. I am completely OFF-GRID and need to get the WallBox to respond to actions like start charging, stop charging and amp adjustments within about 30 seconds.
Is there any hack around this issue?