1

Revoking charging authorization via "stop_charging" is not working


M
Mike Pieper

When I configure the charger to require authorization for loading, it waits for authorization before it starts charging.
That means I can send API command resume_charging and nothing happens. Only when I send start_charging the charging starts. That's OK up to here.

But now, when I call "stop_charging" the charging goes on! That's not correct. According to API documentation it should stop charging and revoking authorization.
Charging can be paused with pause_charging, but also here the authorization remains.

A

Activity Newest / Oldest

M

Mike Pieper

Do you have at least a work around?
The aim is to keep control over the charger. I don't want that it automatically starts charging after a power loss or on a cloud outage.

Another idea would be to disable/enable the charger. This works for the power loss case. At the last cloud outage I found the charger loading but I am not sure if it was started before by my home automation.

But the question is: Does this wear out the EEPROM?


A

Alek Slater

Status changed to: Identified

A

Alek Slater

Yup, this is unfortunately a known issue, that's just not been prioritized yet, sorry about that.