Energy per hour sensor ? #183

ujhede · 2022-05-08T17:02:25Z

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?

Not that i can think of.

Additional information

No response

olalid · 2022-05-08T20:10:01Z

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.
The value is supplied from easee cloud and we do not really know the exact algorithm behind calculating it.
But from the way it behaves I would assume that it is showing the amount of energy between hour marks.

PS. It would be nice to know what kind of problem you are seeing with the configuration panel?

TheEnergy · 2023-04-24T18:46:15Z

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
Is it possibel to get it to write it to the EHTEYW8B Cost per kWh sensor? so the hourly would match?

Could be nice with a script like this.

olalid · 2023-04-25T09:35:59Z

Yes, you can use an automation to write the current price to Easee.
I do not think that will mean that the price will be logged correctly throughout a charging session.
I think the price that is set when the charging starts is the one it will use for the whole session.
Not 100% sure though.
Something along these lines (untested):

- id: update_easee_price
  alias: Easee price
  trigger:
  - platform: state
    entity_id: sensor.nordpool_kwh_dk2_dkk_3_10_025
  action:
  - service: easee.set_charging_cost
    data:
      cost_per_kwh: {{ states('sensor.nordpool_kwh_dk2_dkk_3_10_025') }}
      vat: 0
      device_id: xxxxxx

TheEnergy · 2023-04-25T19:06:03Z

Seems to be on the right track. When i run the script, this happens.

alias: Price
description: ""
trigger:

platform: state
entity_id:
- sensor.nordpool_kwh_dk2_dkk_3_10_025
  condition: []
  action:
service: easee.set_charging_cost
data:
cost_per_kwh:
"[object Object]": null
vat: 0
device_id: cfcdc7cdf0eb5625e3341a9f62845bd1

So it report back is zero to easse.

Krabbee · 2023-10-23T10:46:58Z

I get the same error when using sensor.
cost_per_kwh:
"[object Object]": null
Can anyone help with that? :)

olalid · 2023-10-23T11:54:03Z

Can you show how your automation looks?

Krabbee · 2023-10-23T11:56:59Z

Can you show how your automation looks?

Right now it looks like this:

alias: "Easee Set Charging Price "
description: ""
trigger:
  - platform: state
    entity_id:
      - sensor.energi_data_service_buy
condition: []
action:
  - service: easee.set_charging_cost
    data:
      cost_per_kwh:
        - entity_id: sensor.energi_data_service_buy
      vat: 0
      device_id: 890d81a5e...
      currency_id: DKK

And the entity looks right.
But I get this error:

olalid · 2023-10-24T11:31:06Z

You can not use an entity_id: as input to cost_per_kwh.
You must provide a value, and you can do that with a template, similar to what I wrote above.
In your case it would probably be: {{ states('sensor.energi_data_service_buy') }}

Krabbee · 2023-10-24T11:43:59Z

You can not use an entity_id: as input to cost_per_kwh.
You must provide a value, and you can do that with a template, similar to what I wrote above.
In your case it would probably be: {{ states('sensor.energi_data_service_buy') }}

I tried using the suggested template, but that does not seem to work :(

service: easee.set_charging_cost
data:
  cost_per_kwh:
    '[object Object]': null
  vat: 0
  device_id: blabla...

Full automation:

alias: "Easee Set Charging Price "
description: ""
trigger:
  - platform: state
    entity_id:
      - sensor.energi_data_service_buy
condition: []
action:
  - service: easee.set_charging_cost
    data:
      cost_per_kwh:
        "[object Object]": null
      vat: 0
      device_id: 890d81a5ec62c...

olalid · 2023-10-24T22:55:39Z

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.

Krabbee · 2023-10-24T23:16:23Z

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.

I probably missed the quotation marks around the states(...) - it works now.
Thank you very much, @olalid

Mats1717 · 2023-10-25T08:14:28Z

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: ***@***.***>

olalid · 2023-10-25T14:42:29Z

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.

Mats1717 · 2023-10-25T14:49:30Z

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: ***@***.***>

ujhede added the support Support and questions label May 8, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Energy per hour sensor ? #183

Energy per hour sensor ? #183

ujhede commented May 8, 2022

olalid commented May 8, 2022 •

edited

Loading

TheEnergy commented Apr 24, 2023

olalid commented Apr 25, 2023 •

edited

Loading

TheEnergy commented Apr 25, 2023

Krabbee commented Oct 23, 2023

olalid commented Oct 23, 2023

Krabbee commented Oct 23, 2023 •

edited

Loading

olalid commented Oct 24, 2023

Krabbee commented Oct 24, 2023

olalid commented Oct 24, 2023

Krabbee commented Oct 24, 2023

Mats1717 commented Oct 25, 2023 via email

olalid commented Oct 25, 2023

Mats1717 commented Oct 25, 2023 via email

Energy per hour sensor ? #183

Energy per hour sensor ? #183

Comments

ujhede commented May 8, 2022

Question

What version of the integration are you using?

Anything in the logs that might be useful for us?

Additional information

olalid commented May 8, 2022 • edited Loading

TheEnergy commented Apr 24, 2023

olalid commented Apr 25, 2023 • edited Loading

TheEnergy commented Apr 25, 2023

Krabbee commented Oct 23, 2023

olalid commented Oct 23, 2023

Krabbee commented Oct 23, 2023 • edited Loading

olalid commented Oct 24, 2023

Krabbee commented Oct 24, 2023

olalid commented Oct 24, 2023

Krabbee commented Oct 24, 2023

Mats1717 commented Oct 25, 2023 via email

olalid commented Oct 25, 2023

Mats1717 commented Oct 25, 2023 via email

olalid commented May 8, 2022 •

edited

Loading

olalid commented Apr 25, 2023 •

edited

Loading

Krabbee commented Oct 23, 2023 •

edited

Loading