-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Energy per hour sensor ? #183
Comments
There is no exact timing when sensors update, this is just how the easee cloud works, it does not push out updates to all connected clients at the same time because that would use far too much bandwidth. PS. It would be nice to know what kind of problem you are seeing with the configuration panel? |
Im kinda hijacking this thread, but its like the same question. I have a sensor nordpool_kwh_dk2_dkk_3_10_025, that give me this output 1.971 DKK/kWh Could be nice with a script like this. |
Yes, you can use an automation to write the current price to Easee.
|
Seems to be on the right track. When i run the script, this happens. alias: Price
|
I get the same error when using sensor. |
Can you show how your automation looks? |
Right now it looks like this:
And the entity looks right. |
You can not use an entity_id: as input to cost_per_kwh. |
I tried using the suggested template, but that does not seem to work :(
Full automation:
|
This works for me:
Your sensor has a different name of course, so your template will be different. |
I probably missed the quotation marks around the |
Hi Olalid
Below works for me but the slave charger has a delay for about 5 minutes
before it changes. Master update directly when new hour.
alias: Elpris Easee Garaget Utsida
description: ""
trigger:
- platform: state
entity_id:
- sensor.nordpool_buy
condition: []
action:
- service: easee.set_charging_cost
data:
cost_per_kwh: "{{ states('sensor.nordpool_buy') }}"
device_id: b2b21358e8e36127da43d458d0c93d5c
mode: single
Den ons 25 okt. 2023 kl 00:55 skrev Ola Lidholm ***@***.***>:
… This works for me:
- id: elbil_laddkostnad
alias: Elbil laddkostnad
trigger:
- platform: state
entity_id: sensor.elpris_total
action:
- service: easee.set_charging_cost
data:
charger_id: EHxxxxxx
cost_per_kwh: "{{ states('sensor.elpris_total') }}"
vat: 0
Your sensor has a different name of course, so your template will be
different.
In your code above you have "[object Object]": null instead of a template.
If the automation editor does not allow you to create it the correct way,
you need to edit the automation manually.
—
Reply to this email directly, view it on GitHub
<#183 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5V43TWBL5U3D5PRPEX26QLYBBBPRAVCNFSM5VMFXHY2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZXHAYTQMJVGEZQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Ok, I do not think there is anything we can do about that. You can complain with Easee about if you want, but they typically have intentional (random) delays in sending out data so that things that happens at specific times are not sent out to all clients at exactly the same time to avoid bandwidth issues. So my guess it is not a bug, it is by design. |
Ok. Not a big problem.Just wanted to report what I been seeing👍Skickat från min iPad25 okt. 2023 kl. 16:42 skrev Ola Lidholm ***@***.***>:
Ok, I do not think there is anything we can do about that.
What we do is call the API to change the price setting and monitor changes sent back from Easee cloud.
If the cloud delays the response for a slave charger it is just the way it is.
You can complain with Easee about if you want, but they typically have intentional (random) delays in sending out data so that things that happens at specific times are not sent out to all clients at exactly the same time to avoid bandwidth issues. So my guess it is not a bug, it is by design.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Question
I am trying to calculate the cost of a charging session using hourly rates and the energy per hour sensor from this integration.
I am having a bit of trouble figuring out what value the energy per hour sensor exposes. It seems to be update every hour around 10 mins past the hour but the time does not seem to be consistent. Smetimes it updates at 5 minutes past.
Is the sensor value the total charge energy since the last update or is it in the last "clock hour" ?
What version of the integration are you using?
manua installation easee (opening the configuration panel give an error)
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: