Deye Balcony ESS (AE-FS2.0-2H2) – local Solarman entities freeze after initial update and wrong data

[euriconogueira]

Hi,

I’m experiencing an issue using the Solarman local integration with a Deye Balcony ESS / Micro Hybrid ESS (AE-FS2.0-2H2).

The integration connects successfully, creates the device and many entities, but most sensor values update only once at startup and then freeze, even though the device is online and updating correctly in the Deye Cloud.

Environment

Home Assistant: latest stable

Solarman integration: 1.5.1

Connection: Local TCP (port 8899)

Slave ID: 1

Definitions tested:

deye_2mppt.yaml

deye_hybrid.yaml

Embedded Logger Information

Embedded logger SN: 3436142*

Sensor list ID: 5417

Module version: MW4_32_5417_SS_04_00.00.00.0B

Extended system version: 00-00-00-0A

Data logging interval: 60 seconds

Cloud upload interval: 5 minutes

Signal strength: 96%

Connection: Wi-Fi (STA)

The same logger reports correct, frequently updated values in the Deye Cloud and on solarmanpv.com.

Inverter / ESS Information

Device type: Deye Balcony ESS / Micro Hybrid ESS

Rated power: 1000 W

Inverter SN: 2503170*

Communication Protocol Version: 0202

Main Control Version: 7420-0138

LoRa Master FW version: C13C

Equipment type: 2304

Wireless CT sub nodes: 1

Observed Behavior

Local TCP connection works and entities are created.

status_lastUpdate and update_time sensors continue updating periodically.

All other sensors (power, current, production, grid, etc.):

Update only once at integration startup

Then remain frozen

Update again only after restarting the integration

No Solarman-related errors appear in the Home Assistant logs.

Deye Cloud shows real-time changing values while local values remain frozen.

Is the Deye Balcony ESS / Micro Hybrid ESS (AE-FS2.0-2H2) and/or the MW4 / sensor list 5417 embedded logger currently supported by the Solarman local integration?

If not, I’m happy to provide additional logs or help test experimental definitions.

Thanks for your work on this integration.

[rmvn]

Have you ever tried to contact deye to check if there is a new firmware update that might solve this?

I'm asking because i just order this same deye balcony for me, and I was hoping i could use solar assistant with it, or integrat it in home assistant.

But after some research i see that I can not have huge hopes.

[euriconogueira]

Have you ever tried to contact deye to check if there is a new firmware update that might solve this?

I'm asking because i just order this same deye balcony for me, and I was hoping i could use solar assistant with it, or integrat it in home assistant.

But after some research i see that I can not have huge hopes.

Hi,

Yes — I actually contacted Deye and updated the firmware in the meantime, but unfortunately it didn’t solve the issue.

I also tested with the alternative Solarman integration available here:
https://github.com/davidrapan/ha-solarman

The behavior is exactly the same: values update once at startup and then freeze.

From what I’ve been able to investigate, this seems to be related to how the device exposes data over Modbus RTU. There’s already a discussion pointing in that direction here:
davidrapan/ha-solarman#715

So at this point it doesn’t look like a simple firmware issue, but rather a limitation / incompatibility in how this specific Balcony ESS (AE-FS2.0-2H2 with MW4 logger / sensor list 5417) handles local polling.

Cloud data keeps updating fine, but local TCP reads don’t behave like expected.