The port is free again and the integration works.

Hallo,

I tried to add my Delta 2 Max, but the configuration fails with „unknown error“. In the protocol I see:

Logger: frontend.js.latest.202306080
Source: components/system_log/init.py:257
First occurred: 20:55:07 (27 occurrences)
Last logged: 21:22:17

:0:0 Script error.
http://192.168.178.30:8123/hacsfiles/frontend/main-ad130be7.js:217:40880 TypeError: null is not an object (evaluating 'e._themes')

Is this due to Delta 2 Max not (yet?) being supported? If so, is it possible to add support for it, please?

Thanks,
infty

The last comments on #69 (comment) got me thinking. Even when EcoFlow is kind enough to "push" 3.0.2.21 on individual request, it does not give us full offline control.

I guess we need to put more effort into it if we want to have that.

From the changelog we can conclude that most of the work is done by the main firmware. The Wi-Fi firmware only does Bluetooth, Wi-Fi and Internet connectivity. So we can either disable that module somehow and directly speak to the chip with the main firmware on it. The hope would be that the protocol is similar or identical to what is already implemented. Or if the Wi-Fi module is something common like a ESP32, we could even write a Open Source firmware for that. I did a quick check. At least I don’t know/have found ESP32 modules like WROOM with the chip pin layout of the picture below. Finding an ESP32 in the DELTA Pro would have been my hope.

Not sure when I come around to teardown my DELTA Pro again to see what can be done. I wanted to create this issue to keep the other issues focused.

Picture of the Wi-Fi module:
Source: https://youtu.be/lagxSrPeoYg?t=968

Hi all,

Everything was looking great at the version 1.0.1.18 but since the latest firmware for the delta Pro, Nothing is working anymore. I deleted my entities in homeassistant and try to add it again but it look like the Ecoflow API has been changed on their side. The wizard do not even detect Ecoflow Pro IP, nothing happen

Am I the only one with this issue?

At first, many thanks for building this integration. The registration of new devices worked like a charm.

When using the River Max as UPS or mainly as pass-through battery, the following configuration is incorrect:

total input energy : Home Battery Storage -> Energy going in to the battery
total output energy : Home Battery Storage -> Energy coming out of the battery

It would add the input and output (that is equal if the battery is fully loaded) to the Energy Dashboard as Battery Charge (IN) and Battery Usage (OUT). But it does not touched the battery at all.

Request to get besides the totals two dedicated sensors for the battery:

Battery input energy = Only in Charge Mode -> Input minus Output (this is what actually flows into the battery)
Battery output energy = Only in Battery Mode (Input OFF/0) -> Output (this is what actually flows out of the battery)

Trying to add my new station with FW 1.0.1.61, but after add it reports error:

Logger: homeassistant.config_entries
Source: config_entries.py:399
First occurred: 21:13:12 (1 occurrences)
Last logged: 21:13:12

Error setting up entry DELTA Pro 050002 for ecoflow
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 399, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/ecoflow/__init__.py", line 275, in async_setup_entry
    hass.config_entries.async_setup_platforms(entry, _PLATFORMS)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'ConfigEntries' object has no attribute 'async_setup_platforms'

This is not an issue but rather a question:

How exactly does the code fetch the BMS and other data (MMPT and INV)? I cannot find this out by checking the source code. request is only called to get get_serial_main and get_dc_in_current.

Until yesterday everything worked fine.
And suddenly all entities stopped working.
I'm doing an Ecoflow restart every 2 minutes so that I can monitor battery status.
But now, nothing works.

which logs should I sent to you?
tnx!

Can this integration work with the river 2 max as well? I have gotten different answers from ecoflow. One said it was possible and the other said it isn't

Hi, this is not an issue but rather a question:

I have Delta Pro(firmware 0.3.6), has anyone tried updating to the latest(0.4.8) firmware? Will this integration still work for me? Has anyone tried this?

Thanks.

I have the software running, and can see all the power usages in watts,
but seem unable to see the volumes in Wh for my River Pro.
is this function available for this model? can it be added?

Hi,

would it be also possible to integrate the River mini ?

