Delta Pro Update WLAN V3.0.2.21 Port is free again and the Integration works.

[claudeju]

The port is free again and the integration works.

[emmvaueff]

@claudeju What have you done? I also have these versions, but my integration looks like this and no device or entities.

[claudeju]

I contacted Ecoflow support then I received the update to WLAN V3.0.2.21.
I thought that this was a regular update

[emmvaueff]

@claudeju As I wrote before, I also contacted Ecoflow support and I received the update to WLAN V3.0.2.21.
But no device or entities ans also an empty integration. How is this looking in your HA?

[Gneves82]

I have contacted support and in the same day, remotely, they have open the communication. Note: the software version of my DP was not updated.
Then I had to delete everything related to Ecoflow in HA and integrate everything again, and it worked.

[PaulHamburg]

@Gneves82: which FW does your DP have? And how old is your DP?

[Gneves82]

Manufacture 2021
FW: V3.0.2.21(Wi-Fi)

[rt1970]

Is the firmware also available for the Delta MAX 2000?
My App shows only Update to 3.0.1.11

[imbrianj]

Thank you for this update - I reached out to support and they were able to upgrade me to 3.0.2.21 and this Home Assistant integration started working again.

[arnieatgit]

I got also the 3.0.2.21 Firmware after a 2nd try with the support. Did anyone of you tried to cut the connection from the Delta Pro to the cloud services? If i disable it on my firewall the local WiFi connection of the battery is also disabled and not reachable from HA. I would like to cut the direct connection to the battery from the cloud services (automatic Firmware update with removed features, turned off output plugs.... is not what i like to have in my infrastructure)

Also a problem is if the cloud services are not reachable for any reason also the HA integration and automation isn't working anymore, that's a real problem for my setup.

[dltccf]

I have two Delta Pros, both are on V1.0.1.49 one has WiFi V30.1.11 and doesn't work, the other has Wifi V0.1.0 and does work. Both report this version is up to date. I noticed that if I do the IoT reset on the box that doesn't work, it will work for maybe 30 seconds and then HA reports disconnect. When you contacted them, did they just update the wifi version or did they also roll back your firmware to V1.0.1.18? I really like the new energy management feature in 1.0.1.49 and don't want to lose that. I asked for that a year ago and it works like I requested. I assumed it rolled out to everyone. Was it not an update that everyone got? Do I have to request anything in particular when talking to them or can I just ask to update the wifi to 3.0.2.21 to work with home assistant?

[arnieatgit]

Late reply, but I'm currently on V1.0.1.49 and V3.0.2.21(Wi-Fi) and the HA integration works.

[PaulHamburg]

…does it work local with all 69 DP-Entitys or only over the EF cloud?

[arnieatgit]

local - but the local access to the API works only when the Delta Pro is able to communicate with ecoflow cloud. (tried to cut the connection to the cloud but then also the local API/Port isn't reachable anymore)

[PatternWorks]

local - but the local access to the API works only when the Delta Pro is able to communicate with ecoflow cloud. (tried to cut the connection to the cloud but then also the local API/Port isn't reachable anymore)

I have the same behaviour with my River Max, if I cut internet access on my router, I lose local communication after approx 30 seconds.

I'm currently on Wifi firmware version 2.0.9, with the offer to upgrade to 3.0.1.11 (which I won't take, because this seems to make things worse, and I'm not sure if there is a version 3.0.2.21 available upon request from EcoFlow support for the River models?)

I guess the question is, Is there a way to fool the device into thinking it is connected to the Ecoflow cloud, and keep the local access alive? I have a Raspberry Pi available, could I spoof the EcoFlow cloud servers with it?

[nxxxse]

Thanks @arnieatgit and @PatternWorks for testing that! I created #92 with ideas how to address that to keep this issue on topic.

[shaddow501]

Hi how did you mange to invoke the downgrade since I contact them and they do not agree to downgrade without specific reason.
So how did you manage to work with the awful company? What did you tell them?

[dltccf]

I have been trying for about two weeks to get them to downgrade. The last message I got from them was from 'the technical team' which said that they were trying and had submitted at request to reopen port 8055 and to please be patient. I had Wireshark running when I upgraded from 3.0.2.21 to 3.0.2.25 that showed it responding to queries and then rejecting them as soon as the upgrade happened. They had asked for me to send a video of the problem so I sent them the pcap file. It must have convinced whoever looked at it, but very slow getting anything actually done.

…

On Thu, Jan 18, 2024, 5:09 AM shaddow501 ***@***.***> wrote: Hi how did you mange to invoke the downgrade since I contact them and they do not agree to downgrade without specific reason. So how did you manage to work with the awful company? What did you tell them? — Reply to this email directly, view it on GitHub <#69 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7JYLZ4AKLIJXKYCPIXDDQ3YPDYFDAVCNFSM6AAAAAAU3NOLOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJYGE3TINBVHE> . You are receiving this because you commented.Message ID: ***@***.***>

[shaddow501]

I have been trying for about two weeks to get them to downgrade. The last message I got from them was from 'the technical team' which said that they were trying and had submitted at request to reopen port 8055 and to please be patient. I had Wireshark running when I upgraded from 3.0.2.21 to 3.0.2.25 that showed it responding to queries and then rejecting them as soon as the upgrade happened. They had asked for me to send a video of the problem so I sent them the pcap file. It must have convinced whoever looked at it, but very slow getting anything actually done.

They actually telling you: It is nice that you decide throw your money on our products and keep us our jobs , we will do the best not to help and support if it is not in our mainline.

"please be patient" means to FUCK OFF, you are not in our interest.
But if you would like to buy from us something else we will be more than happy to assist you...

Anyway I have contacted the local dealer, he said to bring the system to them and they will try to downgrade it locally, but there is no guarantee that they will have success.