Easee EV charging station

Hei
I am looking for a solution to change operators on the charger without going in the app. The problem is that I use tibber for my privat car and PlugPay for my work car and would be nice to have a button on my dashbord to change between operators.

Hi all, thanks for the great project!
Would like to ask if the basic schedule and weekly schedule are supposed to be in “Unknown” state or maybe I did something wrong?
Thanks!

Does anybody see the same or maybe something wrong with my charger? Both weekly and basic schedule shows unknown - I do have basic schedule enabled. And it is unknown regardless if car is connected or not. I tried to reload the integration and didn’t help. Appreciate your suggestion!

I usually have this switch disabled but I enabled to check. It seems to work for me.

Maybe remove the schedule and readd it?

Hi, thanks for checking and strange it doesn’t work in my setup. There is no error in log and all attributes except for ID are empty…

Ok some further investigation and looks like I can use the switch to turn on/off basic schedule, however it never polls data from Easee so besides name and ID all other fields are Unknown…

Edit:
Can’t seem to remove it, the delete button is greyed out. I tried to remove my account and add it back, for some reason it remembers all entity names so same result…

Another edit:
Looks like regardless what I do the integration must write something to disk to remember all the settings. I have tried the following:

  1. Remove the account
  2. Delete the integration and restart
  3. Reinstall the integration
  4. Add device by Easee user account
  5. Every is restored include entity names, disabled entities etc, and the two schedule switch still won’t work for me

Enabled debug logging and follow the trace of schedule I can see below logs:

2025-08-26 17:00:40.435 DEBUG (MainThread) [custom_components.easee.controller] Adding entity: basic_schedule (switch) for product Car Charger, unit None
2025-08-26 17:00:51.979 DEBUG (MainThread) [custom_components.easee.switch] Getting state of basic_schedule

There is no further mentioning of schedule so assume the data never come?

@mhoogenbosch : one more question if you don’t mind. What version of the Easee integration do you use?

I have created a support case on this: Basic and weekly schedule data unavailable · Issue #636 · nordicopen/easee_hass · GitHub

I have version 0.9.71 installed.I guess the latest version.

But the schedule is created in the Easee cloud isn’t it? So it would make sense it is recreated using the entries in the cloud. My intention was to suggest removing the schedule all together in the cloud, not removing the button inside HA. Because the button in HA cannot be deleted since it is part of the integration.

Removing the integration removes all entities, but since the information is stored in the Easee cloud, it makes sense it readd’s all entities with the cloud values.

Ok thanks for checking - maybe some issue with Easee cloud as I can’t think of anything with HA or integration.

1 Like

Hey Martijn,

Ik zie dat deze tread al van even geleden is, maar is het je gelukt om de Easee aan te sturen op basis van de hoeveelheid solar welke je over hebt? Ik wil heel graag een soortgelijke automatisering bouwen, maar het wil nog niet echt lukken. Ook ik heb de Easee laadpaal, P1 meter van Homewizard en mijn SolarEdge omvormer alle geïntegreerd in HA. Met hulp van AI ben ik een heel eind gekomen, maar vooralsnog krijg ik de laadpaal niet ingeschakeld vanuit HA.

Mocht je wat hulp kunnen/willen bieden, heel graag!

Ja, moet zeggen dat het best aardig werkt bij mij. Waar gaat het mis?

Bedankt voor je reactie,

De Easee wil niet starten met laden, ik heb onderstaand script met hulp van AI gemaakt (heb geen programmeur achtergrond) Ik mis voor mijn gevoel een start / stop entiteit van de Easee welke je wel in de app hebt.

Als ik door alle berichten lees, zie ik wel dat je een pauze / start commando kunt gebruiken, maar ik begrijp niet goed hoe en waarom.

De sensor.p1_meter_power geeft aan wanneer er een overschot is wanneer hij in de min gaat. Dus simpel gedacht zou dit voldoende informatie moeten zijn om de auto te laten laden.
Hoewel het natuurlijk een volgend probleem geeft, dat wanneer hij laad, hij niet meer in de min zit en dus weer zou gaan stoppen. (maar ik had gehoopt dat ik hem minstens zou zien starten…) Dus ik ben me er van bewust dat de variables van -200 en -400 niet gaan werken.

Het script wat ik nu heb gemaakt is:

