tolwi
API stops to collect for ONE device (DELTA 2 MAX) and OK for all the others
Hi,
Since a few weeks, my DELTA 2 MAX is seen offline, and data are no more collected. Data are collected for a few minutes after a restart, between 4 and 5 minutes.
During the phase between online and offline, there is a recurring message in logs, that stops when the delta 2 max is seen offline
2025-01-24 14:43:23.563 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None) Traceback (most recent call last): File "/config/custom_components/ecoflow_cloud/api/public_api.py", line 80, in quota_all raw = await self.call_api("/device/quota/all", {"sn": sn}) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/ecoflow_cloud/api/public_api.py", line 100, in call_api return await self._get_json_response(resp) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/ecoflow_cloud/api/__init__.py", line 80, in _get_json_response raise EcoflowException(f"{response_message}") custom_components.ecoflow_cloud.api.EcoflowException: (('signature is wrong',), {})
Of course I tested to erase and re add the device with the same failure.
All others devices are OK : powerstream and smartplugs, with the very same API key.
Normal operation of the powerstream
2025-01-24 14:43:24.483 DEBUG (MainThread) [custom_components.ecoflow_cloud.devices] Finished fetching Ecoflow update coordinator data in 0.000 seconds (success: True) 2025-01-24 14:43:24.541 DEBUG (MainThread) [custom_components.ecoflow_cloud.devices] Finished fetching Ecoflow update coordinator data in 0.000 seconds (success: True) 2025-01-24 14:43:25.254 DEBUG (Thread-30 (_thread_main)) [custom_components.ecoflow_cloud.api.ecoflow_mqtt] Message for HW51XXXXXXX2361 and Topic /open/open-34153e3XXXXXXXXXXX4d9110c/HW5XXXXXXX2361/quota
Any idea ?
Kind regards
Hello everyone, is there already a solution to the problem? I've had the same error since yesterday, Delta 2 Max is no longer receiving data, the PowerStream works...
Has anyone found a solution for this? For me, the Delta 2 Max still doesn't deliver any data and is offline while the power stream is running. Everything works in the app...
My observations show that controls like switch.*_backup_reserve_enabledand number.*_ac_charging_power continue to work. Additionally after each such communication with EcoFlow API, sensor.*_status returns back to online and its attribute data_last_update is updated. However shortly after, quota_requests attribute starts to increment every few seconds until sensor.*_status switches to assume_offline when everything stops changing. Note, that from my experience the only way for data from API to be retrieved, is to restart HA, but even after restart only single reading is read and it subsequent updates never happen.
In my case not only Delta 2 Max but also PowerStream that is integrated via API has its sensor.*_status in assume_offline state.
Note that "older" approach with non-API (email/password) integration method (that is usually unstable, and periodically stops working), currently works, and produce meaningful data. I am not switching to it yet since it'll require a lot of changes both to dashboards and to template sensors and automations.
Still hope that someone more knowledgeable about EcoFlow protocol will be able both to explain and possibly fix the issue.
Unfortunately, the same situation still exists here. PowerStream works, Delta 2 Max is offline.
I have also tried to reconfigure the integration, but the Delta 2 Max is online for exactly 4 minutes and then goes offline forever...
I hope someone can offer a solution to this problem.
No, I haven't tested that yet. The PowerStream works too. I don't want to break anything else with it. And there's a 1.30beta3 in the works right now...
I also have the same issue (3 devices, data collection stops for one). Re-generating API key on EF Developer Portal worked fine. However, it would be great if integration provides some notification that API keys are old.
Does the newly generated code now run without problems and did generating the code work well?
Does the newly generated code now run without problems and did generating the code work well?
You need to remove the old code before generating a new one. Also you will receive 4 or 5 email code confirmations in the process, which is kinda ridiculous.
As for the integration - yes, works as expected after the key is refreshed.
@florismetzner @k-korn
Today I finally implemented and tested the new code generation. So far it's working perfectly :-)
Thank you for the tip!
However, it would be great if integration provides some notification that API keys are old.
Yes, that would be a desirable feature :-)
Have you tried a new API key?
I had the same issue, after setup values have not been updated properly, worked only for some time after reboot or once after pressing reload in the Ecoflow Integration configuration page.
Renewed the key a few minutes ago and since then it seems to work as normal, updating every few seconds automatically! HA OS 15 Home Assistant Core 2025.2.4
