Setup:
• SolarFlow 800 Pro
• 2x AB2000X battery packs
• No Smart Meter
Background:
I added a second AB2000X battery to a working Solarflow 800 Pro using WiF with a WiFi Hub 2.4ghz close by. The firmware updated automatically to V1.0.25 shortly after. Since then the behavior has been inconsistent and confusing.
Issue 1 — Second battery showed 0% and no temperature via WiFi
After adding Pack 2, the app showed Pack 1 at 100% and Pack 2 at 0% with –°C. However when connecting via Bluetooth, both packs showed correctly at 70% with normal temperatures. Removing Pack 2 and using only Pack 1 showed correctly via WiFi. It is unclear whether this is a cloud registration issue, a firmware bug, or something else.
Issue 2 — Device shows Standby via WiFi but is active via Bluetooth
Via WiFi the device constantly shows Standby even when it is actively discharging at 148W — which is clearly visible when connecting via Bluetooth. The WiFi/Cloud status does not reflect the actual device state.
Issue 3 — On-grid output resets to 0W
I set On-grid output mode to 200W. The setting appears saved but resets to 0W automatically within minutes via WiFi.
Issue 4 — HEMS reactivates itself
I disabled HEMS. It turns itself back on automatically, overrides manual settings, and resets On-grid output to 0W.
Issue 5 — “Setup failed” errors
Saving settings via WiFi frequently returns “Setup failed.” Sometimes requires 3 attempts.
What works:
• Both batteries function correctly via Bluetooth
• Solar charging works
• Settings applied via Bluetooth take effect immediately and correctly
• Device operates normally when observed via Bluetooth
Key observation:
Everything worked correctly before the update with one battery. Via Bluetooth everything still works. Via WiFi/Cloud the behavior is inconsistent and unreliable — suggesting the issue is in the cloud communication layer introduced or broken by V1.0.25.
Question for the community:
Has anyone else experienced similar inconsistencies after V1.0.25? Is there a rollback option?