easee REST Client | basic_charge_plan | suddenly affects day + 1 #51
Description
Using easee REST Client to schedule my charger and has been doing so for at least a year without issues or any changes.
Since yesterday 26th of November 2025 I started seeing issues.
The plan now suddely affects next day rather than todays date for some weird reason.
As an example sending this to the API:
url: https://api.easee.com/api/chargers/XXXXXXX/basic_charge_plan
payload: "{"chargingCurrentLimit":32,"chargeStartTime":"2025-11-27T06:00:00.000Z","isEnabled":true,"repeat":false}"
Resulted in a chargplan, according to the easee mobile app, that is set for 7AM CET (6AM UTC) "tomorrow" instead to "today".
I have now removed the scheduling functionality and rely of starting/stoping from nod-red instead (which probably works good enough).
Looked at chagelog for the API but has not found anything that would explain this.
I have a theory that I have not been able to verify yet.
Maybe this issue only happens if the chargeStartTime is set to a timestamp that has already past.
Will try to verify this as soon as posible. And avoid using the schedule functionality if this is the case...