It is recognised already by the integration but the data is not valid.

Thanks

Michael

{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2022.7.6",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.10.5",
"docker": true,
"arch": "aarch64",
"timezone": "Europe/Berlin",
"os_name": "Linux",
"os_version": "5.15.32-v8",
"supervisor": "2022.07.0",
"host_os": "Home Assistant OS 8.2",
"docker_version": "20.10.14",
"chassis": "embedded",
"run_as_root": true
},
"custom_components": {
"ecoflow": {
"version": "2.1",
"requirements": [
"reactivex"
]
},
"weatherflow": {
"version": "1.0.6",
"requirements": [
"pyweatherflowrest==1.0.8"
]
},
"hacs": {
"version": "1.26.2",
"requirements": [
"aiogithubapi>=22.2.4"
]
},
"sonoff": {
"version": "3.1.0",
"requirements": [
"pycryptodome>=3.6.6"
]
},
"meross_lan": {
"version": "2.6.1",
"requirements": []
}
},
"integration_manifest": {
"domain": "ecoflow",
"name": "Ecoflow",
"version": "2.1",
"documentation": "https://github.com/vwt12eh8/hassio-ecoflow",
"issue_tracker": "https://github.com/vwt12eh8/hassio-ecoflow/issues",
"requirements": [
"reactivex"
],
"config_flow": true,
"codeowners": [
"@vwt12eh8"
],
"dhcp": [
{
"hostname": "ecoflow_",
"macaddress": ""
}
],
"iot_class": "local_push",
"is_built_in": false
},
"data": {
"inverter": {},
"dc_in_current_config": 4000
}
}

Thank you for your nice work with this integration!

As mentioned in other issues #57 #54 #53 i have just updated firmware of my Delta Pro EU Version to Firmware 0.1.0.0 and integration isn´t working anymore. Support also informed about this bad decision. I was a bit blind before updating and not looking into the other issues...

I have integrated my Delta Pro to my local network via Wifi. Then no ports are open from 1 - 65535. But when i am in IoT Mode with Wifi of the Delta Pro i have scanned ports again and there was port 80/tcp http and 80555/tcp senomix04 open. Because for updating firmware they maybe need something... ;)

I have added a Raspberry Pi with Wifi to Delta Pro Wifi and via LAN integrated it to my local network something like a bridge. After installing haproxy and adding this to the configuration and restart haproxy, i can use the integration again.

/etc/haproxy/haproxy.cfg

frontend ecoflow
        bind *:8055
        mode tcp
        use_backend ecoflowdeltapro

backend ecoflowdeltapro
        mode tcp
        server deltapro 192.168.4.1:8055 check

With the IP of Raspberry Pi in local Network i can add the Delta Pro again with this nice integration (including changing options). Only issue right now is, i need a running android application to be able getting information. When i close the android app, information stopped and home assistant is telling me entries are not available.

I will investigate this in next days further and keep you informed. Hopefully i can send just a dummy request from raspberry pi to delta pro to update information.

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

I noticed another issue with the AC input sensors' readout in bypass (pass-through) mode on my Delta Pro running hassio-ecoflow 2.2.2):
Once the battery is fully charged, and the unit switches to pass-through mode, the sensor values for AC are "Off" resp. "0 W", although the unit is still plugged on AC and passing on power to the active AC output. The AC output power is correctly displayed, as well as the "Total input" and "Total output".

As a side note: According to the activity log, the AC input was reset at the same time the Charging indicator changed to "Not charging" when the battery was full. The ac_in_power in the debug log looks correct in this case (and is aligned with the ac_out_power)

config_entry-ecoflow-b59e0ccb379fad5eff3c3280bd845a54_2.json.txt

After nearly 4.000 hours of solar production, my DeltaPro broke down. EcoFlow offered to replace it by a refurbished module.
I got a new one and tried to integrate it again with the hassio-ecoflow app. EcoFlow provided the firmware 1…..61 which is not working. They gave me a downgrade to 1.0.1.18.

Unfortunately home assistant does not identify the DeltaPro. I guess, that’s the well known problem of missing contact to the API, but my setting should not have changed, because the app sits on an isolated home assistant - never dated up since working - on a separate raspi, connected via „Remote Home-Assistant“.

My HA setup is:
Home Assistant 2023.2.4
Supervisor 2023.10.1
Operating System 10.5
Frontend 20230202.0 - latest

The DeltaPro App has these settings:
V1.0.1.18 with V3.0.2.21(WLAN)

I ran out of ideas, how to fix it :-)

Hi,

are there any plans/timeline to support Ecoflow Delta 2?

Is there anything I can help with (I have one).

Thank you :)

Got it to connect for the briefest moment during iot reset process, may need to get the private API by sending serial number from EcoFlow for those who have updated or ask for a rollback

Hi - Great work on developing this add-on. Works really well.
I have 2 x Ecoflow River's and stats are coming through nice.

I do have a question though on the main status entity.

Both of my Ecoflow's are showing as "Problem" but there is nothing on the units themselves or the official Ecoflow app to indicate any problem.

Could there be a an issue with this entity?

Thank

Is it possible to support the smart home panel? If there is anything I could do to help please let me know.

Would be great to see this device working with Home assistant in the future

Hi, I just updated my Delta Pro to firmware 1.0.0.96. and now the Integration with Home Assistant is not working. I tried to remove and re-add my Delta Pro in Home Assistant but it still doesn't work. Anyone else facing similar problems?

Thanks.

We had the well know problem with this integration, broken by EcoFlow etc. You all know, what the case was.

Together with a lot of other users, we had put massive pressure on EcoFlow, because we are planning commercial usage of DeltaPro and bought more than one unit ... etc.

Our concern - absolutely strange:

• We have the lastest versions of all HA-components, taking all the updates.
• EcoFlow-firmware is newest release with port 8055 working
• We downloaded the lastest version of hassio-ecoflow alpha-3 from HACS via the shop
• The integration shows up after restart and we enter the correct IP. No question: EcoFlow is online, FING shows it, ping is working
• The EcoFlow-integration tile shows up without any entities. It looks like it does not find the DeltaPro.
• EcoFlow is working on the Wifi-based App on iPhone
• We veryfied, that port 8055 is sending data ...

Sure - it has to be a very, very simple a stupid problem.
But my colleagues and I are standing in front of the forest and don't see this one tree ...

Any idea? Call us "fools" ... but please drop a hint, if you have any idea.

Just got my brand new EcoFlow Delta 2. It has firmware V1.0.0.1 and V1.0.3.18 (Wi-Fi) and the app tells me this is the latest firmware.

It connects fine via wifi/app.

Integration does unfortunately not want to connect on the correct IP of the EcoFlow Delta 2.

I have read all the other issues & the home assistant forum and I see several potential issues ranging from API closure to firmware updates etc.

Could you advice on best next steps/trouble shooting?

Hi ! Auto fan speed in my case (I using 3x River) is completely fail. Fan working only on „1” speed, but If I change auto fan speed to disabled, fan speed is „3”. Hot and quiet or cool and loud - bravo for china small devs. My question is - if so ecoflow did stupid alghoritm related to automatically fan control… where is „2” speed ? Medium ?

we can turn it on manually via local API ?

Logger: homeassistant.config_entries
Source: config_entries.py:2077
First occurred: 12:25:23 (1 occurrences)
Last logged: 12:25:23

Error occurred loading flow for integration ecoflow: cannot import name 'Observable' from 'reactivex' (/usr/local/lib/python3.11/site-packages/reactivex/init.py)

Total Charge Level & Car Input unavailable with River Max

Log says

Logger: custom_components.ecoflow.ecoflow.rxtcp
Source: components/number/init.py:175
Integration: Ecoflow (documentation, issues)
First occurred: 16:15:49 (1 occurrences)
Last logged: 16:15:49

