Hello. I get this api error when I’m trying to “Turn charger ON”.
Failed to turn on the charger. Reason: post ‘/api/chargers/XXXXXXX/commands/resume_charging’: Failed, HTTP status code ‘400’
Anyone have a clue?
Maybe wait and see what Homey Energy will give us. Otherwise I think people use the power by the hour app?
Typically the error you get when no car is connected to the charger. The app just shows what the Easee API returns. You can check http response codes yourself in their public developer docs.
Suddenly getting the error:
Failed to set dynamic Circuit current. Reason: body used already for: https://api.easee.com/api/sites/796331/circuits/748055/settings
Anyone has any idea? Already restarted the app, but no luck so far.
Try the test version, it is solved there. Error occurs after the circuit current is changed - so it still works
1 Like
As far as I know not in this app, but the “power by the hour” app has summarizers that can do this for you
I was on Experimental and wasn’t able to charge. Rolled back to stable and then charging started. I’m using Piggy bank which I guess rely on your public capabilities. Made any changes there? 
That is a good catch, in the test version I have removed the measure_power.surplus capability in the Equalizer device. To be fully compliant with Homey Energy, the measure_power capability will from this version show a negative value when exporting energy. Previously, measure_power was import and measure_power.surplus export - both positive values.
Thanks for replying. I don’t have an Equalizer, but since “measure.power” now can be negative, could that change the “type” and possibly be a breaking change inside Piggy’s code for the charger?
The developer for Piggy have stopped developing it, so I fear I’ll have to test some edits and install through CLI when the test version reaches stable
I have the following problem: the charger can be readout, but when a command is sent, it goes wrong.
Does anyone have a solution for this?
Should be working in the latest version just moved from test to live.
Hi
After installing 1.8.4 my flow to change the dynamic charge current don’t fail anymore, but my charger don’t respond. So it stays on 6 amps all the time.
I’m guessing you are charging your car and want to adjust the dynamic charger current upwards?
If so, there is a confirmed bug in the charger firmware that Easse will fix (at some point). The recommendation is to use the dynamic circuit current until the bug is fixed.
I’m using dynamic circuit current. But my charger is not reacting after the new update yesterday.
I’ll forward the diag report, but the flow I can see is a bit odd.
A lot of actions in a short period of time
No need to stop the charger for setting the circuit current
2025-03-18T01:02:13.351Z, stop charging
2025-03-18T01:03:14.615Z, change circuit current to 16A on all three phases
2025-03-18T01:03:14.801Z, start charging
2025-03-18T01:03:47.482Z, stop charging
2025-03-18T01:04:49.667Z, change circuit current to 16A on all three phases
2025-03-18T01:04:49.753Z, start charging
2025-03-18T01:06:09.744Z, stop charging
2025-03-18T01:06:10.999Z, change circuit current to 6A on one phase and 0 amps on the other two phases
--end of diag log--
All actions return a http 200, ie accepted by Easee cloud - so I don’t see any evidence for the statement that the charger is not reacting.
Example
2025-03-18T01:03:14.615Z [log] [ManagerDrivers] [Driver:charger] [Billader] Action 'circuitCurrentControlPerPhase' triggered
2025-03-18T01:03:14.616Z [log] [ManagerDrivers] [Driver:charger] [Billader] - current: '16/16/16' amps
2025-03-18T01:03:14.616Z [log] [ManagerDrivers] [Driver:charger] [Billader] - actual used: '16/16/16' Amps
2025-03-18T01:03:14.616Z [log] [ManagerDrivers] [Driver:charger] [Device:0a13f5e2-3b7d-4316-8ef5-fa24c51721d5] [Billader] Setting dynamic circuit current to '16/16/16'
2025-03-18T01:03:14.617Z [log] [ManagerDrivers] [Driver:charger] [Device:0a13f5e2-3b7d-4316-8ef5-fa24c51721d5] Setting dynamic circuit current with data: {"phase1":16,"phase2":16,"phase3":16,"timeToLive":0}
2025-03-18T01:03:14.617Z [log] [ManagerDrivers] [Driver:charger] [Device:0a13f5e2-3b7d-4316-8ef5-fa24c51721d5] Invoking url '/api/sites/892557/circuits/839709/settings'
2025-03-18T01:03:14.796Z [log] [ManagerDrivers] [Driver:charger] [Device:0a13f5e2-3b7d-4316-8ef5-fa24c51721d5] Received empty response with status code 200
2025-03-18T01:03:14.797Z [log] [ManagerDrivers] [Driver:charger] [Device:0a13f5e2-3b7d-4316-8ef5-fa24c51721d5] Command result: {"statusCode":200,"isEmpty":true}
2025-03-18T01:03:14.797Z [log] [ManagerDrivers] [Driver:charger] [Device:0a13f5e2-3b7d-4316-8ef5-fa24c51721d5] Received empty response with status code 200. Considering command successful.
Same issue here
I tested a bit more myself and see that it doesnt work here either. I tried the command using curl and it also doesnt work there. I’ll ask Easee, but looks like a problem on their side.
What changed since last is that time in the Homey app is that to live is passed as an argument, which wasn’t the case before. I have removed that locally and tried, but it doesnt change anything.
1 Like
It was my problem after all, or well, anyhow, it is fixed in v1.8.5 which is awaiting Athom’s approval.
I looked at the docs when I added timeToLive and noticed that the phase properties were named phase1 , phase2 and phase3 - so I updated this in the Homey app and tested that I got an HTTP 200 back.
However, this doesn’t work. When switching back to dynamicCircuitCurrentP1 , dynamicCircuitCurrentP2 , and dynamicCircuitCurrentP3 , it works in the Homey app again
3 Likes
It seems that I have problems with the Easee app. I made a flow to charge my car with advanced flow and suddenly the flow stopt working. (a week or two ago it was still working). I tested everything I repaired the issue with the Dynamic circuit current (that I found in the data base) but now the Card “Turn Charger on” does not function it reports back with a time out. It seems that the turn off does work. I tested that by manual switching the Easee charger on (via the easee app) and let the flow switch it off again. The flow is running on a Homey pro 2018.
Does anybody have the same issues or even better does someone know how to fix this.
it is getting more weird, it seems that although the card does not finish the charger actually starts charging, it is only the flow that does not continue.
If I check the current values in the homey data it remains zero while in the easee app the power is 5 or 6 amps per phase depending on the set point I gave.
this is the error log: 2025-04-05T18:21:30.177Z
Error: post ‘/api/chargers/EH67SQ8H/commands/toggle_charging’: Request timed out after 20000ms
at invoke (/lib/Easee.js:514:19)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Easee.#postWaitForResponse (/lib/Easee.js:22:28)
at async Easee.toggleCharging (/lib/Easee.js:119:16)
