No, Node Red was not requesting any reports at the time from the log.
Now however my load shedding is sending an keep alive current setpoint signal. But it is not really influencing it i think.
Good to optimize the performance. I think it would make more sense to use the t_UDP_pause times that kecontactp30udp_pgen manual.
What is triggering the request at this moment? Which file has that part of the code?
As I am relatively new to HA, I came upon this integregration and was able to setup my SolarEdge EV charger, which is basically a P30x in disguise.
The integration works perfectly and I can use the slider to change the charging current when charging.
What I am not able to figure out is how to automate that charging current value. What I would like is to use the excess power from my PV to charge the car. When the power drops from the PV, the charge current (or better the power) should drop and vise versa. That would allow to maximise the use of the PV power. Somehow, Iām not able to send a number value to the current entity.
Edit: I was able to set the number using the āset_valueā service in the number domain. This set the value to the wanted current as well as turned on the charging when set to a value between 6 and 32.
Hi @jongbj
Do you also have a SolarEdge inverter for your PV array?
I have a SolarEdge inverter and a Keba P30 X-Series.
My inverter is connected to the network using Ethernet, and I use the SolarEdge Modbus integration for Home Assistant, and also Dannerphās Keba integration.
I then use a custom automation that I wrote to have the excess solar funneled into the car by increasing/decreasing the MaxChargeCurrent on the EVSE. this automation maintains the MaxChargeCurrent at a minimum of 1.4kw so that the charge session isnāt constantly stopping and starting as the clouds pass.
You could also look into evcc.io which is available as a HomeAssistant add-on (I will probably move to this at some point). Itās just tricky for most as while the UI supports English, all the documentation is in German.
@OttoJager
t_UDP pause should be respected if I am not wrong. current update time is 5 seconds, if a command is sent, the update time decreases to 1 second (for faster response) for a while.
@jongbj
For Automation, I would advise to use the corresponding services (you can check them under the development tools).There is also a set_charging_power service, which (once charging has started) calculates the corresponding charging current depending on the number of phases the EV is charging and the locally measured voltage values.
Hi @dannerph,
I have a question regarding RFID Tag handling. Can you explain little bit more about RFID class. I really not getting how it works. I only want to read the RFID Tag which is currently used for charging.
If I read RFID Class I will get different number for each charging session but the RFID tag used for charging in this case is still the same.
Thanks a lot for your effort
Hi @schmersgahoven
the RFID class is directly coming from the report 1xx and corresponds to the color code of the RFID card (at least for my BMW Wallbox plus). I just checked, there is also the RFID tag within this report according to the manual, I can add it in the next beta release (currently too busy to work on the integration sorry).
@markroly : I have a similar situation but with a home-battery. Iām trying to get it working in a way that Iām not draining my home-battery to charge the car.
I think I can set this up by using the power send back to the grid as a reference (as that is excess and does not go to or come from the home-battery).
EVCC.io seems to be doing what I want it to do, however, as far as I can tell, it is a web-based service. Iād rather have it integrated into Home Assistant. You indicated it could be installed as add-on, but I could not find that. The German is not an problem for me.
@dannerph : Thanks will use that. Do you know how many messages the EV charger can handle. I had it setup to update the power level every second and that seemed be a bit much.
Hi!
I would like to change the keba.set_current with an helper āinput_number.suncharging_currentā. Is this possible?
I have been trying different variants like the below, but no luck.
data:
current: (states("input_number.suncharging_current") | float )
service: keba.set_current
What do you think?
Hi,
for sure it works. You have to use:
service: keba.set_current
data:
device_id: **ID OF YOUR KEBA**
current: "{{ states('input_number.suncharging_current') | float }}"
Many thanks!
ā¦but where do i find the device_id?
My Keba only shows up as several entities?
If i use the Dev tools / Template i get āNoneā if i for instance try
{{ device_id(āsensor.keba_p30_total_energyā) }}
Go to dev tools > services and choose the keba set current service.
There you can pick your wallbox from the dropdown list and create a yaml service call.
Then you have all needed items for the data section.
Thankā¦but it looks like Iām missing something in my Keba installation. I just do not have any drop down menu?
That is strange. On my install it looks like this:
This is keba beta integration 3.0.3 from hacs and HA 2023.6.1
Ehumm, i might not have updated it for a while 
Cheers
Hi,
I have a Keba P30 branded as a solaredge EV and manageable via the solaredge apps.
I am able to use the integration from HA (I use the beta version 3.03 from @dannerph. Thanks a lot to him!) and it works great, except to enable/start the charge.
I suspect that is the RFID class which is wrong but I have no idea of the value to use. I tried to keep the empty value and I tried to use a value which has been sent when I started the charge via the solaredge app but both failed with error āauthorization rejectedā.
Any idea of the RFID class value to use?
Thanks for your help
jay
Hi @jayjay1,
Iāve had the same issue. Iāve then started a charge within the app and were able to stop it through HA.
Since then am able to start/stop it with HA. the message of āauth rejectedā still is present, but not hindering me.
BR,
surfer2100
I have the same problem.
Sometimes it works disabling āsolar excessā in SolarEdge app.
Hi @jongbj Iām having the same SolarEdge setup (charger, battery) and use Node-Red to set the Solaredge Home Hub inverter command modes. This way I (can) maintain the home battery charge when charging the car or otherwise when I donāt want the battery to drain. Since you have this SolarEdge setup can you say something about the way the EV charger is configured and works with this. integration? Do you have a card reader installed? (I donāt and am running into an authorization error). Do you have still the SolarEdge firmware (1.14) or did you put in the Kabe firmware 1.17 already? Thanks!
Since I just spent a little too long time on debugging my scripts, I might as well share what I found here in case someone else gets bitten by it:
I have a python script that controls my EVSE based on the energy price and my current load. Since I donāt want to trip my main circuit breakers if Home Assistant goes down, I run my Keba in Failsafe mode. In order to not trip the failsafe, I periodically call set_current with my calculated maximum allowed current level. When the script wanted to stop the charging, the disable command was used.
When upgrading to version 3.0.0 of the integration, I started getting weird problems; When I stopped the charging due to high energy price, the unit restarted the charging by itself a few seconds later, causing a toggle loop which didnāt fel healthy. I didnāt have time to debug this, so I reverted to 2.4.0 until now.
After a debugging session, I realized that the set_current service of keba_kecontact now always uses the currtime command. Previously the curr command was used when delay was set to 0, which it was by default. The difference here seems to be that calling currtime with a current value other than 0 will start the charging, while curr will not.
In my case, my problem was easily solved by periodically setting current to 0 when I donāt want to charge.
