The FranklinWH error codes list is best understood as a set of FranklinWH App alerts, operating-state messages, LED patterns, and diagnostic categories rather than one universal numeric-code chart. The aGate and aPower report grid, battery, communication, relay, temperature, and rapid-shutdown conditions, while the correct remedy ranges from waiting for stable utility power to calling a qualified installer.
Key Facts at a Glance
FranklinWH FHP faults commonly involve the aGate controller, aPower battery, grid relays, CT meters, communication buses, or thermal protection.
A flashing aPower indicator and an exclamation mark in the FranklinWH App indicate an abnormal operating state, but neither identifies the root cause by itself.
A standard system restart normally requires shutting down the aPower units, opening the aGate control switch, waiting about 2-5 minutes, and restarting in sequence.
Homeowners should not remove the aGate deadfront or test energized terminals to diagnose a relay, CAN, RS485, or grid-voltage fault.
Reversed CTs, unstable utility voltage, router changes, blocked ventilation, emergency-stop activation, and low battery state of charge produce different symptoms.
A persistent fault after one controlled restart usually needs installer diagnostics, firmware review, wiring inspection, or a warranty decision.
Why Is There No Single FranklinWH Numeric Code List?
FranklinWH does not present every FHP installation as one public, universal numeric-code directory. Alert wording can differ by aGate generation, aPower model, firmware version, app release, solar inverter, generator module, and installer configuration.
The practical FranklinWH error codes list therefore uses the exact app message as the primary identifier. A message such as “aGate Offline,” “Grid Fault,” “Fail-Safe Mode,” “System Stopped,” or “RSD Fault” is more useful than an assumed number copied from another installation. Record the complete message, timestamp, battery percentage, grid condition, aPower LED behavior, and whether solar production was active.
The FranklinWH troubleshooting materials direct users toward system status and Direct Connect functions rather than a single public lookup table. That distinction prevents a common mistake: treating a communication alert as proof that the battery hardware has failed.
What Does a FranklinWH Fault Actually Represent?
A FranklinWH fault represents a protective or diagnostic state detected by the energy management system. The aGate evaluates utility input, Smart Circuits, generator interfaces, internal relays, and meter data; the aPower evaluates battery-management information, inverter operation, cell conditions, and temperature.
A protective state can reduce output, disconnect the grid, stop charging, shed selected loads, or isolate a battery. Those actions may be intentional safety responses rather than component failures. FranklinWH systems are designed to prevent abnormal voltage, frequency, current, temperature, or communication conditions from propagating into household circuits.
How Does FranklinWH Fault Detection Work?
FranklinWH fault detection works through coordinated monitoring between the aGate Energy Management Controller and one or more aPower LFP battery units. The aGate checks grid voltage and frequency, relay status, Smart Circuit behavior, meter readings, generator signals, and communications; the aPower reports BMS, inverter, thermal, and battery-state information.
When the system detects an abnormal condition, the FranklinWH App can display an exclamation mark and a descriptive alert. The aPower indicator may flash approximately once per second during a fault or abnormal state, although the exact light behavior should be checked against the user manual for the installed hardware version.
The protection response depends on the fault. An out-of-range grid condition can open the grid relay and prevent unintentional islanding. A battery or communication fault can place the system in Fail-Safe Mode. A Smart Circuit may shed a selected load to preserve battery operation.
Which Components Generate the Main Alerts?
| Component or signal | What it monitors | Typical alert family | First safe observation |
|---|---|---|---|
| aGate controller | Grid, relays, CT meters, Smart Circuits | Grid Fault, Meter Error, aGate Offline | Check app connectivity and utility status |
| aPower battery | BMS, inverter, cells, temperature | Battery Fault, System Stopped, Over-Temperature | Record state of charge and LED pattern |
| CAN communication | aGate-to-aPower data link | Communication Loss, Fail-Safe Mode | Note whether one or all batteries disappear |
| RS485 or meter wiring | Meter and accessory data | Meter Error, CT Configuration | Compare app power-flow direction |
| Rooftop rapid shutdown | PV safety transmitter and receivers | RSD Fault, PV Shutdown | Check emergency-stop status without opening equipment |
| Wi-Fi or cellular path | Cloud and remote app connection | Offline, No Connection | Try local Direct Connect before changing wiring |
What Do the Main FranklinWH Error Categories Mean?
The main FranklinWH error categories are grid and relay faults, communication faults, meter and CT errors, battery shutdowns, thermal protection, rapid-shutdown events, and generator or load-management problems. Correct classification matters because each category has a different safe response.
The table below translates common alert descriptions into likely mechanisms. The wording is representative, not a guarantee that every installed system uses the same label.
| Alert or status | Likely mechanism | Homeowner check | Professional action |
|---|---|---|---|
| Fail-Safe Mode | Lost aGate, aPower, or inverter communication | Check whether one or several units are missing | Test CAN wiring, termination, connectors, and firmware |
| Grid Fault | Utility voltage or frequency outside limits | Check whether neighbors also lost power | Measure line voltage and inspect relay and utility settings |
| Grid Relay Disconnected | Protective relay opened | Wait for stable utility service | Verify voltage, frequency, relay operation, and interconnection |
| aGate Offline | Wi-Fi, router, DHCP, or cellular communication issue | Use System Direct Connect | Reconfigure network or install suitable Ethernet service |
| Meter or CT Error | CT orientation, phase pairing, or meter wiring problem | Compare live import and export direction | Correct CT arrows, phases, and commissioning settings |
| System Stopped | Low battery, shutdown command, or internal protection | Reduce large loads and record state of charge | Diagnose battery, load, inverter, and restart conditions |
| Battery or BMS Fault | Cell, temperature, contactor, or BMS condition | Do not open the battery enclosure | Retrieve service logs and assess warranty |
| Over-Temperature | High ambient temperature, blocked airflow, or internal heat | Clear external obstructions | Check clearances, installation location, and thermal readings |
| RSD Fault | Rapid-shutdown command or transmitter-receiver loss | Reset an accessible emergency stop if safe | Test keep-alive signal and rooftop devices |
| Generator Fault | Start signal, neutral, fuel, or module issue | Check generator operating status | Test two-wire control, bonding, transfer logic, and module wiring |
How Do You Safely Reset a FranklinWH System?
A safe FranklinWH restart usually takes about 2-5 minutes of power-off time, plus the time needed for the system to boot and reconnect. The restart works best for transient communication glitches, temporary grid abnormalities, and some post-commissioning lockouts, but it cannot repair reversed CTs, damaged wiring, failed cells, or an active utility problem.
Do not reset a system that is hot, wet, physically damaged, smoking, making unusual sounds, or showing signs of arcing. During an outage, disconnect nonessential high-power loads first, because air-conditioning compressors, electric water heaters, pumps, and EV chargers can prevent a low-battery system from recovering.
Step 1: Record the Alert and System State
Capture the exact FranklinWH App message, battery state of charge, grid status, solar production, aPower LED behavior, and the time the fault began. Screenshots preserve information that may disappear after a reboot.
Step 2: Turn Off Each aPower Unit
Use the power push-button or approved operating switch on each aPower unit. If multiple batteries are installed, turn them off individually and confirm that each unit has stopped.
Success checkpoint: Each aPower shows the expected powered-down state in accordance with the installed manual.
Common mistake: Turning off only one battery when the alert involves several units. A remaining battery can keep the communication fault active.
Step 3: Open the aGate Control Switch
Turn the aGate red system control switch to the prescribed OFF position. Do not remove the deadfront, touch line terminals, or open sealed high-voltage compartments.
Success checkpoint: The aGate enters its documented shutdown state without unusual sound, odor, heat, or visible damage.
Common mistake: Treating the control switch as permission to access energized internal equipment. The switch does not make every internal compartment safe to touch.
Step 4: Wait for Internal Discharge
Leave the system fully off for approximately 2-5 minutes. A short pause may not clear a latched communication or control state.
Success checkpoint: The full waiting interval has elapsed and no unsafe condition has appeared.
Common mistake: Repeatedly toggling switches within seconds. Rapid cycling can complicate diagnosis and does not substitute for a complete shutdown.
Step 5: Restart the aGate and Batteries in Sequence
Turn the aGate control switch ON first. Then turn each aPower ON one at a time, waiting approximately 15 seconds between units when the installed instructions specify sequential startup.
Success checkpoint: The app begins to detect the aGate and each aPower, and the system progresses toward Normal Operating State.
Common mistake: Starting all batteries simultaneously. Sequential startup gives the controller time to identify each battery and can make a missing-unit problem easier to isolate.
Step 6: Verify Status Through Direct Connect
Open the FranklinWH App and use More, then System Direct Connect, if cloud connectivity remains unavailable. Check whether the system changes from Fault or Fail-Safe Mode to Normal Operating State.
Success checkpoint: The original alert clears, every installed aPower appears, and energy-flow readings are plausible.
Common mistake: Assuming the app is fixed because the LED becomes white. Verify grid, battery, solar, and load readings separately.
Which FranklinWH Faults Can a Homeowner Check?
Homeowners can safely check the app message, utility outage status, visible switches, network availability, emergency-stop position, external ventilation, and household load size. Homeowners should not measure live switchboard voltage, inspect CAN termination, correct CT wiring, open the aGate deadfront, or bypass a protective relay.
Why Does FranklinWH Show aGate Offline?
FranklinWH shows “aGate Offline” when the app cannot communicate with the controller through the available network path. The cause may be a router replacement, changed Wi-Fi password, DHCP reassignment, weak signal, local internet outage, or unavailable cellular backup.
First determine whether the equipment is operating while only remote communication is lost. Try System Direct Connect from the FranklinWH App, then inspect the router without resetting unrelated network equipment. Ethernet can provide a more stable path where the installation and network design support it, but Ethernet will not correct a powered-down aGate or a failed internal communication bus.
Expert rule: A cloud-offline message is not evidence that the battery is empty or defective. If local Direct Connect shows normal operation, prioritize networking rather than battery replacement.
Why Is the Grid Relay Disconnected?
The grid relay disconnects when the aGate detects utility voltage, frequency, phase, or other conditions outside its programmed interconnection range. A reported utility spike above approximately 270 V is a field example of a condition that can cause protective disconnection, but the actual threshold depends on configuration, jurisdiction, and equipment settings.
The system should reconnect only after acceptable grid conditions return and the reconnection delay completes. Do not force reconnection or use a manual bypass unless a qualified professional has confirmed that the procedure is authorized for the installation.
| Visible condition | Likely interpretation | Safe response | Escalation trigger |
|---|---|---|---|
| Neighbors also lack power | Utility outage | Wait for utility restoration | Utility reports extended outage |
| Grid unavailable, battery normal | Normal islanded operation or grid relay open | Check app grid status | Relay remains open after stable service |
| Grid voltage repeatedly abnormal | Utility or service-equipment problem | Contact utility or installer | Repeated trips after utility confirmation |
| Grid restored, relay remains open | Latched fault or incomplete verification | Perform one approved restart | Persistent state after restart |
| Relay trips under large load | Possible wiring, load, or voltage issue | Turn off nonessential loads | Immediate repeated trips |
Why Does FranklinWH Report a CT or Meter Error?
A CT or meter error usually results from reversed current-transformer orientation, incorrect phase pairing, a loose connection, or commissioning configuration. In a correctly oriented installation, the app should show import and export in the expected directions; readings that mirror solar production or show implausible load flow warrant professional inspection.
Split CTs must be installed on the correct conductors and paired with the correct phases. The exact terminal mapping depends on the aGate version and installation guide, so homeowners should not move CTs based on an internet diagram.
Expert rule: Negative power flow is not automatically a bad CT. Solar export naturally reverses the direction of measured power. Compare the reading during known grid import, such as when solar is inactive and a moderate household load is running.
What Do Low Battery, Thermal, and RSD Alerts Mean?
Low-battery, thermal, and rapid-shutdown alerts indicate different protective mechanisms. A low state of charge limits available energy, thermal protection reduces or stops output when temperatures exceed safe limits, and RSD interrupts photovoltaic production when the rapid-shutdown circuit or emergency stop is activated.
| Condition | Typical symptom | Immediate action | Professional diagnosis |
|---|---|---|---|
| State of charge near 0% | System Stopped or no backup output | Turn off HVAC, EV, pumps, and water heating | Assess black-start capacity and battery health |
| High ambient temperature | Reduced output or thermal alert | Clear debris and improve shade or airflow | Check enclosure clearances and heat readings |
| Cold battery condition | Charging restriction or delayed recovery | Wait for permitted temperature range | Verify heater, sensors, and firmware |
| Emergency stop active | PV or system shutdown | Confirm accessible stop is released | Test shutdown loop and control wiring |
| Rooftop RSD communication loss | Solar remains unavailable | Do not climb onto the roof | Test transmitter, receivers, and keep-alive signal |
FranklinWH user materials describe a reserved energy buffer for system startup, while community and installer documents often describe a black-start reserve near 1 kWh. Treat that figure as installation and firmware dependent, not as a promise that a depleted system will start every load.
Heavy loads are the most common recovery obstacle. Disconnecting a central air conditioner or EV charger can allow the inverter to stabilize, while leaving those loads connected can cause repeated startup collapse.
How Do Generator and Load-Shedding Faults Differ?
Generator and load-shedding faults differ because the generator supplies an external source while Smart Circuits control which household loads remain energized. A generator alert can involve start-stop wiring, fuel, transfer logic, neutral bonding, or the optional Smart Generator Module; a load-shedding event can be normal battery-protection behavior.
Portable generators and vehicle-to-home sources require particular caution. A floating neutral, bonded neutral, improper transfer arrangement, or incompatible grounding configuration can trip ground-fault protection or create an unsafe parallel-neutral condition. The generator manufacturer, FranklinWH documentation, local electrical code, and the installer’s design must govern the connection.
The Smart Generator Module can provide automated two-wire start and stop control where correctly installed. A homeowner should not improvise a generator connection through an outlet or alter neutral-ground bonding to clear an error.
When Should You Call a FranklinWH Installer?
Call a FranklinWH installer when a fault persists after one controlled restart, returns immediately, involves high voltage, affects a battery BMS, follows water intrusion, or prevents safe backup operation. Installer work is also required for CT rewiring, CAN or RS485 testing, grid-voltage measurement, RSD diagnosis, generator bonding, firmware service, and warranty replacement.
| Situation | Homeowner action | Installer or utility action | Typical resolution window |
|---|---|---|---|
| One transient communication alert | Record, restart once | Review only if it returns | 5-30 minutes |
| aGate remains offline | Try Direct Connect | Reconfigure network or inspect controller | Same day to several days |
| Grid relay repeatedly opens | Confirm utility status | Utility voltage test and relay diagnosis | 1-5 business days |
| CT readings remain reversed | Avoid rewiring | Correct orientation and phase pairing | 1-3 hours on site |
| Battery BMS or thermal fault | Leave enclosure closed | Retrieve logs and assess hardware | 1-7 business days |
| RSD fault persists | Check accessible stop only | Test rooftop devices and transmitter | 1-3 visits |
| Warranty hardware replacement | Preserve alert evidence | RMA and replacement coordination | Often 3-7 business days after approval |
Warranty duration, labor coverage, and response time depend on the applicable FranklinWH warranty, installer agreement, and failure classification. The FranklinWH end-user warranty document, rather than a community estimate, controls eligibility.
How Much Does FranklinWH Error Repair Cost?
FranklinWH error repair can cost $0 under a covered hardware warranty, while typical out-of-warranty diagnostic visits often fall around $150-$350. CT correction, conduit moisture damage, network work, generator retrofits, travel distance, and local labor rates can move the final invoice substantially.
| Repair scenario | Typical cost range | Typical labor time | Main cost variable |
|---|---|---|---|
| Covered hardware replacement | $0 for covered part | 1-4 hours | Warranty approval and installer labor |
| Network reconfiguration | $0-$250 | 30-90 minutes | Installer network policy |
| CT or phase correction | $150-$350 | 1-3 hours | Access and rewiring complexity |
| Diagnostic service visit | $150-$350 | 1-2 hours | Travel and test requirements |
| Generator Module retrofit | $700-$1,350 total | 3-8 hours | Hardware, controls, and labor |
| Moisture-related repair | $250-$1,500 or more | 2-8 hours | Corrosion and enclosure damage |
These are typical planning ranges, not FranklinWH price schedules. Ask for a written scope that separates diagnostic labor, replacement parts, travel, permit work, and warranty-covered items.
How Does FranklinWH Compare With Other Battery Systems?
FranklinWH differs from Tesla Powerwall 3 and Enphase IQ Battery 5P mainly in system architecture, generator integration, circuit control, and retrofit strategy. FranklinWH FHP uses an aGate controller with separate aPower batteries and is often selected for flexible AC-coupled retrofits, while Powerwall 3 emphasizes an integrated inverter and Enphase uses a modular microinverter ecosystem.
| Decision criterion | FranklinWH FHP | Tesla Powerwall 3 | Enphase IQ Battery 5P |
|---|---|---|---|
| Nominal storage example | 15.0 kWh with aPower 2 configuration | 13.5 kWh | 5.0 kWh per battery |
| Reported continuous output example | 10.0 kW system figure | 11.5 kW system figure | 3.84 kW per battery |
| Coupling approach | AC-coupled with aGate | Integrated DC and AC inverter architecture | AC-coupled microinverter ecosystem |
| Battery chemistry | LFP | LFP | LFP |
| Generator integration | Optional native Generator Module | Usually external integration equipment | Enphase Smart Switch ecosystem |
| Smart-load control | Three aGate Smart Circuit positions in referenced configurations | External load-management equipment commonly required | Dedicated Enphase control products |
| Retrofit orientation | Strong fit for existing compatible solar | More design changes may be needed | Strong fit for Enphase-centered sites |
Published specifications change by model and firmware, so compare the exact datasheet, not a product-family summary. FranklinWH is not the best fit for every project: a new solar build may favor an integrated DC architecture, while a small modular installation may favor incremental Enphase batteries.
What Mistakes Cause Repeat FranklinWH Faults?
Repeat FranklinWH faults often come from installation or operating conditions rather than a failed battery. The highest-impact mistakes include reversed CTs, top-entry conduit that allows water toward electronics, incomplete battery startup during commissioning, unmanaged heavy loads at low state of charge, and generator neutral-ground conflicts.
Reversed CTs and Incorrect Phase Pairing
A reversed CT can make import appear as export or distort load calculations. Correcting the arrow direction is only half the repair, because the CT must also correspond to the correct phase and software input.
Moisture Entering Through the Enclosure Top
Unsealed top penetrations can direct rainwater toward internal components. Outdoor conduit should follow the approved entry points, sealing method, drainage design, and clearances in the installation guide.
Batteries Left Asleep During Commissioning
A battery that remains off can appear as a missing string or communication failure. Commissioning should identify every installed aPower and confirm its reported state before the system is handed over.
Heavy Loads Connected During Black Start
A depleted battery may have enough energy to boot controls but not enough to start multiple compressors and heating elements. Load shedding should be configured before an outage, not improvised after the battery reaches its minimum reserve.
What Information Should You Send Support?
Send support the exact alert, screenshots, equipment serial numbers, firmware versions if visible, installation date, battery state of charge, outage status, LED behavior, and the result of one approved restart. Include whether the issue began after a storm, router replacement, firmware update, generator installation, or electrical work.
A concise service record should contain:
- Alert text and timestamp.
- aGate status and number of aPower units detected.
- Grid, solar, battery, and home-load readings.
- Visible switch positions and emergency-stop status.
- Weather, temperature, water exposure, or unusual odor.
- Photos of external equipment and labels, without opening energized compartments.
- Whether the fault cleared and returned after restart.
This evidence reduces the chance that a technician treats an offline app as a battery failure or treats a grid relay trip as a communications problem.
FranklinWH Error Codes List FAQ
Does a flashing aPower light always mean the battery has failed?
No. A flashing aPower indicator can accompany communication loss, grid protection, low battery, thermal protection, rapid shutdown, or another abnormal operating state. The FranklinWH App alert, detected battery count, state of charge, and outage status are needed to narrow the cause. Persistent or repeated battery-specific alerts require installer review.
Can I clear a FranklinWH fault from the app?
The FranklinWH App can display alerts, provide local Direct Connect access, and support some configuration or update functions, but it cannot repair wiring, restore utility voltage, replace a failed BMS, or correct a reversed CT. Use the app to document and verify the condition, not to bypass a safety lockout.
Why does FranklinWH show no connection to the grid?
FranklinWH may show no grid connection because the utility is out, the grid relay is open, voltage or frequency is outside limits, or the controller has lost valid meter information. Check the utility status and app details first. A persistent message after stable service needs professional voltage, relay, and meter testing.
Will a FranklinWH battery recharge after reaching 0%?
A FranklinWH battery may recover when solar or an approved generator source becomes available, but recovery depends on the system’s startup reserve, load level, temperature, and fault state. Turn off major loads before waiting for solar recovery. If the system cannot restart under suitable conditions, contact the installer.
Is a FranklinWH reset safe during a power outage?
A controlled reset can be appropriate during an outage when the equipment is dry, cool, undamaged, and operated according to the installed manual. Shut down large loads first and do not open the aGate. A reset cannot substitute for emergency service when there is smoke, fire, water intrusion, arcing, or physical damage.
How long does FranklinWH error-code repair take?
A transient alert may clear within 5-30 minutes after conditions normalize and one approved restart. Network or CT work commonly takes one service visit, while warranty hardware replacement may take several business days after diagnosis and approval. Utility faults, rooftop RSD access, permits, and replacement availability can extend the schedule.
The Bottom Line
The FranklinWH error codes list is a diagnostic map, not a universal numeric-code catalog. Start with the exact app alert and aPower LED state, classify the issue as grid, communication, meter, battery, thermal, RSD, or generator related, and perform only the documented restart when the equipment is safe. If the fault returns, involves energized equipment, or affects a battery or relay, preserve the evidence and call a qualified FranklinWH installer.