Add explanation of resume_charging-limitations#282
Conversation
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.
|
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. |
|
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 😉 |
|
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. |
|
Ok. I did some further testing to map out the behavior:
Test 1
Test 2
Test 3
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. |
Goes on the #192 list? |
|
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. |
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.