I am experiencing an issue with my Bluetti AC70P charging station. When an external load is connected, the device displays error code E016 (Fun Error). Initially, both fans seem to spin normally. There is no dust or visible mechanical damage.
Did you check for firmware updates in the Bluetti App? Its important to connect by Bluettoth, when searching for new firmware updates.
It would be also interesting to know, what kind of external load this issue produce. Is it only with AC or DC outputs too? Only with high consumers (like hairdryer) or also small loads (like charging a smartphone).
I have already installed all the available updates through the Bluetti App. Unfortunately, the issue persists even with a small load, such as charging my smartphone via its charger through the AC port. The problem doesn’t seem to be limited to high-power consumers like a hairdryer.
Please let me know if there’s anything else I can try.
You also could check if there is any Errorcode that you can provide us. When connected to the AC70P, there should be a exclamation mark in the upper right corner, beside the settings symbol. Click on that and look at current errors or history and provide this information here.
Oh, now i get it. You mean “Fan error”. Thats what mentioned in the manual. Than it makes sense, that the unit refuse to charge/discharge.
Sorry, you even mentioned that error in the initial post.
I found similar behavior in these posts:
I suggest you to reach the local after sales team with that problem. @BLUETTI_CARE can help you to create a request and maybe get a replacement unit/repair when within warranty.
I have read about the two cases you mentioned. However, I have not made any structural modifications to the charging station (e.g., changing the fan), and I am not encountering multiple error codes. Instead, the same error, E016, repeats consistently.
The device is new, and sending it in for repairs would require shipping it to another city, which would take a significant amount of time. I am hopeful that the issue can be resolved through a firmware update.
Could you please advise if there is a way to reinstall the firmware or perform an additional update to address this problem?