-
-
Notifications
You must be signed in to change notification settings - Fork 639
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
Issue/easee prevent parallel start stop #8433
Issue/easee prevent parallel start stop #8433
Conversation
This reverts commit 64cb372.
Co-authored-by: andig <cpuidle@gmx.de>
Co-authored-by: andig <cpuidle@gmx.de>
Co-authored-by: andig <cpuidle@gmx.de>
Co-authored-by: andig <cpuidle@gmx.de>
Co-authored-by: andig <cpuidle@gmx.de>
Co-authored-by: andig <cpuidle@gmx.de>
Co-authored-by: andig <cpuidle@gmx.de>
Co-authored-by: andig <cpuidle@gmx.de>
Co-authored-by: andig <cpuidle@gmx.de>
Co-authored-by: andig <cpuidle@gmx.de>
Co-authored-by: andig <cpuidle@gmx.de>
This is ready for review / merge again. I have tested locally, including reset of the WB to replicate the scenario that @kai-morich had. |
ich teste gerade deinen PR branch. Warte noch auf Sonne für 1p3p-Umschaltung, sieht aber soweit gut aus. Lädt korrekt, keine Warnings, keine unnötigen Requests. folgende Sequenz zeigt schön das Verhalten mit leerer response.
|
LGTM! |
Fix #8398
Followup to #8307, removed retry logic for empty responses, as according to new found understanding of the API these will always yield the same result.
Marking as draft for now. Will have to wait till sunrise tomorrow to see if this works.