Do not perform a firmware update #58

vwt12eh8 · 2022-09-22T01:11:48Z

vwt12eh8
Sep 22, 2022
Maintainer

We have received reports that local APIs are no longer available after updating to the latest firmware.

If the local API is not available, this integration will not be usable, so please hold off on firmware updates until a solution is found.

Ecoflow also have an MQTT server that you can connect to, at least I assume that this version update hasn't disabled access to that as well. I think all the information that this addon includes is also available through that services, can get a bit more information over here: v1ckxy/ecoflow-withoutflow#1 (comment)

Edit: It is still there and running.

1 reply

Ne0-Hack3r Oct 10, 2022

Yes. I'm aware of at least one other writing scripts to use the cloud based MQTT service... That could be a "solution" for this integration but it means dependence on the internet and cloud service and most likely less "real time" data... I'm hoping Ecoflow can be convinced to re-open the ports or we can find a way to trick the units into opening the port. I for one would really like to keep local connection and real-time data. I've gotten so much use out of this integration already and there is still so much more I can do... It's one thing for Ecoflow to ignore requests for a proper API and decide not to focus on providing integration outside their own ecosystem but to just arbitrarily close the port after so much effort has been put into private integration is nuts!

mat-berlin · 2022-10-01T11:50:34Z

mat-berlin
Oct 1, 2022

