service keba.stop does not work

[mattsve]

Calling service keba.stop (no rfid specified) does nothing, the car keeps on charging. The disable button works fine, and so does keba.start service after the disable button is pressed.

Tried with version 3.0.3

[deqw]

I’m very happy with this integration because I now I’m no longer dependent on the (slow) BMW webservice to see if the car is charging or not. But like above I have a problem with starting and stopping charging via the integration. I have no RFID in use and therefore could not specify anything in the integrations setup. Start and stop now resulting in a authentication error. Is there a way to circumvent the RFID sequence?

[matlimatli]

I changed my scripts/automations to use

service: button.press
data: {}
target:
  entity_id: button.keba_p30_enable

for starting, (and button.keba_p30_disable for stopping). Could this be an option for you as well?

[pos-ei-don]

I do the same. As long as the charging is not stopped by the car (becaus the condifured soc is reached) enable will restart charging directly after hitting enable. I the other case, when the car stopped the charging, I have to send the "charging" command to the car via api aswell.

[deqw]

I changed my scripts/automations to use

service: button.press
data: {}
target:
  entity_id: button.keba_p30_enable

for starting, (and button.keba_p30_disable for stopping). Could this be an option for you as well?

That is helpful @matlimatli . I compared this to the call that the Call Service node is making in Node-Red:

So this is not resulting in the same call. I cannot get to a button.press service as far as I can see now. What I do see is that I can select a Keba domain in the node which can be used to start and stop. Which results in the following call.

I have to test if that is doing anything / the same as your automation call.

[deqw]

Although the call is looking different it isn't.

I see that:

Is picked up fine by the API:

The keba domain start/stop doesn't do anything from Node-Red.

[deqw]

Tested and can confirm this Node-Red route works fine, although it might not solve the @mattsve opening issue.