alias: Easee laden met solar overschot
description: Start/stop Easee laden afhankelijk van zonne-overschot
triggers:

  • entity_id: sensor.p1_meter_power
    for: “00:00:15”
    trigger: state
    conditions:
  • condition: state
    entity_id: switch.smart_charge_slim_laden
    state: “on”
  • condition: or
    conditions:
    • condition: state
      entity_id: device_tracker.starship_location
      state: home
    • condition: state
      entity_id: device_tracker.i3_120
      state: home
      actions:
  • choose:
    • conditions:
      • condition: template
        value_template: |
        {{ grid_usage <= drempel_start
        and states(‘sensor.smart_charge_status’) in [‘ready_to_charge’,‘waiting_for_start’]
        and (states(‘number.easee_EHQE****_max_current’) | int) == 0 }}
        sequence:
      • target:
        entity_id: number.easee_EHQE****_max_current
        data:
        value: 6
        action: number.set_value
      • data:
        message: Easee laden gestart met 6A (solar overschot beschikbaar)
        action: notify.mobile_app_iphone_van_joost
    • conditions:
      • condition: template
        value_template: |
        {{ grid_usage > drempel_stop
        and states(‘sensor.smart_charge_status’) == ‘charging’
        and (states(‘number.easee_EHQE****_max_current’) | int) > 0 }}
        sequence:
      • target:
        entity_id: number.easee_EHQE****_max_current
        data:
        value: “0”
        action: number.set_value
      • data:
        message: Easee laden gestopt (stroom terug naar 0A :partly_sunny::electric_plug:)
        action: notify.mobile_app_iphone_van_joost
        mode: single
        variables:
        grid_usage: “{{ states(‘sensor.p1_meter_power’) | float }}”
        drempel_start: -400
        drempel_stop: -200

I honestly don’t understand why you choose to create this yourself with help of an AI because I believe everything you need is a few post above. If you start with the post of @rayures you’ll be able to get this going. Your script is far to complicated for me to read (besides the code should be between brackets so it is better readable).

I’m using the scripts and code of @rayures , furthermore I turn on my charger when my car is ‘home’ and disable it when it is away. Because I don’t have a dynamic energy contract, I reset everything to 3phase and 16A at 11pm. At 6am I reset it to 1 phase and enable the automations. At night my max battery charge level is set to 60%, at 6am this is reset to 80%, making it possible to charge with solar power.

I also have an Override switch which enables 3phase 16A charging during the day when I wish to do so.

1 Like

Hi Martijn,

I understand now, I rebuild the ‘‘script’’ manually in the Home Assistant gui and I got it to work now. I was (as often) thinking too complicated. It works now, I don’t really need the 6A and more A option in my automation because my solar panels do not generate more power. You are right about the option to activate the charger when the car is ‘home’ and disable it when it’s away. I need to fix this part. Thanks for your response.

1 Like

Did you ever find a solution for this?

1 Like

Hi everyone:

Maybe a silly question: I only have 1 charger installed at home, should I set limit by circuit dynamic limit or charger dynamic limit?
I understand from the document the max limit should be untouched, and if I want to adjust power I should use circuit dynamic limit. But I notice there is also charger dynamic limit, so for a single charger would you recommend to use charger limit instead of circuit limit?
In Easee app I only find 2 settings:

  1. Temporaray charging limit
  2. Charger limit

How are they mapped to the HA entities?
Thx in advance!

Point 1 is a time based limit, so nothing to do with circuit or charger. I’m setting both tbh. Works for me

Thanks do you mean you use both circuit dynamic limit and charger dynamic limit and it works the same for you?
Appreciate your input!

I’ve been quoted for an Easee One charger. It seems to be the cheapest of the 7kw chargers that I’ve seen.

I only want the ability to turn charging on an off as I see fit within HA. I won’t be interested in programming in schedules.

Is this the car charger for me?

Hello everyone, at my home, three people charge their vehicles at the wallbox. One initiates the charging process via an app, while the other two use their own RFID chips. Is there a way to identify who initiated the charging process?

Wondering whether someone found a solution to this yet. Perhaps @Dmfutte or @dmartens who had the same issue have managed to find a solution?

I see that the EASEE charger also has an entity of “Session energy” however I can’t select this as an energy meter in the energy dashboard. Another idea was to make something that integrates the power usage but I’m new to HA and that sounds cumbersome and prone to failure too.