The 0 to 4 Watts output issue. Tracing the error

[robdidu]

Hi there. Since I'm using Astramter one or both of my B2500Ds are entering a kind of dead end state, where they won't accept any new data from the meter and somtimes dropping the power to 4 Watts or smth. Until today I thought, that I can identify this "error" by just checking if the output of one storage is lower than 10 Watts, but today I saw that one starge froze at 96 Watts output. Taking this into account, I think that this might also be responsible for the imbalanced distribution of discharge in my setup.
Good news No.1: a restart of the storages fixes the dead end state. While a restart of Astrameter won't.

Good news No.2: I happen to have a debug log file.

last_12k_lines.log

From the logs, it seemes like both storages got stuck shortly after waking up from their DoD sleep.
Then at 8:50 there was another incident dropping the output of one storage to 4 Watts, while the other remained in their former frozen state.
This might be a Marstek issue, but we should check what Astrameter is sending to the storages that may be is responsible for sending them to a frozen state?

Any help is appreciatet.

[stokifan]

Hi, I had similar issues, and fixed them for the most part by tuning WiFi settings. For the remaining few glitches I use esphome-b2500 as there you can read the connection status oft the device and respond to it (reboot for instance). And then it provides the data too in MQTT. Am 19. Juni 2026 11:49:42 MESZ schrieb robdidu ***@***.***>:

…

Hi there. Since I'm using Astramter one or both of my B2500Ds are entering a kind of dead end state, where they won't accept any new data from the meter and somtimes dropping the power to 4 Watts or smth. Until today I thought, that I can identify this "error" by just checking if the output of one storage is lower than 10 Watts, but today I saw that one starge froze at 96 Watts output. Taking this into account, I think that this might also be responsible for the imbalanced distribution of discharge in my setup. Good news No.1: a restart of the storages fixes the dead end state. While a restart of Astrameter won't. Good news No.2: I happen to have a debug log file. [last_12k_lines.log](https://github.com/user-attachments/files/29132021/last_12k_lines.log) From the logs, it seemes like both storages got stuck shortly after waking up from their DoD sleep. Then at 8:50 there was another incident dropping the output of one storage to 4 Watts, while the other remained in their former frozen state. This might be a Marstek issue, but we should check what Astrameter is sending to the storages that may be is responsible for sending them to a frozen state? Any help is appreciatet. -- Reply to this email directly or view it on GitHub: #501 You are receiving this because you are subscribed to this thread. Message ID: ***@***.***>