Skip to content

Add explanation of resume_charging-limitations #282

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

steinmn
Copy link
Contributor

@steinmn steinmn commented Aug 13, 2025

The stop/resume commands have some limitations that aren't very intuitive if you haven't struggled directly with the API (and maybe not even then). Added some clarification to the readme to hopefully reduce questions/confusion and avoid issues like #278.

Also correct some misnamed deprecated services.

The stop/resume commands have some limitations that aren't very intuitive if you haven't struggled directly with the API (and maybe not even then). Added some clarification to the readme to hopefully reduce questions/confusion and avoid issues like custom-components#278.

Also correct some misnamed deprecated services.
@sveinse
Copy link
Collaborator

sveinse commented Aug 15, 2025

There is one thing that itches a little bit in the restrictions we've setup for resuming charge and that's that only charge sessions which have been stopped by the command can be resumed. It sounds a little user unfriendly to me. I'm curious how Zaptec behaves in this respect. Next time I'm going to charge my car, I will test with Portal if I'm able to resume a charging if it has been stopped by the car.

@steinmn
Copy link
Contributor Author

steinmn commented Aug 15, 2025

We've only implemented the restrictions the Zaptec API told us to, so if that itches, the Zaptec devs are the ones that need to scratch it 😉

@sveinse
Copy link
Collaborator

sveinse commented Aug 15, 2025

Jep. But I'd like to check if they are doing it differently. If they are, we'd like to do so as well and add it to our feedback.

@sveinse sveinse added this to the v0.8.2 milestone Aug 15, 2025
@steinmn steinmn mentioned this pull request Aug 17, 2025
@sveinse
Copy link
Collaborator

sveinse commented Aug 17, 2025

Ok. I did some further testing to map out the behavior:

  • Set "Authorization required" off in Zaptec Portal

Test 1

  • Set "Charger max current" to 0
  • See that the charger mode is in "Waiting"
  • Press "Stop charging"
  • Charger mode switches to "Charge done"

Test 2

  • Press "Resume charging"
  • Charger mode switch to "Waiting"

Test 3

  • Set "Charger max current" to 10
  • Stop charging from VW app
  • Zaptec immediately observes the charger current to 0, but stays in "Charging" until a good while until it switch to "Charge done".

In the Zaptec App it sais "Charging stopped by car", which is not information this integration has. There is no button available in the Portal or the Zaptec app that allows to resume the charging from the charger side. I am able to resume the charging from the car side thou.

TL;DR: I'm happy with the PR and we can proceed.

@steinmn
Copy link
Contributor Author

steinmn commented Aug 17, 2025

In the Zaptec App it sais "Charging stopped by car", which is not information this integration has.

Goes on the #192 list?

@sveinse
Copy link
Collaborator

sveinse commented Aug 17, 2025

I think we need some more research on that before adding it to the list. There are so many strange things that happen when you stop the charging by the car. E.g. it takes Zaptec 3-5 minutes until it detects that the charging has stopped. So I don't think Zaptec and the car is exchanging any information about it stopping charging. The only thing Zaptec can do is observe that the current is 0. So I don't know if the information being presented is actual information or just something that's deduced from the observed state.

@sveinse sveinse merged commit d27017d into custom-components:master Aug 17, 2025
3 checks passed
@steinmn steinmn deleted the add-explanation-of-resume-limitations branch August 17, 2025 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants