Pause/Resume Charger not working

[osulivanDE]

Question

When using the new action_command to pause/resume the charging session i get the following Error in Home Assistant Logs:

Logger: custom_components.easee.services Source: custom_components/easee/services.py:478 Integration: Easee EV Charger (documentation, issues) First occurred: 3. November 2022 um 22:15:14 (142 occurrences) Last logged: 10:00:14

Failed to execute service: action_command with data {'charger_id': 'EH3RMYID', 'action_command': 'pause'}

I trigger the service out of Node-Red. Here i get an green message, the service could be triggered but Home Assistant logs an Error. This is how i trigger it in Node-Red:

Server: HomeAssistant Domain: easee Service: action_command Data: {"charger_id":msg.chargerID,"action_command":"pause"}

Do i maybe put wrong Data into the Service?

What version of the integration are you using?

easeee-0.9.46

Anything in the logs that might be useful for us?

No response

Additional information

No response

[astrandb]

Is there anything interesting in the full HA log?

Have you tried to test the service in Developer tools in HA, there you can switch between UI and yaml mode to see the generated data.

You can turn on more detailed logging by entering following into configuration.yaml

logger:
  default: info
  logs:
    pyeasee: debug
    custom_components.easee: debug

[osulivanDE]

Thanks astrandb for your fast answer. I tested the service out of the dev tools and could generate the same error

But it seems this charger also has some other problems:

The Charger looks great in the integration interface and sends data... strange.

[osulivanDE]

Update: when i trigger Actions out of the integrations tab (for example activate/deactivate Smart charging) i get no error in the logs. So basic communication seems to be fine.

[astrandb]

The error indicates that the API does not accept the command when there is no car connected to the charger.

[osulivanDE]

Oh, yes. That is true. There is no car connected at the moment. Did this behavior change with the new action_command? I can´t remember this was a problem with the old start/resume command.

Thanks so much for your help.

[astrandb]

We are using the same API call, so there should be no differences in behaviour.

[osulivanDE]

I will update my script to trigger pause/resume only when a car is connected. Thanks so much :)