Discussions

Ask a Question

Default phase behaviour

Hi, I have a challenge: My car can charge on one phase, I have three phases in my house. The charger, which is fed all three phases, is fused with 20A. My house’s electrical load is distributed such that I can pull 20A from one particular phase at any time (phase 2), as no major appliances are connected to this phase, other than the charger. I would like a setup where I don’t have to adjust current ratings for individual phases continuously, but just have a setup that works under any conditions. Thus, I tried setting the maxCircuitCurrentP1, P2 and P3 to 8, 20 and 8 respectively – my assumptions was then, that when I plug in my car, it would default to the phase with the highest current rating (P2=20A), and if a guest comes over that can use multiple phases, they would be capped at 8A. However, with the 8, 20, 8A maxCircuitCurrent, when I plug in my single phase car, the charger just defaults to P1=8A. This can of course be remedied by either: a) Setting the dynamicCircuitCurrent to 0, 20, 0 (what I’m currently doing), this however means that I have to worry about and reconfigure the charger in the event of a power cycle of the charger, so it doesn’t start defaulting to P1=8A again. Or b) I could permanently set the maxCircuitCurrent for P1 and P3 to 0, forcing the charger to use P2, however in the event of a guest wanting to charge with multiple phases I would have the hassle of reconfiguring the charger to open up the other phases. My question is therefore; can the default behavior be changed to utilize the highest current rated phase when single phase charging, while still enabling multi phase charging, or can I achieve this in a smarter way than proposed in a) and b) Thanks!

Equalizer state API not correctly updating?

It seems like the activePowerExport parameter of the Equalizer state API response is not updating at all since the 20th of August. All other parameters seems to be updating as they should. The Equalizer reads the power flow to/from the grid from the HAN port of a fiscal meter (Elvia). Any ideas as to what the issue may be? Is it related to the Equalizer or the HAN port communication?

Slow changing settings

I change maxCircuitCurrentP1, maxCircuitCurrentP2 and maxCircuitCurrentP3 through the API. However it takes several minutes before the config is changed. What could be the problem?

Unlock connector

Hello, I have a parking place for which we share a Easee home charger. The two cars belongs to different people, so we don't have each other keys to unlock the cars. I thought by stopping the charge, it would unlock the connector, at least on Easee part, so we could easily switch charging without bothering each other to ask for unlocking the cars. I would like know how we could unlock the connector when the car has finished charging ? I saw that OCPP has a "UnlockConnector" command but I couldn't find in Easee api how to send it. Thanks

Dynamic Circuit Current

Intention of Post: This is to validate my understanding of the above topic when it comes to Master/Slave installations. Setting up Dynamic Circuit Current the following API is used: [[https://developer.easee.cloud/reference/get_api-sites-siteid-circuits-circuitid-dynamiccurrent]] I have come to recognize, that, while I setup the Dynamic Circuit Current (DCC) to a value X (i.e. 3x 20A) and a TTL of '0', the Master perfectly shows that setting when using the App to view the 'Restrictions'.... HOWEVER the Slave Boxes show 1000 A (!). Now this could be to not have to manipulate each Slave Box when the DCC changes... as one will stay below the 1000A limit as the charging current for the Slave Box is allocated by the Master. So... using both on the Easee App as well as using the 'Dashboard Circuit States' API [https://api.easee.cloud/api/sites/{siteId}/state]... both show me the 1000A for the DCC of the particular Slave Box. Is this as designed ? Tx, homa

Recently receiving an error "errors":{"":["A non-empty request body is required" by calling the API

Hello, I have developed a dynamic charging behaviour for my Easee wallbox via a Rule in Openhab. This was working fine now since a year or so. Without any change in my Rule I receive now the error: {"errors":{"":["A non-empty request body is required."]},"type":"https://tools.ietf.org/html/rfc7231#section-6.5.1","title":"One or more validation errors occurred.","status":400,"traceId":"00-7d4a626c10a5bc44a2c30078f0a67d67-1c95b612248de32d-00"} My call is via Rules in openhab which is Java based. It looks like: var String url = "" var String easeeRequestBody = "" var String json = "" url = "https://api.easee.cloud/api/accounts/token" easeeRequestBody = '{ "userName": "user", "password": "pw" }' logInfo("Info",easeeRequestBody) json = sendHttpPostRequest(url, "application/json", easeeRequestBody, 5000) Any hint whats causing this?

Seeing users ongoing sessions as admin

I'm admin of a site for my home owners association. We only use RFID for authenticating and starting a charging session. I want to run a script to be able to see which user is currently charging (all users use all chargers). What request(s) should I use? I noted that I'm forbidden from seeing other users charging sessions which seems weird to me.

Limit on endpoint calls - scope

Hi, I have a question regarding the limit on the state endpoint of 600 calls/5 min - is that per charge point, per site, per site owner account or per individual account? thanks in advance! Jon

dynamicChargerCurrent not working with 2 digit values?

Hey there, i've got a problem with the easee api. Got a normal HTTP Post request with working headers. Content is { "dynamicChargerCurrent": value } and thats working fine for 1 digit numbers (6-9). But when I try the request with 2 digits e.g. 10-16 its just not working! I don't get why it's working through the testing feature in the cloud API website, every other service i've used gets this error: {"errors":{"chargerSetting":["A value for the 'chargerSetting' parameter or property was not provided."],"dynamicChargerCurrent":["Unexpected end when deserializing object. Path 'dynamicChargerCurrent', line 1, position 27."]},"type":"https://tools.ietf.org/html/rfc7231#section-6.5.1","title":"One or more validation errors occurred.","status":400,"traceId":"00-8d2161f5affaa84e9dbcdf7839405461-11530d577ae7a542-00"} with the content being something like: {"dynamicChargerCurrent": 10} Anyone ran into the same issue?

SOC for the EV?

Hello! I see the answer, that it is not possible to communicate with the car, but anyway the charger somehow knows only to charge with approx 11KW (16amp) and not trying to put full 20amp which I have available? - So somehow the charger is communicating with the car? - Anyone who succeed to get in touch with Ford and their Development API's?