Discussions

Ask a Question

RestSharp 107

I am new to Easee API... and RestShart. I am using C# and trying to adopt the sample codes for version 107 but I cant get it working... Anyone done this and are willing to share experience? Thanks!
ANSWERED

dynamicCircuitCurrent

Hello. I am creating load balancing for my Easee Home based on readings from my Electric Meter (HAN-Port). When I look in the API Docs then I find this: Load balancing is set by setting the Circuit Settings dynamicCircuitCurrentP1, dynamicCircuitCurrentP2 and dynamicCircuitCurrentP3. and then an example sending values to all three phases. https://developer.easee.cloud/docs/load-balancing But when I check the Docs for Set Circuit Settings, this is what I find. Please only specify keys you want to change. Endpoint handles partial JSON objects and will give a 400 response if it does not understand the request. Will only forward values for dynamicCircuitCurrentP1, P2, P3 to device if new value != old value https://developer.easee.cloud/reference/post_api-sites-siteid-circuits-circuitid-settings But if I follow the recommendation to only send the keys I want to change (dynamicCircuitCurrentX) then the other dynamicCircuitCurrent sets to 0 So I need to resend the same value for all dynamicCircuitCurrent if I just want to change one of them. Is this the supposed behavior?
ANSWERED

Tibber + using API myself

Hi, Did I understand things correctly if it's impossible to connect my Easee charger with Tibber while at the same time access the charger directly through my home automation using the API. Or is this possible somehow?

Can easee equalizer read PV current?

I Have solar panels installed. On sunny days i feed back 30KWH to the grid. Can the equalizer read the feedback power so the charger goes on when sun is shinning
ANSWERED

api/streams/amqp responding with 400

I'm trying to integrate our home charger to my home management system, and I seem to be unable to get the AMQP stream details - requesting them gives me a 400: ` curl -D- --request GET --url https://api.easee.cloud/api/streams/amqp --header "Authorization: Bearer NNN" --header 'Accept: application/json' {"type":"https://tools.ietf.org/html/rfc7231#section-6.5.1","title":"Bad Request","status":400,"traceId":"|8e1b6d3d-415148d1ce99decd."} ` It also fails using the (rather neat) "Try It" button at https://developer.easee.cloud/reference#stream, while other GET connections work there, as they do from cURL. So I know the auth is correct. What am I missing?

How to see if car is connected ?

Checking Observations was recommended by support, use ID: 109 (ChargerOpMode). Test: a car is connected and charging. Input: { "to": "2022-04-07T08:59:20.550Z", "from": "2022-04-07T08:44:20.550Z", "ChargerID": "EGJHJGJG-fake", "observationId": 109 } Output: 0 I only see previous observations that are completed (used different car) if i set date range to a day. How to check every minute is a car is connected (charging or NOT charging) ?
ANSWERED

car percentage

Does the Easee API (public or Partner) allow for the current battery percentage of the car to be displayed. I've seen this at all superchargers/fast-chargers around. I guess the car either reports it to the cars during the charge or the car anwsers if the charges requests.

Demo site

We are in the process of installing easee chargers in our community. Installation is not complete yet and we do not have a site in easee cloud. I am planning to use your public cloud API, is there a demo site that could be used to developed against until proper site is available?
ANSWERED

Smart Charging

What does "enable smart charging" do?

SignalR stream publishes non plausible state data

The SignalR stream of my Easee charger publishes non plausible data. The car is connected and charging but the I get `CHARGER_OP_MODE 0001` (disconnected) when I establish a new connection to the box. See the log below for details: ``` [easee ] TRACE 2021/12/10 14:49:36 ProductUpdate EH635870: CABLE_LOCKED true [easee ] TRACE 2021/12/10 14:49:36 ProductUpdate EH635870: CABLE_RATING 20 [easee ] TRACE 2021/12/10 14:49:36 ProductUpdate EH635870: CHARGER_OP_MODE 0001 << DISCONNECTED [easee ] TRACE 2021/12/10 14:49:36 ProductUpdate EH635870: OUTPUT_PHASE 0000 [easee ] TRACE 2021/12/10 14:49:36 ProductUpdate EH635870: DYNAMIC_CIRCUIT_CURRENT_P1 40 [easee ] TRACE 2021/12/10 14:49:36 ProductUpdate EH635870: DYNAMIC_CIRCUIT_CURRENT_P2 40 [easee ] TRACE 2021/12/10 14:49:36 ProductUpdate EH635870: DYNAMIC_CIRCUIT_CURRENT_P3 40 [easee ] TRACE 2021/12/10 14:49:36 ProductUpdate EH635870: OUTPUT_CURRENT 7 [easee ] TRACE 2021/12/10 14:49:36 ProductUpdate EH635870: DERATED_CURRENT 0 [easee ] TRACE 2021/12/10 14:49:36 ProductUpdate EH635870: DERATING_ACTIVE false [easee ] TRACE 2021/12/10 14:49:36 ProductUpdate EH635870: ERROR_CODE 0000 [easee ] TRACE 2021/12/10 14:49:36 ProductUpdate EH635870: TOTAL_POWER 4.714 << CHARGING [easee ] TRACE 2021/12/10 14:49:36 ProductUpdate EH635870: SESSION_ENERGY 1.636 [easee ] TRACE 2021/12/10 14:49:36 ProductUpdate EH635870: ENERGY_PER_HOUR 1.598 ``` I'm one of the evcc.io core devs and we haven't noticed this effect before. The REST API seems to work fine, there I get the correct opMode.