The EpEver line of MPPT solar charge controllers is an excellent value-for-money for some use cases. They cost about half as much as prettier, more-prestigious controlllers.

• the controllers can take massive overpaneling; the smaller units (≤40A) have documentation that allows +50% overpaneling¹⁾. The larger units show +200%²⁾
• the passive heatsinks are huge for their rated capacity
• accessories like display, temp probes, etc, are extremely inexpensive
• the current user manuals³⁾ are quite good

As with vans, all controllers have issues. This page aims to list known⁴⁾ issues with EpEver controllers.

They may not be a fit for all use cases, though. Consider these drawbacks in the light of your own intended scenario:

• the MPPT algorithm is not particularly robust
  • it will adjust to changing conditions, but it can be slow. One might say “plodding”.
  • it can be slow to react after long periods of no load - see this reddit post where I describe the phenomenon
  • it can get confused in complex solar conditions, as with partly-cloudy skies and high winds, or in breezes that move partial shade around on the panels. In these conditions Vpanel can crash to just above Vbatt, severely hobbling solar harvest.⁵⁾
• the large AN controllers (≥50A) have undersized terminal screws which can snap under overzealous tightening. IMO EpEver should update the design with hefty BN-series terminal screws.
• firmware does not appear to be field-upgradable without hacking
• Absorption duration cannot be zeroed out; the minimum duration is 10 minutes.
• Absorption duration max is 180 minutes

• mppt epever tracker issue
• EPever EPsolar Tracer 4215B MPPT review PART 1 - 4215BN Taking 5 minutes to find MPPT @ 11:10. Sails right past MPP at 10:36.
• The EPSolar EPEver Tracer A Series after Nine Months of Use - 12v Solar Shed - crashed PV voltage causing low output at 4:05.

My epever often pulls pv voltages down to battery voltage acting like PWM. Getting really annoying now. It works okay with 12v and 17.5v panels, but the bigger panels with a voltage of 35v present a problem on cloudy days. It drags thr voltage down, and doesnt let it back up until i reset the unit. It then lets the panels back up to proper voltage and starts producing decent power again. (source)

I have the 4215bn with mt50, and whenever I connect my solar panels in series (2x100w), it will display the accumulated voltage for a few seconds (40w) under the pv icon, then it will go down to between 13-20v, immediately, even if the weather hasn't changed (no clouds and fulll sunlight). (source)

I'm sending my tracer3215bm back today as the mppt tracking issue is a blocker for me. I have 3 60 cell panels in series for a total of around 90v pv. This is on a 24v system. One morning it will work fine and the next it will get stuck down around 28v and never increase leaving my output at a fraction of what it could be. The only way to get it to increase the pv voltage is to disconnect the pv array momentarily. (source)

Facing the same with Epever (12v system) in bad conditions it will pull the 2x 18v panels in series down to single panel voltage range of 14-18v. I resorted to taking my panels in parallel (which sucks due to higher current and cable losses), which wastes less. In northern europe this is a killer for my batteries in winter, as i cannot even maintain a proper float voltage with my equipment attached. (source)

The system seems to work as it should most of the time. On occasion in full sun the charge controller shows a lower voltage ie 26.4 v about half of what it typically does in full sun. If I unplug everything and plug the panels back in it will return to the higher voltage around 60v and begin working normally again. (source)

I used a epever 3210an controller for about a year. I was using lead acid. With the same issues you're having. A passing cloud will cause the charge controller to get lost tracking. And the array voltage will drop and get stuck. Having to constantly watch then unplug and reconnect to get it going again. (source)

just started having this issue all of a sudden, it's supposed to be 102 volts and it drops down to 28 volts (24 volt battery system) and when I disconnect my panels and reconnect it seems to resolve…. so confused myself not sure what started it, because it never used to do this. Has anyone solved this issue? – source

I have 2 3210AN and one of them have the same problem.. need to disconnect to PV and need 3-5 second to track correctly. it's cause 8% less energy production compare to another one. - source

I have 3210AN and the same problem. I only have one panel Risen 440Wp Vmpp 43.8V. In the morning or in the cloudy sky Mppt does not work. Holds 14V about 24W. When disconnected it goes on about 43V and shows 100W. This is annoying. This is evident software error. – source

im having the same issue with epever charge controller. Early morning before the sun fully hits the panels 17 volts and .5 amps from a 60 volt array 300 watt array. I can unplug the panels and reconnect at it goes up to 57 or so volts then slowly drifts back to 17 again. Does the tracking just not work right or what is your opinion. I ran 2 100 watt 18.9 vmp panels on the epever. And 2 on a pwm. The mppt would go from 150 watts in full sun to 100 watt output every 20 minutes or so. And the pwm would steady put out 148 watts. In an all day comparison pwm won producing more watt hours.⁶⁾

I threw out my EPSolar Tracers for the same reason, equal paneling with correct voltages in a test of 3 EP Solar Tracers verses 3 Trace C-40 PWM The old trace units preformed much better. … [the epever] would slowly sink in PV input volts until reset or maybe 20-30 minutes later would do a full sweep and come up to a decent input voltage. I bought a Classic…..problems gone⁷⁾

After driving with the Victron DC-DC charger kicking on, the Epever MPPT solar charge controller would act similar to a PWM controller: it would read incoming voltage close to the battery's and drastically reduce incoming amps from what was typical for our setup. Resetting breakers or factory resetting the MPPT and setting it up again would fix it until we drove again.source