Since a while I dont get any sensor data at all, tried to reinstall in HA but same issue, all sensor says “unavailable”, any suggestions?
Did you find a solution?
The automation " Update easee charging price" (automation.update_easee_charging_price) has an action that calls an unknown service: easee.set_charging_cost.
This error prevents the automation from running correctly. Maybe this service is no longer available, or perhaps a typo caused it.
All,
I am preparing to go “full electric” as for my mobility. The choice of EV charger has been made, it is going to be Easee with the equalizer, mainly because of this integration in HA.
I have 2 burning questions to this community:
- Does anyone successfully use an RJ11 splitter on the P1 port, to feed both the equalizer AND HA system? I am currently using DSMR Smart meter with a direct hookup of P1 to my Pi4, and equalizer requires the same tap-in on the P1 port.
- How does this load balancing work when it comes to timing? I know the P1 telegrams from my smart meter have a lag of 5-10 seconds. I use 3 Phases and have solar panels returning on all phases. But if I am fully charging at lets say 11kW, no solar production, and all of a sudden my fridge and electric boiler kick in, isn’t the equalizer too late to prevent overload on any of the phase when this happens ?
Tnx,
John
I do something like this
sensors:
new_charge_watt:
friendly_name: Nieuw laadpaal setting in kWatt
unique_id: "new_charge_watt"
unit_of_measurement: "kW"
value_template: '{{ min(states("input_number.vermogen_maximum_in_kw") | float(0), max(states("input_number.vermogen_mininum_in_kw") | float(0), states("sensor.power_production") | float(0) - states("sensor.power_consumption") | float(0) + states("sensor.easee_charger_power") | float(0) - states("input_number.vermogen_marge") | float(0))) | round(0, floor) | int }}'
new_charge_amp:
friendly_name: Nieuw laadpaal setting in Ampere
unique_id: "new_charge_amp"
unit_of_measurement: "A"
value_template: '{{ max(0, min(40, (min(states("input_number.vermogen_maximum_in_kw") | float(0), max(states("input_number.vermogen_mininum_in_kw") | float(0), states("sensor.power_production") | float(0) - states("sensor.power_consumption") | float(0) + states("sensor.easee_charger_power") | float(0) - states("input_number.vermogen_marge") | float(0))))) / states("sensor.easee_charger_voltage") | float(0)) | round(0, floor) | int }}'
it results into a test template like this:
sensors:
new_charge_watt:
friendly_name: Nieuw laadpaal setting in kWatt
unique_id: "new_charge_watt"
unit_of_measurement: "kW"
value_template: '1.543'
new_charge_amp:
friendly_name: Nieuw laadpaal setting in Ampere
unique_id: "new_charge_amp"
unit_of_measurement: "A"
value_template: '6'
vermogen marge: 0.5
voltage van LP: 237.692001342773
nu terug op net: 0.642
nu laadpaal: 1.40100002288818
subTot Power: 2.04300002288818
min marge: 1.54300002288818
omgev. in Ampere: 6.491594223496973
omgev. in Ampere: 6
I can’t seem to run the service in the dashboard but I can put it in a script and run that.
Once I have checked the output of the variable thoroughly i will make an automation of it.
script:
alias: Set Dynamic charge liimt Easee
sequence:
- service: easee.set_charger_dynamic_limit
data:
current: "{{ states(\"sensor.new_charge_amp\") | int }}"
device_id: **************************************
mode: single
icon: mdi:lightning-bolt-circle
1 Like
Question about easee equlizer, how fast does your sensor update import_power mine is really slow and not getting the measurement in real time, anyone having the same problem or isn't the equlizer faster?
Mine seems not updating it as it should as well, I dont use any info from the Equaliser.
I have a P1 smart meter and that updates every minute.
Silly question maybe but I’m looking for an entity to start the charge so that Easee can control the start and stop instead of the car.
I’m using GitHub - jonasbkarlsson/ev_smart_charging: Electric vehicle smart charging for Home Assistant. to optimize the price, but I can’t seem to figure out which entity to use for starting and stopping…
Thanks!
1 Like
I use this template switch:
1 Like
Thanks! Been experimenting with that today, but I can’t seem to separate my two chargers independently, and using the Easee Charger Charger Enabled is not recommended as it writes to flash and may destroy it after a while.
Have anyone succeeded with this?
Hmmm you should be able to set the dynamic limit per device . Are you sure you send the device with the service call?
Yes, the service calls are separate, but it triggers both chargers since I’m behind an Equalizer (as it seems). Any idea how to solve?
You can read more here about my setup:
Ah I see ( I hope 
)
you use the service “easee.set_circuit_dynamic_limit”, you should set the dynamic limit to the charger itself. “easee.set_charger_dynamic_limit”
- show_name: true
show_icon: false
type: button
tap_action:
action: call-service
service: easee.set_charger_dynamic_limit
target: {}
data:
current: 30
device_id: 09*******************************79
entity: sensor.easee_charger_dynamic_charger_limit
name: Set 30 A 7.4kW
Thanks! Actually tried that yesterday but it didn’t trigger the start of the charger. 
It only went into “waiting for smart charge to start”. Pressing the stop switch made it pause.
The setting on/off is for me always on when someone is home and the charger is connected.
When you don’t want it to charge set the dynamic Amperage to 0
1 Like
@dictus.jurgen Do you also integrate some smart charging, or is it during a fixed period of time (schelude)? If smart charging, which integration do you use?
What I want to gain here is to charge when the price is at it’s lowest (new price every hour). I mean I could just skip integrating to HA all together and just set a schelude in Easee during like 02-05, but that would defeat my purpose 
Yes, I fluctuate the dynamic range when my solar panels return to the grid, with a margin (helper variable) and only change the dynamic range when the value is stable for 30s
I added the sensor value in message above
Actually… Now it works!
I created a few more tests and discovered that the charging didn’t start since the whole circuit was to low (because I set it to 0 A when stopping with the previous function). Enabling the circuit power again, then running the new automation with only setting the charger now works as intended.
Question is, will it put extra wear on the charger or the car? I’ve read the setting the whole circuit is recommended… EDIT: No it won’t but doing like this has side effects:
Btw, thanks for making my day!
1 Like