No that is what the “dynamic” value is for, setting the other values avery few seconds would indeed be bad for the chargers health
1 Like
Another question, people here with two chargers, how do you prevent the charging to start when the cable is connected?
I find the entity for “car plugged” on my car is super bad since it lags.
EDIT, nvm - solved it! This is with two chargers. Condition; permanent locking can’t be enabled as it’s checking if the cable is locked or unlocked on the Easee charger.
alias: EV smart - Tesla inkopplad
description: ""
trigger:
- type: locked
platform: device
device_id: 07xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
entity_id: acxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
domain: binary_sensor
condition: []
action:
- type: turn_on
device_id: 74xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
entity_id: 03xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
domain: switch
- service: easee.set_charger_dynamic_limit
data:
current: 0
device_id: 07xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
mode: single
1 Like
Thinking about replacing my Tibber pulse with the easee load balancer. (Equaliser)
I guess it’s still a cloud api?
How often does the values update?
Is there any noticeable lag?
It updates every 10 second or so, pretty much the same as if you would observe if in the Easee-app.
Hello, I’m a newbie here and I was able to integrate my Easee Home and see the entities.
I also have an entity from my “Smart Meter” PowerOpti with the current load (positive or negative).
Now I want an automatic charging when the load is below - 1.3 kW (I use only one phase loading).
And I want the possibility to manual override that and to manual choose a current from 6 to 32 Ampere.
Anyone has a similar setting and/or is willing to help me?
Thanks in advance!
hi! newbie here, is it a bug hassle to ask how you managed to integrate a ‘pause charging’ button on your HA dashboard?
so far i only managed to integrate some ‘monitor only’ parameters
You need to look into Call Service.
The integration has a number of services and actions.
Had my Easee One installed today and trying to figure out the best way to automate charging. Or more so, which service is the correct/best to call.
I’ve got a number of automations setup from when I was using a Granny Charger through a Smart Plug based around electricity prices - happy with these and want to continue to use them.
Am I right in saying that I should be using Pause/Resume and there is no need to use Start/Stop?
The Easee API docs seem to indicate that Start/Stop is around device authorization - so if my Easee One is always “Open” this shouldn’t be required?
I’ve seen some comments about using Dynamic Charging and changing the current instead. Is that a preferred way to turn charging on/off?
Hi, the best way is to control it by using the Easee Circuit dynamic limit. Any values below 6A on a single phase will probably stop charging the car (imagine most EV’s are the same on this), and everything above will charge, where you can dynamically set the charging rate (especially helpful if you have solar panels, like we do, and want to only use the excess solar power to charge the car). Here’s the yaml for the service call
1 Like
I have a problem where my integration “works” (i can see the device, toggle controller etc on/off) but it does not generate a device_id / charger_id etc that i can use in services to start/stop/pause, change limits etc, has anyone bumped into a similar problem?
2024-05-14 12:38:48.450 DEBUG (MainThread) [custom_components.easee.controller] Found charger: SOMETHING SOMETHING{‘id’: ‘SOMETHING’, ‘name’: ‘SOMETHING’, 'levelOfAccess’: None, ‘userRole’: 1, ‘productCode’: 1, ‘backPlate’: {‘id’: ‘SOMETHINGbackplate’, ‘masterBackPlateId’: ‘SOMETHINGbackplate’, ‘name’: None}, ‘isTemporary’: False, ‘color’: None, ‘createdOn’: ‘2021-09-24T10:50:05.255956’, ‘updatedOn’: ‘2022-01-18T12:27:06.706292’}
Can this levelOfAccess be the reason? on the “Site”-line i have levelOfAccess: 1 …
Please open Developer tools and go to to the Services tab. Select the service “Easee EV Charger: Action command” and the target device box should be populated. You can change to YAML mode if you want to see the actual codes.
If you can control the charger from the integration, your access level should be OK.
1 Like
Nothing there unfortunately…
I recently moved from a borettslag (HOA (?)) where i was a end-user and i could control that one OK, but now with this new-to-me charger that I am the owner off I dont get a controllable device_id
I can controll the charger with toggling the actual charger on and off, but i have a feeling thats not the best way to do it…
OK, then there is an access/permission problem. Make sure that the new charger and the new site are properly added to your account, both on the easee web-site and in their app.
1 Like
Thanks, looked into it and I don’t see anything that should be a show-stopper there, although i had to create the site from scratch since the previous owner were an older couple which didn’t use the smart functionality…
I don’t have a ‘Installer’ set on the site-level, do you by any chance know if that has any effect? (In other words the company that installed the charger isn’t set, list doesn’t contain that company…)
And public/private/open does that have any effect?
I guess the easiest is factory reset and start over …
Edit: seems like last update fixed it for me, didn’t really do anything that I hadn’t tried before…
This block gives this error in 2024.05.3, what am i missing ?
Unnamed automation could not be validated and has been disabled: extra keys not allowed @ data['switch']
The template sensor i created as a Helper as the automations.yaml did not like that block.
I have installed EV Smart Chargeing station and I see the sensors as well as services but the integration doesn’t affect the Easee charger.
Recently saw that is now possible to connect and control via bluetooth. Do you guys think this will be in place of local network accessibility?
I’ve tried (unsuccessfully) to find anyone who has tried to access the charger via bluetooth. But with this and e.g. an esp32 as bluetooth proxy, we should (theoretically) be able to have local control in HA now?
Hi folks,
is it possible to increase or decrease the value of the `circuit_dynamic_limit
I tried
- service: easee.set_circuit_dynamic_limit
metadata: {}
data:
current_p1: {{ states('sensor.easee_box_dynamisches_stromkreislimit') + 1 }}
time_to_live: 0
device_id: dad6e72558fb5067a3f61ecc2471669a
but this doesn’t work
How can I start charging, when der Easee Box Status is awaiting_authorization ?
@Baujahr70, I don’t know if you have solved this, but I did yesterday, sort of. I wanted the charger to open automatically when the car parked in front of it (I have the charger and my house in the middle of my small town, and I spend a lot of time at my cabin outside of town, so anybody could connect to it in the meantime). To do that I put a BLE beacon in the glove compartment, and that is registered by ESPresense setup in the house (which also unlocks the door for our phones and keys), and using an automation that makes the presence detector into a device tracker.
But I could not find a service to open charging, so I instead opted for setting the charger as open (which means that anybody can charge) and use the service to turn off and on the carger. So when the device tracker for the car goes from not_home to home, the charger is activated, and when the device tracker for the car goes from home to not_home, the charger is turned off. I hope that helps! Text