what a pitty, i read this just now.
I can not connect to my ecoflow delta mini. I did firmware update right after installation :-( (before trying to connect HA to it) firmware version is 0.1.0.0.
any news on this issue?

0 replies

Ne0-Hack3r · 2022-10-01T21:18:47Z

Ne0-Hack3r
Oct 1, 2022

We have received reports that local APIs are no longer available after updating to the latest firmware.

If the local API is not available, this integration will not be usable, so please hold off on firmware updates until a solution is found.

Related

#53 #54 #57

I have 1.0.0.96 firmware on both my DPs and integration is still working... I'm on HA OS 8.4 and Core 2022.8.6 with version 2.2.2 of the EF integration currently... So while I have (and have had) the most recent firmware for Delta Pro installed for quite some time I do not have the most current versions of HA and the EF integration...

There is a newer firmware for DP on the horizon but it has not been released yet (expected soon). So is this just a problem with the most recent firmware on the Delta Max??? I do not have a DM so cannot test...

2 replies

sidonsoft Oct 4, 2022

as per my post, the local api was closed off in the wifi module firmware update on the delta max it was 0.4.8 -> 3.0.1.11

I contacted EcoFlow in regards to a roll back of the firmware but they replied with my private api key instead.

mattwells Oct 4, 2022

Is that the same one you would use to make a get request to this fairly useless endpoint with your serial number and API key? https://api.ecoflow.com/iot-service/open/api/device/queryDeviceQuota?sn=XXXXXXXXXXXXXXX

Jenda987 · 2022-10-11T08:33:34Z

Jenda987
Oct 11, 2022

I got following response from EcoFlow support ...
Please note that port 8055 has been locked, and the function will not be able to open again for now. Sorry for the inconvenience.
Please check the API access for your devices. https://api.ecoflow.com/iot-service/open/api/device/queryDeviceQuota?sn=XXXXXXXXXXXXXXX

0 replies

vwt12eh8 · 2022-10-14T23:33:19Z

vwt12eh8
Oct 14, 2022
Maintainer Author

It appears that EcoFlow has intentionally closed the TCP port.
The only way to continue this integration in the future may be to use Bluetooth or Cloud MQTT.
Some functionality degradation is inevitable for that.

If local completion is important to you, Bluetooth is the only choice.
Bluetooth support has recently been enhanced in the Home Assistant Core, so this is a useful enough option.
But it requires hardware for Bluetooth communication.

If possible, I would like to allow users to choose one of these for this integration in the future.
But I've been busy with other things lately, so this may take some time.

5 replies

Ne0-Hack3r Oct 16, 2022

What might be required for BT integration? A Raspberry Pi Zero W perhaps?

Do you have any path of communication to EF developers or R&D? Any insight as to why they closed the port or any chance that a petition from enthusiasts like us might persuade them to re-open it?

vwt12eh8 Oct 16, 2022
Maintainer Author

Generally, a USB dongle will allow you to use Bluetooth.
If the device is far from the server, ESPHome can be used.

If you are running hassio-core on RaspberryPi, there is nothing to prepare.

lwsrbrts Oct 21, 2022

I like the idea of using Bluetooth as I suspect most of the Ecoflow units also support Bluetooth. For me personally, I will have to use a ESPHome Bluetooth proxy as my Home Assistant instance runs on Hyper-V and I can't add USB devices for that reason.

I just had a quick watch of this video (https://www.youtube.com/watch?v=5TfdWT6EMPo) and one of the things it mentions is that a Bluetooth proxy connection is passive, not active, which would mean that you can't send commands to the Bluetooth device - presumably this means I would be prevented from controlling the AC or DC output. Given that there's only 2 controls, I don't think that's a huge loss!

Bluetooth gets my vote and I'd be happy to assist with any testing.

A side-benefit of using Bluetooth would probably be that the Smart Home Panel could (maybe) be supported in the future - but this would definitely need an active connection in order to control its relays etc.

Ne0-Hack3r Oct 23, 2022

I like the idea of using Bluetooth as I suspect most of the Ecoflow units also support Bluetooth. For me personally, I will have to use a ESPHome Bluetooth proxy as my Home Assistant instance runs on Hyper-V and I can't add USB devices for that reason.

I just had a quick watch of this video (https://www.youtube.com/watch?v=5TfdWT6EMPo) and one of the things it mentions is that a Bluetooth proxy connection is passive, not active, which would mean that you can't send commands to the Bluetooth device - presumably this means I would be prevented from controlling the AC or DC output. Given that there's only 2 controls, I don't think that's a huge loss!

Bluetooth gets my vote and I'd be happy to assist with any testing.

A side-benefit of using Bluetooth would probably be that the Smart Home Panel could (maybe) be supported in the future - but this would definitely need an active connection in order to control its relays etc.

I'm currently running HA on Hyper-V as well... but it sounds like I might want to re-deploy on an RP with BT and locate that near my SHP and DPs if this integration goes the BT route... There are a lot of controls on DP that can be set using automation (I have one now that can turn on DC output to send 12V to a relay to stop DC input from an external SMPS or turn off the DP output to start DC input from the SMPS).

I like the idea of keeping that data local as long as BT would have the full functionality that we currently have over WiFi... I might even abandon the app in favor of a secure connection to my HA in that case and just not put EF devices on WiFi at all...

Leatherface75 Nov 1, 2022

It appears that EcoFlow has intentionally closed the TCP port. The only way to continue this integration in the future may be to use Bluetooth or Cloud MQTT. Some functionality degradation is inevitable for that.

If local completion is important to you, Bluetooth is the only choice. Bluetooth support has recently been enhanced in the Home Assistant Core, so this is a useful enough option. But it requires hardware for Bluetooth communication.

If possible, I would like to allow users to choose one of these for this integration in the future. But I've been busy with other things lately, so this may take some time.

Problem is that atleast old River models don't have bluetooth.
I think it's only Delta Pro models and the new River 2 and Delta 2 that supports it.

skpow55 · 2022-10-21T14:31:09Z

skpow55
Oct 21, 2022

Bluetooth is a good option. I would also like to see EF provide a browser/web page interface to their server. I inquired about this several weeks ago and they said they do not currently have one. It may help if more EF product owners also suggest the same to them to build up demand for providing one. It's common for other solar storage/power equipment vendors to provide browser/web page interfaces to their products.

…

On 10/21/2022 7:22 AM, Lewis Roberts wrote: I like the idea of using Bluetooth as I suspect most of the Ecoflow units also support Bluetooth. For me personally, I will have to use a ESPHone Bluetooth proxy as my Home Assistant instance runs on Hyper-V and I can't add USB devices for that reason. I just had a quick watch of this video (https://www.youtube.com/watch?v=5TfdWT6EMPo) and one of the things it mentions is that a Bluetooth proxy connection is passive, not active, which would mean that you can't send commands to the Bluetooth device - presumably this means I would be prevented from controlling the AC or DC output. Given that there's only 2 controls, I don't think that's a huge loss! Bluetooth gets my vote and I'd be happy to assist with any testing. A side-benefit of using Bluetooth would probably be that the Smart Home Panel could (maybe) be supported in the future - but this would definitely need an active connection in order to control its relays etc. — Reply to this email directly, view it on GitHub <#58 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AS75SI2RZARUXT5ZGY4E2ULWEKDHLANCNFSM6AAAAAAQSSTDPA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

0 replies

lwsrbrts · 2022-10-21T20:14:19Z

lwsrbrts
Oct 21, 2022

Quick update for everyone ruing the day they decided to update their firmware. I've spent some time today working out how to use Ecoflow's own MQTT server to get access to your battery data in Home Assistant.

Yes, its cloud-based and there's work for you to do to configure it but it's an option for those of you technically skilled enough. You do need to have MQTT setup already.

All posted here:

v1ckxy/ecoflow-withoutflow#1 (comment)

0 replies

rickhuizinga · 2022-11-11T03:03:39Z

rickhuizinga
Nov 11, 2022

Has anyone tried the newly released 1.0.1.18 firmware for the Delta Pro?

9 replies

Ne0-Hack3r Nov 14, 2022

I can confirm the same experience when the Ecoflow servers were offline this week for about 22 hours. When the Delta Pro can't talk to their server, it shuts down the interface that this Home Assistant extension uses to communicate with the Delta Pro.

Yep. And that outage, by the way, was EF locking down the cloud MQTT server. Can still connect to it using login credentials for the app and subscribe to MQTT for your device (assuming you know SN/AppKey) but can no longer list keys... these are pretty well known for most of the pre-existing devices but won't know if they add/change things moving forward and makes adding new devices very difficult...

lwsrbrts Nov 15, 2022

Having looked through the Android APK using APKLab add-on for Visual Studio Code to (somewhat) decompile it, there's a file listing the MQTT "contracts" in whatever "Smali Bytecode" is...

I found it in this file
smali_classes2\com\ecoflow\common\http\mqtt\MqttContracts.smali

.field public static ACTION_CONNECT_FAILURE:I = 0x11
.field public static ACTION_CONNECT_SUCCESS:I = 0x10
.field public static ACTION_PUBLISH:I = 0x13
.field public static ACTION_SUBSCRIBE:I = 0x12
.field public static final CONNECTION_TIMEOUT:I = 0x1e
.field public static final KEEP_ALIVE_INTERVAL:I = 0x1e
.field public static final MQTT_PUBLISH_DEVICE_STATUS:Ljava/lang/String; = "/app/%s/%s/thing/property/get"
.field public static final MQTT_PUBLISH_SET:Ljava/lang/String; = "/app/%s/%s/thing/property/set"
.field public static final MQTT_SUBSCRIBE_DEVICE_STATUS:Ljava/lang/String; = "/app/%s/%s/thing/property/get_reply"
.field public static final MQTT_SUBSCRIBE_SET:Ljava/lang/String; = "/app/%s/%s/thing/property/set_reply"
.field public static final MQTT_TOPIC_BASE:Ljava/lang/String; = "/app/%s/%s/thing/property/"
.field public static final MQTT_TOPIC_PROPERTY:Ljava/lang/String; = "/app/device/property/%s"
.field public static final PORT:Ljava/lang/String; = "8883"
.field public static final SERVER:Ljava/lang/String; = "ssl://10.10.11.107"
.field public static final SUBSCRIBE_MODULE_INFO:Ljava/lang/String; = "/ota/module/inform/%s/%s"
.field public static final SUBSCRIBE_ONLINE_STATUS:Ljava/lang/String; = "/app/device/status/%s"
.field public static final SUBSCRIBE_UPGRADE_STATUS:Ljava/lang/String; = "/app/device/progress/%s"

I imagine this file would have updates with any new topics that they may define. Where there's a %s/%s that format suggests the use of the User ID and Device Serial, in that order for the topic.

Ne0-Hack3r Nov 20, 2022

I don't think subscribing to the topics is the issue... it's determining the names required to change settings. The BEEP on/of setting for example does not use the same name on every device...

lwsrbrts Nov 20, 2022

Issue? The messages published to the set topic by the app when a setting is changed are already recordable/accessible and can be easily replayed, either directly on their MQTT server or a bridge connection set up from your own broker to allow you to use HA to publish the MQTT message.

It's a given that each device type might have different params.id values, even for what could be described as the same setting, but there's nothing stopping you from connecting the the Ecoflow MQTT server, performing the action in the app, recording the values it generates on the set topic for your device and then replaying the same message with appropriate values you want to apply instead.

I've already described how to do this on another GitHub repo which I've mentioned in other messages.

Ne0-Hack3r Nov 24, 2022

I'm likely just missing something as I'm new to playing with MQTT... I've recently gotten MQTT Explorer setup and subscribed to the topics for my devices and am trying to make sense of how to capture a change and "replay" it. Once I understand how to do that manually in explorer I think doing it programmatically will make more sense...

GeorgWolter · 2023-02-03T17:16:30Z

GeorgWolter
Feb 3, 2023

Info on DELTA Pro:
There is a new FW 3.0.2.21 (WLAN) and according to EcoFlow's support team Port 8055 is open.
Tested this integration with my DELTA Pro and it works again 🙏😁

11 replies

GCustom Feb 3, 2023

Just cancelled the spinning to get the stats:

Home Assistant 2023.1.7 Docker on Synology
Frontend 20230110.0 - latest
OS Synology 7.1.1-42962 Update 2
HACS 1.30.1
Frontend 20220906112053
This integration 2.2.3

I'll update the container if there's an available update and post back here if that makes a difference as I see @GeorgWolter has a newer HA than me

GCustom Feb 4, 2023

New container contained 2923.2.1 too, after some time the spinning times out and gives unknown error

GeorgWolter Feb 4, 2023

Does your DS support the Virtual Machine Manager (VMM)?
Then you could give that a try in installing a HA test instance.

GCustom Feb 4, 2023

It does I've got the VMM running on another unit so it'll be a clean installation and removal if it doesn't work. I'll try that tomorrow when I'm more fresh as I have only glanced at the instructions for a full install years ago when I saw the docker containers I closed the tab on those instructions :)

Prior to upgrading the firmware it was working this morning

GeorgWolter Feb 4, 2023

My two hardware-platforms are a Raspi4 4MB (USB SSD) and a DS218+ (VM).
HA Yellow should arrive in the next week. Hoping to get the Compute Module in the same week 😁

Leatherface75 · 2023-02-04T02:15:24Z

Leatherface75
Feb 4, 2023

Too bad i don't see that update for River Max yet.
There is another addon using mqtt now but only in initial stages yet.
You guys could help that guy with diagnosis information.

https://github.com/tolwi/hassio-ecoflow-cloud

1 reply

GeorgWolter Feb 4, 2023

Interesting, I will look into that!
During that long period where hassio-ecoflow could not work I have used the EcoFlow cloud.
But that provides only 3 entities (Power in, Power out, SoC). Did the HA integration with NodeRed.

DarrylGNOLA · 2023-02-06T05:15:56Z

DarrylGNOLA
Feb 6, 2023

FYI. There is a new wifi firmware out for Delta Pro's that is reopening the port for this integration to work. Check out other discussions.

0 replies

icemandk · 2023-02-19T15:58:12Z

icemandk
Feb 19, 2023

i have delta pro i have no access to 3.0.2.21 still saying 3.0.1.11 is up to date

3 replies

Ne0-Hack3r Feb 24, 2023

i have delta pro i have no access to 3.0.2.21 still saying 3.0.1.11 is up to date

And port is closed with 3.0.1.11, correct?

There is more than one WiFi board in various Delta Pro units so there may not be a new one, yet, for the WiFi in your unit...

icemandk Feb 24, 2023

yes and im done with ecoflow selling everyting changing to victron, i don trust ecoflow anymore after secret closing port

DarrylGNOLA Feb 25, 2023

Yes. But it seems you need to request the Wifi update from support if it is not showing. See @Roughman007 comment below.

Ne0-Hack3r · 2023-02-24T09:06:33Z

Ne0-Hack3r
Feb 24, 2023

EcoFlow has started a beta test of API that hooks into cloud server via MQTT and HTTP with a fairly large data set... beta is limited to select SHP+DP users initially... no local API as yet...

2 replies

GCustom Feb 24, 2023

Is it automatic if you have the api and that unit or do you need to request the beta?

Ne0-Hack3r Feb 25, 2023

Is it automatic if you have the api and that unit or do you need to request the beta?

You have to apply to be part of the beta and need to have both SHP and DP at this point... that is my understanding at least... still waiting for access...

Roughman007 · 2023-02-24T14:26:53Z

Roughman007
Feb 24, 2023

i have delta pro i have no access to 3.0.2.21 still saying 3.0.1.11 is up to date

Hi, I wrote to ecoflow support that I want firmware 3.0.2.21 to be able control the unit from HA (I want beta firmware). After 4 days, the update appeared in my ecoflow application.