search

nordicopen / easee_hass

Custom component for Easee EV charger integration with Home Assistant
216 stars 37 forks source link

action: easee.set_charger_dynamic_limit - no longer works #463

Closed Mkay505 closed 2 months ago

Mkay505 commented 2 months ago

The problem

The action command: easee.set_charger_dynamic_limit is not working anymore. This command was previously ideal for controlling photovoltaic surpluses. As of today, only the maximum for 1 or 3 phases is possible for me. If I want to limit the current to 10 amps, for example, this is no longer possible.

Version of Easee integration having the issue?

0.9.59

Version of Home Assistant Core having the issue?

2024.9.1

Anything in the logs that might be useful for us?

No response

Additional information

No response

olalid commented 2 months ago

Could perhaps be same as this? https://github.com/nordicopen/easee_hass/issues/422 If not, please try to find something in the logs.

bverlinden commented 2 months ago

Might be related to a general issue with the easee api? See https://status.easee.com/incidents/z00bt9vnjykh

aifiks commented 2 months ago

I also noticed the same thing now.

Logs say: Logger: custom_components.easee.services Source: custom_components/easee/services.py:660 integration: Easee EV charger (documentation, issues) First occurred: 15:58:30 (19 occurrences) Last logged: 16:14:10

Forbidden : [set_charger_dynamic_limit] - Check your access privileges:

osulivanDE commented 2 months ago

Easee Cloud API is a mess. Please vote here for a local API: https://feedback.easee.com/b/features/local-apis/ Easee had this on the roadmap for at least 3 years now but still offers this unreliable cloud API

aifiks commented 2 months ago

I see that Easee confirms issues with their Cloud API: https://status.easee.com/

enoch85 commented 2 months ago

Could perhaps be same as this? #422 If not, please try to find something in the logs.

This is a a new issue and started a few days ago. Here are some logs from me. Most of it are selections from a much large log file, but these lines seems to go on repeat more or less.

