@matli Maybe add this text to issue #17 on github?
2 Likes
Hm, i can choose all the stuff and push also the button (Dienst AusfĂŒhren), but nothing happens on my Keba Wall Box. What do I wrong?
Latest Home Assistant and Keba Integration is installed.
1 Like
Matli, I runned also in to same behavior with a BMW Connect charger. After authentication was disabled (on the chargers webUI) charger started as soon cable was connected, and if I stopped charging with HA-app it just started again and again.
The solution to this was automatization.
So basically how my integration is setup:
When connected, do nothing.
When disconnect set curr to 6A.
Charging is later done ether manually by setting a current (6A-16A) or setting up a start time in a schedule card.
First post/answer here at community, I have however read almost everything on this page because I was stuck with a BMW connect (Keba P30) charger that was kind of useless after our beloved car brand decide to drop all support for it.
So I want to send big thank you to you, dannerph and all other contributors on KEBA integration.
With your help my charger works better than it ever could even with BMWs app.
1 Like
Hey,
Did anyone manage to connect the BMW wall box gen4?
link for reference
Does it work with the input number number.abc_charging_current (âLadestrom setzenâ) ?
Maybe 22kW is too much for your model?
Is the new Keba P40 supported?
I donât think so. The P40 doesnât have an UDP interface which the core integration uses.
But it has Modbus TCP, or at least it will get it with a future update, so should be able to use that.
I have a P30 that sometimes works and sometimes doesnât. When it doesnât work, I get the following message:
Could not find a charging station at 10.0.51.155
After turning on debug logging, I think I know whatâs going on:
2024-08-08 20:22:55.873 DEBUG (MainThread) [keba_kecontact.keba_protocol] Asyncio UDP connection setup complete.
2024-08-08 20:22:55.879 DEBUG (MainThread) [keba_kecontact.keba_protocol] Send report 1
2024-08-08 20:22:55.991 DEBUG (MainThread) [keba_kecontact.keba_protocol] Send report 2
2024-08-08 20:22:56.095 DEBUG (MainThread) [keba_kecontact.keba_protocol] Send report 3
2024-08-08 20:22:56.218 ERROR (MainThread) [homeassistant.components.keba] Could not find a charging station at 10.0.51.155
2024-08-08 20:22:56.219 ERROR (MainThread) [homeassistant.setup] Setup failed for 'keba': Integration failed to initialize.
2024-08-08 20:22:56.408 DEBUG (MainThread) [keba_kecontact.keba_protocol] Datagram received.
2024-08-08 20:22:56.409 DEBUG (MainThread) [keba_kecontact.keba_protocol] Execute callback
2024-08-08 20:22:56.409 DEBUG (MainThread) [homeassistant.components.keba] Notifying 0 listeners
It looks like the response is received too late. My P30 is sadly only connected via WiFi, so I canât really do anything to test that theory.
Since this appears to be some kind of timeout, is there a way to increase it a bit?
1 Like
Hi matli,
Iâm currently working on a python script that starts charging when api prices are low. I believe you have done the same and I am wondering if you could share how you achieved that?
I have the same problem. The integration with my P30 worked. But since today I always get the error message âhomeassistant.components.keba] Could not find a charging station at xxxâ
My Keba P30 is still reachable via the IP Adresse (Web UI) and also via the Keba Portal. So the connection might be slow but without any problems.
I raised an issue on GitHub, but it doesnât look like the situation will change anytime soon: Keba: "Slow" response leads to "Could not find a charging station" · Issue #124129 · home-assistant/core · GitHub