'MaxLevelEntity' object has no attribute '_attr_value'
Traceback (most recent call last):
File "/config/custom_components/ecoflow/ecoflow/rxtcp.py", line 73, in __loop
self.received.on_next(data)
File "/usr/local/lib/python3.9/site-packages/reactivex/subject/subject.py", line 59, in on_next
super().on_next(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/observer/observer.py", line 39, in on_next
self._on_next_core(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/subject/subject.py", line 66, in _on_next_core
observer.on_next(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/observer/autodetachobserver.py", line 28, in on_next
self._on_next(value)
File "/config/custom_components/ecoflow/ecoflow/receive.py", line 42, in next
sub.on_next(x[:18 + size])
File "/usr/local/lib/python3.9/site-packages/reactivex/observer/autodetachobserver.py", line 28, in on_next
self._on_next(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/operators/_map.py", line 47, in on_next
obv.on_next(result)
File "/usr/local/lib/python3.9/site-packages/reactivex/observer/autodetachobserver.py", line 28, in on_next
self._on_next(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/subject/subject.py", line 59, in on_next
super().on_next(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/observer/observer.py", line 39, in on_next
self._on_next_core(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/subject/subject.py", line 66, in _on_next_core
observer.on_next(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/observer/autodetachobserver.py", line 28, in on_next
self._on_next(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/observer/autodetachobserver.py", line 28, in on_next
self._on_next(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/observer/autodetachobserver.py", line 28, in on_next
self._on_next(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/operators/_filter.py", line 38, in on_next
observer.on_next(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/observer/autodetachobserver.py", line 28, in on_next
self._on_next(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/operators/_map.py", line 47, in on_next
obv.on_next(result)
File "/usr/local/lib/python3.9/site-packages/reactivex/observer/autodetachobserver.py", line 28, in on_next
self._on_next(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/subject/subject.py", line 59, in on_next
super().on_next(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/observer/observer.py", line 39, in on_next
self._on_next_core(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/subject/replaysubject.py", line 106, in _on_next_core
cast(ScheduledObserver[_T], observer).ensure_active()
File "/usr/local/lib/python3.9/site-packages/reactivex/observer/scheduledobserver.py", line 57, in ensure_active
self.disposable.disposable = self.scheduler.schedule(self.run)
File "/usr/local/lib/python3.9/site-packages/reactivex/scheduler/trampolinescheduler.py", line 49, in schedule
return self.schedule_absolute(self.now, action, state=state)
File "/usr/local/lib/python3.9/site-packages/reactivex/scheduler/trampolinescheduler.py", line 95, in schedule_absolute
self.get_trampoline().run(item)
File "/usr/local/lib/python3.9/site-packages/reactivex/scheduler/trampoline.py", line 30, in run
self._run()
File "/usr/local/lib/python3.9/site-packages/reactivex/scheduler/trampoline.py", line 51, in _run
item.invoke()
File "/usr/local/lib/python3.9/site-packages/reactivex/scheduler/scheduleditem.py", line 27, in invoke
ret = self.scheduler.invoke_action(self.action, state=self.state)
File "/usr/local/lib/python3.9/site-packages/reactivex/scheduler/scheduler.py", line 105, in invoke_action
ret = action(self, state)
File "/usr/local/lib/python3.9/site-packages/reactivex/observer/scheduledobserver.py", line 70, in run
work()
File "/usr/local/lib/python3.9/site-packages/reactivex/observer/scheduledobserver.py", line 32, in action
self.observer.on_next(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/observer/autodetachobserver.py", line 28, in on_next
self._on_next(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/observer/autodetachobserver.py", line 28, in on_next
self._on_next(value)
File "/usr/local/lib/python3.9/site-packages/reactivex/observer/autodetachobserver.py", line 28, in on_next
self._on_next(value)
File "/config/custom_components/ecoflow/init.py", line 244, in __updated
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 533, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 571, in _async_write_ha_state
state = self._stringify_state(available)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 539, in _stringify_state
if (state := self.state) is None:
File "/usr/src/homeassistant/homeassistant/components/number/init.py", line 170, in state
return self.value
File "/usr/src/homeassistant/homeassistant/components/number/init.py", line 175, in value
return self._attr_value
AttributeError: 'MaxLevelEntity' object has no attribute '_attr_value'

I got the following error in the latest Home Assistant Release:

Error setting up entry for ecoflow

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/config/custom_components/ecoflow/__init__.py", line 429, in async_setup_entry
    hass.config_entries.async_setup_platforms(entry, _PLATFORMS)
AttributeError: 'ConfigEntries' object has no attribute 'async_setup_platforms'

It seems like it can be fixed by changing the line from

hass.config_entries.async_setup_platforms(entry, _PLATFORMS)

to

await hass.config_entries.async_forward_entry_setups(entry, _PLATFORMS)

I'm trying to add integration for my Ecoflow River Pro, but it's run forever on IP step.

Home Assistant 2022.11.5
HACS 1.28.4
Ecoflow River Pro Firmware V1.2.5.27/V3.0.1.11(wi-fi)

Right now the app wont open on any of my devices, and it would be extremely convenient for control via home assistant.

First of all - Thank you!

Second - Works flawlessly with a Delta Max so feel free to add a check mark next to that as working:

Hi - I am using the latest version 2.2.3 and still seeing false alerts with the input entity and the trigger for input not powered. See the screenshot.

This device is on bypass and I know input power was not lost so not sure why I am seeing these? Any ideas?

Thanks

Hi! First, thank you. This integration is exactly what I've wanted for my Delta Pro since I got hold of it. Fantastic piece of work and - if there's a method of donation - let me know how I can say thanks. I'm sure you do this for the challenge but it's always nice if someone can show their appreciation for your work and I am happy to do so.

On to the issue. Not a big one, but for the Delta Pro, at least on my unit (UK unit with 240V output x 4), the maximum charge rate configurable while in Custom mode is 2900W, settable in the app, however the slider for the integration only goes to 1500W.

If I set the value in the app to 2900W, it's accepted and seems to be represented just fine in the entity, but its slider is obviously maxed out.

Screenshot from HA included below.

Not sure if it's of interest also but I have 2 extra batteries on my Delta Pro unit and by all accounts everything looks like it's reporting fine but if you want me to specifically test or provide something, happy to do so.

Thanks again!

I am fairly sure that this is a me issue as I have only just installed Home Assistant for the first time but when I click the "My Add Integration" button at the bottom of the readme I get this error when I click through to my Home Assistant instance:

This integration does not support configuration via the UI. If you followed this link from the Home Assistant website, make sure you run the latest version of Home Assistant.

Please could you advise? HA noob /

Home Assistant 2022.7.4
Supervisor 2022.07.0
Operating System 8.2
Frontend 20220707.0 - latest

It looks like DELTA Pro extra battery status is changed each 6 seconds to unavailable and then in a half second (it's very quick) back to normal status.
Normal status

Unavailable status

Log

Everything else looks normal.
Remark - if firmware on extra battery wasn't updated then status was shown as 'Problem'. But maybe it's correct status.

Hello,

First of all, thank you for this integration, sounds promising !
I've created a topic about EcoFlow products 6 months ago or so on HA Forums and somehow, I didn't know about your work until someone else mentioned it.

So, I've naturally tried it by adding the repo to HACS, rebooted and then installing it through integration but I've got an error message directly:

I guess this is because you tested it on River products but then I saw the other ongoing issue with someone going further with his Delta mini, so I wonder if it's me or something else :-).
I've fixed the IP of the Dela MAX from my DHCP server, so I'm pretty sure aboiut its IP.

Any idea?

I'm beginner to HA but I'd happy to help you in any way I can (and I'm sure other from the forum as well).

Traceback (most recent call last):
File "/config/custom_components/ecoflow/ecoflow/rxtcp.py", line 71, in __loop
data = await self.__rx.read(1024)
File "/usr/local/lib/python3.10/asyncio/streams.py", line 669, in read
await self._wait_for_data('read')
File "/usr/local/lib/python3.10/asyncio/streams.py", line 502, in _wait_for_data
await self._waiter
File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 854, in _read_ready__data_received
data = self._sock.recv(self.max_size)
ConnectionResetError: [Errno 104] Connection reset by peer

this is the error i get in homeassistant logs.

This is not an issue but rather a request:

Hi, would it be possible to add a "Discharge/Charge Level" function like in the app? To set the battery limit.

Thanks.

Logger: homeassistant.helpers.frame
Source: helpers/frame.py:77
First occurred: 14:20:49 (1 occurrences)
Last logged: 14:20:49

Detected integration that called async_setup_platforms instead of awaiting async_forward_entry_setups; this will fail in version 2023.3. Please report issue to the custom integration author for ecoflow using this method at custom_components/ecoflow/init.py, line 429: hass.config_entries.async_setup_platforms(entry, _PLATFORMS)

Hi , i tried to get data from my Delta Mini using your great software.
The set up seams to work and home assistant detects your integration and I could add my device into ha.
But it looks like that no data are received from my device.
IP-Address is OK, my phone app shows all data.

Any idea how to find why it is not working?

Thanks and best regards
Frank

Hello!

My setup is as follows:
Delta PRO with 1240W solar panels
Powerstream connected via extra battery port to Delta Pro with also 620W solar panels

When I look at the data in HA it seams that total output of the Delta PRO isn't adding the output which is from the DP to PS:

How can I set that up, or see the rela values in the energy dashboard:

Thanks for your help in advance

Hi,
I downloaded hassio-ecoflow in HACS but when I try to add my device, after entering the IP address it does circles for a long time and then says and Unknown Error Occurred.
I know the Delta Pro had some issue with a port that needed to be open which seems to be resolved now.
I don't know if the problem I am having with the River Pro is related or not.
I can't see anything in the HA logs to give me a hit what the problem might be.
Any tips in troubleshooting would be greatly appreciated.
Ecoflow app says firmware is V1.2.5.17 V3.0.1.11(Wi-Fi)
Home Assistant 2023.2.5

Firstly, really good job ! This repo works fine with my Ecoflow River (EF4 288Wh without extra batterie).
Nevertheless, it could be great to add the remaining time to the available sensors.
As this data is available in the log data, I think it could be added quite easily.

Hello! First of all thanks alot for your work, you really did an awesome job with this integration! In fact I installed HA only because of this.
I recently got a Delta Pro and I'm just about to finish the HA setup, using the latest HA version (2022.7.7) and hassio-ecoflow version 2.2.1

I noticed an issue that the Charging sensor says "Not charging" while the Delta Pro was running on AC with battery level at 50% and the AC output turned on. Actually it always says "Not charging", regardless of charging or not (bypass mode).
I can confirm the battery is indeed charging, with the battery level gradually increasing. Every related readout looks good, apart from the charging indicator.

Attaching debug output for your reference. Just let me know if you need more infos

config_entry-ecoflow-b59e0ccb379fad5eff3c3280bd845a54.json.txt
.

I have ordered the ecoflow micro inverter and would love to be able integrate the power generation into home assistant. I don't have the technical knowledge to do this but have been getting good with home assistant. I would be happy to help in any way possible

The serial number is used to manage the extra battery as a single device.

This avoids the problem of multiple entities even if they are shared by multiple units.

Issue

The following devices can have multiple extra batteries connected to them and I don't know how to get the serial number for each one.

• DELTA max
• DELTA pro

We are looking for someone who has these devices and two extra batteries and can work with us to find a way to solve this.

Thank you so much for this custom integration. It works very well with HA and my Delta Pro units.

I was wondering if there are any plans to expose additional sensors from the BMS in DP or EB units such as battery pack voltage/current and/or individual cell voltages (if available)?

If you have followed my previous posts you will be aware that I have integrated my Smart Home Panel to automate charging with Glow CAD smart meter. Everything is working, I am running firmware 1.0.1.18 on each Delta Pro. The app keeps telling me there is a new official firmware 1.0.1.61 which it wants me to update the Delta Pros to. I am just wondering if anyone has updated it and if this has caused any problems with the integration not working anymore?

I am currently too scared to update it in case it breaks everything but the changelog has definitely attractive fix of sorting out the excessive fan noise which would be useful but I am currently taking 'if its not broke don't try to fix it' mantra.

Hello,
I am trying to test ver2-beta. But I am getting 'Not Loaded' on all units which I have (RIVER Pro, DELTA Max, DELTA Pro).


What could be wrong?