2024-09-13 22:11:02.922 ERROR (MainThread) [custom_components.easee.services] Forbidden : [set_charger_dynamic_limit] - Check your access privileges: 
2024-09-13 22:11:57.226 ERROR (MainThread) [custom_components.easee.services] Forbidden : [set_charger_dynamic_limit] - Check your access privileges: 
2024-09-13 22:12:53.285 ERROR (MainThread) [custom_components.easee.services] Forbidden : [set_charger_dynamic_limit] - Check your access privileges: 
2024-09-13 22:13:22.466 ERROR (MainThread) [custom_components.easee.services] Forbidden : [set_charger_dynamic_limit] - Check your access privileges: 
2024-09-13 22:14:43.959 ERROR (MainThread) [custom_components.easee.services] Forbidden : [set_charger_dynamic_limit] - Check your access privileges: 
2024-09-13 22:14:43.996 ERROR (MainThread) [custom_components.easee.services] Forbidden : [set_charger_dynamic_limit] - Check your access privileges: 
2024-09-13 22:19:12.081 DEBUG (MainThread) [pyeasee.easee] No callback found for EHXXXXXX
2024-09-13 22:19:12.081 DEBUG (MainThread) [pyeasee.easee] No callback found for EHXXXXXX
2024-09-13 22:19:12.081 DEBUG (MainThread) [pyeasee.easee] No callback found for EHXXXXXX
2024-09-13 22:19:12.081 DEBUG (MainThread) [pyeasee.easee] No callback found for EHXXXXXX
2024-09-13 22:19:12.081 DEBUG (MainThread) [pyeasee.easee] No callback found for EHXXXXXX
2024-09-13 22:19:12.082 DEBUG (MainThread) [pyeasee.easee] No callback found for EHXXXXXX
2024-09-13 22:19:12.082 DEBUG (MainThread) [pyeasee.easee] No callback found for EHXXXXXX
2024-09-13 22:19:12.082 DEBUG (MainThread) [pyeasee.easee] No callback found for EHXXXXXX
2024-09-13 22:20:41.232 DEBUG (MainThread) [custom_components.easee.controller] Callback EHXXXXXX 195 state_inVoltageT2T4 241.86700439453125 3
2024-09-13 22:20:41.232 DEBUG (MainThread) [custom_components.easee.controller] Callback EHXXXXXX196 state_inVoltageT2T5 234.9739990234375 3
2024-09-13 22:20:41.232 DEBUG (MainThread) [custom_components.easee.controller] Callback EHXXXXXX 194 state_inVoltageT2T3 239.9239959716797 3
2024-09-13 22:20:41.232 DEBUG (MainThread) [custom_components.easee.controller] Callback EHXXXXXX 150 state_tempMax 29 4
2024-09-13 22:21:00.199 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXXsmart_charging
2024-09-13 22:21:00.199 DEBUG (MainThread) [custom_components.easee.switch] Getting state of smart_charging
2024-09-13 22:21:00.199 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX enable_smart_button
2024-09-13 22:21:00.199 DEBUG (MainThread) [custom_components.easee.switch] Getting state of enable_smart_button
2024-09-13 22:21:00.199 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX cable_locked_permanently
2024-09-13 22:21:00.199 DEBUG (MainThread) [custom_components.easee.switch] Getting state of cable_locked_permanently
2024-09-13 22:21:00.199 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXXis_enabled
2024-09-13 22:21:00.200 DEBUG (MainThread) [custom_components.easee.switch] Getting state of is_enabled
2024-09-13 22:21:00.200 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXXenable_idle_current
2024-09-13 22:21:00.200 DEBUG (MainThread) [custom_components.easee.switch] Getting state of enable_idle_current
2024-09-13 22:21:00.200 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX status
2024-09-13 22:21:00.200 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX power
2024-09-13 22:21:00.200 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX session_energy
2024-09-13 22:21:00.200 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update :EHXXXXXX lifetime_energy
2024-09-13 22:21:00.200 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX energy_per_hour
2024-09-13 22:21:00.201 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX cost_day
2024-09-13 22:21:00.201 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX cost_month
2024-09-13 22:21:00.201 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX cost_year
2024-09-13 22:21:00.201 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX circuit_current
2024-09-13 22:21:00.201 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX equalizer_limit
2024-09-13 22:21:00.201 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXXdynamic_circuit_limit
2024-09-13 22:21:00.201 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX max_circuit_limit
2024-09-13 22:21:00.201 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX dynamic_charger_limit
2024-09-13 22:21:00.201 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX max_charger_limit
2024-09-13 22:21:00.201 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX reason_for_no_current
2024-09-13 22:21:00.202 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX cost_per_kwh
2024-09-13 22:21:00.202 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX temp_max
2024-09-13 22:21:00.202 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX cable_locked
2024-09-13 22:21:00.202 DEBUG (MainThread) [custom_components.easee.binary_sensor] Getting state of cable_locked
2024-09-13 22:21:00.202 DEBUG (MainThread) [custom_components.easee.entity] Entity async_update : EHXXXXXX online
2024-09-13 22:21:00.202 DEBUG (MainThread) [custom_components.easee.binary_sensor] Getting state of online

2024-09-14 00:02:40.570 DEBUG (MainThread) [pyeasee.easee] GET: /firmware/EHL8TAED/latest ({})
2024-09-14 00:02:40.570 DEBUG (MainThread) [pyeasee.easee] verify_updated_token: 2024-09-14 01:01:14.984157, 2024-09-14 00:02:40.570649, False
2024-09-14 00:02:40.620 DEBUG (MainThread) [custom_components.easee.controller] Latest Firmware for EHXXXXX: 323
2024-09-14 00:02:40.620 DEBUG (MainThread) [pyeasee.easee] GET: /firmware/QPXXXXX/latest ({})
2024-09-14 00:02:40.620 DEBUG (MainThread) [pyeasee.easee] verify_updated_token: 2024-09-14 01:01:14.984157, 2024-09-14 00:02:40.620566, False
2024-09-14 00:02:40.665 DEBUG (MainThread) [custom_components.easee.controller] Latest Firmware for QPXXXXX: 122
2024-09-14 00:02:47.653 DEBUG (MainThread) [custom_components.easee.controller] Callback QPXXXXX 50 state_rcpi -74.5 3
2024-09-14 00:02:47.654 DEBUG (MainThread) [pyeasee.easee] No callback found for QPXXXXX

