Request: Delta 3 Plus and new version 3 devices #465
Comments
|
Hi, KR |
|
If you need an interface in HA as an intermediate solution you could take advantage of another smart home called ioBroker and its EF adapter https://github.com/foxthefox/ioBroker.ecoflow-mqtt, which has a gateway implementation to HA and integrates EF devices perfectly. The only downside is the needed installation of ioBroker in your environment. |
|
Ecoflow API does not appear to supply any data over either HTTP API or MQTT for the River 3, and as you can see in the iobroker adapter they also have no actual data configured for it. The River 3 Plus does seem to have some data available over MQTT according to the adapter, but I dont own one so cannot check if they also have data available over HTTP. Bit sad that the R3 has been out for quite a few months without any API support at all (ig at least the R3Plus has data even if its undocumented in their developer portal...) |
|
The River3 most likely is sending data. Since I did not have any sample data from somebody owning the R3 it is void in the iobroker adapter. There is an option to gather the data of unknwon devices and if I get them posted I can start with implementation of the R3. So it is only a matter of finding an owner who is willing to use the iobroker adapter and to provide some sample data. Ps. the communication is via the MQTT Server, which is also used by the APP |
|
I have tested connecting to MQTT but I get no data from the River 3, while I do get data from other ecoflow devices like a River 2 Pro and Glacier. (Even accessing the App interface while the client is connected to MQTT, which always seems to force some data to show up) Tested using https://github.com/Mark-Hicks/ecoflow-api-examples/blob/main/ef_api_mqtt_example.py Do you have another quick way to test for this? |
|
I am not so familiar with python, but it seems something missing especially the 5 topics I am using. Relatively quick is the usage of node-red and follow this gist To be mentioned (it comes later in the comments), you should set the message type to hex or base64, otherwise it tries on JSON and strings, which is not suitable for further evaluation. Or by using this iobroker adapter. |
|
Using that node-red setup, it confirms what I've seen before using other tools, it just outputs some encoded/binary data on some endpoints, and nothing on others (notice no output on Debug2 I have redacted some identifiable information like my node-red domain, part of the device serial number and my user id Note that no data shows up on the topics unless I open the mobile app while connected. Here are the base64 encoded outputs for each debug node: Debug3: Debug4: Debug5: Debug6: EDIT: I see, they are protobuf encoding the data for newer devices, that suuuuuuucks >.> |
|
Very cool, we see data incomming! |
|
I checked it a bit, it converts as follows: debug3 (the usual get command for data request) debug5 (set command, something from the APP for time sync) debug6(set_reply, the ACK to the command) debug4 (the get_reply, unfortunately truncated and one unknown message inside, but one is complete): As far as I can see it, the device is communicating with useful information. If you want to give it another try, then please expand the message size of mqtt of debug4 (and stay at base64) and post the output. Hopefully not truncated then. |
|
Thanks for the help, here is the full output of that endpoint without the debug max length truncation: |
|
Perfect! Now there is the missing other telegram With both telegrams I might start the addition in iobroker. |
|
I don't know anything about ioBroker, but I've now installed it on a Raspberry Pi and got it running. I've also integrated the Ecoflow instance.< 8000 /p> What do I need to do now to access the Delta3 data? |
|
Very good if you have the setup made successfully. You need to go to instances and there on the config page of the adapter wrench symbol. Edit |
|
I'm using the Delta 3 (without Plus). I've now added it to the "not yet supported devices" list and also checked that "debug" is enabled. But I'm not receiving any data – or do I need to do something else? If I know how to get sample data, I'd be happy to provide it 😀. To see if this even works, I also attached my "River 2." All relevant data came up immediately. So, at least the installation is running smoothly. |
|
I have created foxthefox/ioBroker.ecoflow-mqtt#255 to deal with River 3 devices, there are already issues there for the Delta 3 series as well so that seems like a better place to discuss this than this repo |
|
@AlphaZuluNRW |
|
so just to confirm, its not possible to use this integration with Delta 3 Plus yet and the above convo is to do with a different integration? |
|
Correct, gen 3 devices are not yet in this integration. It is only through the iobroker adapter and its gateway to HA. |
|
I’ve successfully added my Delta 3 Plus with this integration that uses Bluetooth connection which works well for me. |
|
I'm now using the integration via ioBroker because I had a Raspberry Pi lying around anyway. After a few initial hiccups, it now works flawlessly and, most importantly, with very little delay. |
Is it at all possible to work on getting the Delta 3 Plus added into this integration? I know there is an integration to use MQTT through the cloud.
https://gist.github.com/nalditopr/493af377e9928b88c2639a9e1607f127
This needs some work by someone that is way smarter than me, it works but not very well.
The text was updated successfully, but these errors were encountered: