v1.2.0: Values ​​are not updated or are updated very slowly

[Neewieedo]

With the current version, the data is unfortunately still very rarely updated. Do you have any idea why this might be?

[walderston]

I'm seeing this too.. HA logs showing

Annoying thing I spent Friday ripping out the ioBroker version I was using. Switched part of my automations back to that and it's working again.

[benjaminmaza]

Same here with delta 2. Also, impossible to update values like "ac chargin power", "max charge level", etc. V1.1 or 1.2.

[ChristianReallyTheBest]

Same here with delta Pro2. Also, impossible to update values like "ac IN power" V1.1 or 1.2.

[sirdir1972]

I have the same problem, data barely updates anymore. What I don’t get - I understand the new version should be able to use the public API. That would mean looging in with acces key and secret key, not with user/password. But I don’t see anywhere how to do that.

[Nick75wien]

Hello! Same here! I mainly have problems with the data from the Powerstream! I get the data from the Delta PRO with this integration: https://github.com/vwt12eh8/hassio-ecoflow

The data on the PS does only update when I reload the integration!

[cezzz674]

Has anyone found a solution to this problem?

[mattpeufpeuf]

I wrote an automation that reload integration each minute

alias: Recharge integration ecoflow description: Reload each minute at 6sec trigger:

• platform: time_pattern seconds: "6" condition: [] action:
• data: entry_id: sensor.powerstream_inverter_output_watts action: homeassistant.reload_config_entry target: device_id: YOURIDDEVICE mode: single

[Nick75wien]

Does it work?

[mattpeufpeuf]

Work great is a big word for that... In red it's since the automation

[walderston]

@mattpeufpeuf hafe you tried deleting your current access key and generating a new key?

Every time you restart, you're actually making the issue worse.

I was initially doing that last week, then on Sunday evening generated a new access key (you have the delete the current one) and updated the devices in HA to use the new key.

As long as I don't restart HA (or keep restarting it) then it's fine.

[sirdir1972]

I was initially doing that last week, then on Sunday evening generated a new access key (you have the delete the current one) and updated the devices in HA to use the new key.

But where do you even enter your access key? I only get asked for username/password.

[walderston]

First one I name the EcoFlow device name as you need to add a new entry for each device.

[mattpeufpeuf]

Thank s I think that it works back with a new api key.

[cezzz674]

I can confirm that creating a new API key solves the problem. But everything will stop working again after rebooting the system

[Nick75wien]

I can confirm that creating a new API key solves the problem. But everything will stop working again after rebooting the system

rebooting HA? this we can't prevent!

[walderston]

I can confirm that creating a new API key solves the problem. But everything will stop working again after rebooting the system

How many EF devices do you have connected to HA?

[cezzz674]

Я могу подтвердить, что создание нового ключа API решает проблему. Но все снова перестанет работать после перезагрузки системы

Сколько устройств EF подключено к HA?

I have delta pro and 2 powerstream

[sirdir1972]

First one I name the EcoFlow device name as you need to add a new entry for each device.

I found it out last night, I had to completely deinstall the package, then it asked me whether I want to use the public server or not. Before it just kept asking for login/password of the private server.

[florismetzner]

Had the same error. Using 1.2.0 with official API and 1x D2M and 1x powerstream. Restarting the interaction brings it back to live for a glimpse of a moment. But values are not updating after a while. Just deleted my API credentials and made a new key and secret, reconfigure the integration and it works like a charm!

[Neewieedo]

Just deleted my API credentials and made a new key and secret, reconfigure the integration and it works like a charm!

...and does that work permanently or only until to the next reboot?

..and do you have to delete the old code or is it enough to simply create an additional new one?

[florismetzner]

Have not rebooted yet, not possible yet but I'll observe it and I'll report if the problem returns..

It is necessary to delete the old credentials before you can obtain new credentials. Furthermore it was good enough to reconfigure the existing integration

[walderston]

If you reboot HA a couple of times the issue will return. You're limited to 10 client ids daily/per 24 hours.

[ChristianReallyTheBest]

[1.2.0] @florismetzner, @Neewieedo : hello everyone, for DELTA Pro (2) , I tested a new key, and it still takes more than 20 seconds to refresh "AC In Power" for example. So I always come back to using the application API, gsm on on the Ecoflow application to get my necessary data within 2 seconds. It would be nice to go back to before "I don't know what", with data that worked well in complete independence. Will we get there? Does anyone have the answer? Is there any hope?

[sirdir1972]

If you reboot HA a couple of times the issue will return. You're limited to 10 client ids daily/per 24 hours.

The client ID should be generated once and never changed for an installation, I‘d say.

[florismetzner]

Agree, but I think that every connection generates a new (session/client) ID

[Hydrocephalic]

Same issue here, but it seems to me the API key regeneration solves the issue.