This messes with my charging as well, since it's not able to set Dynamic Amp per charger.

enoch85 commented 2 months ago

Btw, I don't know if Easee changed something in their API recently? Loggning in to easee.cloud it looks totally different from before.

Mkay505 commented 2 months ago

You only can set the dynamic value (temporary) in the easee app manually. First I thought the command was generally deleted or my wallboxes have a defect.

enoch85 commented 2 months ago

@Mkay505 It worked until like 2 days ago. Same app, same version of HAOS. So you mean it's gone from the API?

guydl012 commented 2 months ago

Same issue here. Last succesful usage 2 days ago.

enoch85 commented 2 months ago

Might be related to a general issue with the easee api? See https://status.easee.com/incidents/z00bt9vnjykh

Aah, saw this now. That might be it!

MarkP12345 commented 2 months ago

Same problem here, cant adjust the amperage any more in HA using this integration since a day.....(automation to only use the pv power for charging).

icefluffy commented 2 months ago

Same Problem here, I'm consuming from grid now...

bverlinden commented 2 months ago

I'm wondering when it will be fixed, my charger is stuck on 16A. I can't change the max limit of the loader using the Easee app since my CPO (e-flux) blocks this. So I'm dependant of the API which is now down for > 24hrs.

tmjo commented 2 months ago

Still not working. Cost me 100 NOK since I exceeded my grid limit this month because of this. Hail mary for local API, but not holding my horses as it has been promised since forever. It seems however like the dynamic circuit limit is working, so I'm temporarily rewriting my automations to send this command instead.

enoch85 commented 2 months ago

" We are continuing to work on a fix for this issue. Posted 1 day ago. Sep 13, 2024 - 16:11 CEST "

It's weekend, I think they (Easee) don't care about third-party API...

aifiks commented 2 months ago

Still not working. Cost me 100 NOK since I exceeded my grid limit this month because of this. Hail mary for local API, but not holding my horses as it has been promised since forever. It seems however like the dynamic circuit limit is working, so I'm temporarily rewriting my automations to send this command instead.

Thanks for the heads up that the dynamic circuit limit is still working! Since I only have one Easee charger, the dynamic circuit limit seems to function similarly to the dynamic charger limit in my case.

olalid commented 2 months ago

Please use the circuit dynamic limit instead if you can. If you only have one charger it is the better option anyway. I assume Easee are aware of the problem, but I have also reported it to them and asked them if we can change something on our end to make it work again. So, until we know more we will keep this issue open as information to others.

aifiks commented 2 months ago

Please use the circuit dynamic limit instead if you can. If you only have one charger it is the better option anyway.

Thanks. Out of curiosity, why is this approach better than using the dynamic charging limit?

olalid commented 2 months ago

The main reason I think it is better because it does not reset when a charging session starts.

aifiks commented 2 months ago

Aha! This resetting has bugged me forever. I’ll definitely use the circuit dynamic limit from now on. Thanks for clarifying! 👍🏻

kimmilde commented 2 months ago

I cant find charger_dynamic_limit longer in easee API documentation. Only circuit dynamic limit. Have they removed it without telling? Switched to circuit dynamic and its all working again! I need some stabil local api that doesnt change!

oivindklausen commented 2 months ago

If I remember correctly, changing Circuit Dynamic Current too often is not recommended since it is stored in non volatile memory? So, if you use it for load balancing current may change quite often.

In addition Enable/Disable Charger is not working any longer, you’ll need to set curren t =0 to disable charging

olalid commented 2 months ago

Anything called "dynamic" is ok to change more often. That being said, you should not call the services too often since you will hit rate-limits if you do that. Although, calling the service with the same values as already set will be filtered out and not actually call the API. It is the other limits, like charger max limit etc that is not recommended to uses for this kind of purpose.

MarkP12345 commented 2 months ago

Enable/Disable Charger is working again

enoch85 commented 2 months ago

Easee API now works again, This can be closed IMHO.

enoch85 commented 2 months ago

@Mkay505 You can close it. 😉