-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration broken FW 1.6.2.43 #53
Comments
I have Delta MAX with FW 1.6.2.43 and everything is working to me. |
Thanks for feedback. I tried your workflow but without any success. Anything else I can try? |
Can you try to check if port 8055 is opened on DELTA Max? E.g. by running following command (xx.xx.xx.xx is IP address of your DELTA Max) in some linux terminal |
Sure, here we go.
|
I did a fresh setup with linking my Delta MAX to the App again. Therefore I unlinked my existing Delta MAX and did the Setup again. During the Setup I did a Port-Scan and realized shortly after adding my WiFi Credentials the Port 8055 is getting closed. |
related #58 |
I just opened a request at EcoFlow Zendesk and described my problem. I asked if the Port 8055 will be open again on newer Firmware Version or if it would be possible to do a Firmware Downgrade. I will keep you posted. |
I opened request also (two days ago) but it seems EcoFlow is focusing only on use of their official API (https://api.ecoflow.com/iot-service/open/api/device/queryDeviceQuota/...). |
Hi, not sure if it works for your delta, but did you try the commands describe in v1ckxy/ecoflow-withoutflow#2 ? Especially the command curl -X POST -d '{"action":"getTCPServer"}' http://ip-address of your device could be interesting, maybe they change the port? |
Hello, I have DELTA Pro, DELTA Max and River RIVER Pro. All units are on latest FW, But only DELTA Pro has all TCP ports closed. |
That is strange as the unit must have a port open to communicate with the external server. Have you made a deep scan with nmap? nmap -Pn -sS -sV --version-all --reason -v -A -O --osscan-guess -p0-65535 IP Address |
I will try full scan. So far I tried only to 0-30000 |
I try a full scan -p0-65535 on Delta2, all are closed. |
Here is my result ... DELTA Max FW 1.6.2.43: RIVER Pro FW 1.2.5.23: DELTA Pro FW 1.0.0.96: |
That is interesting. So what we need is a capture between the device and the server from Ecoflow. But do not place a capture here, as it will contain a lot of private information. You should open the capture with wireshark and look at the traffic between your device and the ecoflow server by filtering the stream with ip.addr == IP Address of your device Without a Fritzbox it is depending on your router if a capture feature is build in or not |
I think that Ecoflow unit is connecting to Ecoflow cloud and act as a sender of data. Capture of this communication will not help because Ecoflow unit has probably hardcoded connection to Ecoflow cloud in FW (probably by some URL). If no port is open then it cannot serve as local server which provides some data. |
Hi I received an answer to my open support ticket.
What should I say, I'm really disappointed. |
That's a joke, as many private data will go to their cloud. Even your wireless password might be send. |
That is the mobile app, but does the device now really connect using MQTT to the ecoflow server? Would be great if so. |
Yes it probably connects via MQTT, using the log from the android device I found out the name and password to ecoflow MQTT server. And using the MQTTX app I was able to read the information through the MQTT from the ecoflow server. The information which I got is shown here But I am unable to get the data into home assistant(I am new to MQTT). |
Fist of all many thanks for this beautiful integraiton.
Sadly I updated my Firmware Version to
1.6.2.43
on my Delta MAX and now the Integration with Home-Assistant is broken. I tried to remove and re-add my Delta MAX in Home-Assistant with no success.Do you have some advises or tests I can to to provide further logs?
Hopefully EcoFlow hasn't disabled there local API. Anyone else facing similar problems?
Cheers e-bits
The text was updated successfully, but these errors were encountered: