Ola Lidholm

Hi, You have likely misunderstood what the stop commands purpose is. See https://developer.easee.cloud/docs/settings I.e. it does not do anything if your charger is not set up with authorisation with RFID...

I personally prefer to use the dynamic circuit limit instead of start/stop/pause/resume. It just always works independent of what mode etc you are in. Set it to something less than...

If you have 2 chargers connected to the same circuit, setting the dynamic circuit limit to less than 6A will stop both cars from charging, yes.

Well, it is only charger dynamic limit that is reset on re-plug, not circuit dynamic limit. There are in any case a lot of different ways to accomplish the same...

Sorry, I do not know if the is_enabled switch it writes to flash. It ends up calling this API: https://developer.easee.cloud/reference/post_api-chargers-id-settings That is all I can tell you... All I can...

You can use the service easee.set_circuit_dynamic_limit to 5 A or lower. That will stop charing from happening. And then change it to whatever max current you want when you want...

It would be tricky to implement this with schedules since the API has no "memory" about what schedule was previously used. So you can not just "enable" something that was...

Yes, the app probably remembers what you set the last time.

There is actually another way you could do this. There is already a service call easee.override_schedule. If you call that service charging will start independent of the schedule. Maybe not...

@skela Are you sure? I seem to remember that just get a 404 error back when no schedule is set and we call the API to fetch it...?