Understand your system. Find the right setting.

A 32-field worksheet: what to collect, where it is used and why it changes system behaviour.

Start with the exact equipment list and a system drawing. Record the source of each value: nameplate, battery integration guide, approved electrical design or commissioning measurement. Leave an unknown value unresolved rather than filling it with a forum example.

Separate installation limits from operating preferences. Hardware compatibility, wiring, protection and approved grid settings establish the boundary. Self-consumption, reserve and charging schedules operate inside that boundary. The active BMS may allow less current than an inverter setting requests.

Use this worksheet alongside the applicable product manual. It records decisions to make, not a universal commissioning sequence. Electrical installation, opening equipment, live measurements and backup transfer tests need a qualified installer following the exact product procedure.

Inverter identity

Where it is used

Nameplate / equipment record

What to enter or collect

Full SUN model, all suffixes, serial number and region.

Why it matters

A 12 kW rating alone does not distinguish phase arrangement, battery voltage class or hardware generation.

Firmware revisions

Where it is used

Device information

What to enter or collect

Main, control and display versions shown, plus logger firmware.

Why it matters

Record the complete set before comparing screenshots or requesting support.

Applicable manuals

Where it is used

System record

What to enter or collect

Exact inverter, battery, logger and meter manual versions.

Why it matters

Keep the regional edition and model range with the configuration record.

AC supply and grid code

Where it is used

Grid Setting / approved design

What to enter or collect

Supply phase arrangement and the grid profile specified for this installation.

Why it matters

The installer must match the actual connection and network requirements.

Battery model and voltage class

Where it is used

Battery Setting / nameplates

What to enter or collect

Exact battery model and supported inverter pairing; LV or HV architecture.

Why it matters

LP and HP inverter families cannot share an assumed battery recipe.

Bank arrangement

Where it is used

Battery record

What to enter or collect

Module count, series/parallel arrangement and controller model.

Why it matters

A module specification does not establish assembled bank voltage or current limits.

Battery capacity — Ah

Where it is used

Battery Setting where requested

What to enter or collect

Documented bank capacity in Ah at the assembled bank voltage.

Why it matters

Series connections increase voltage; parallel capacity adds only in an approved arrangement.

Battery energy — kWh

Where it is used

Planning / monitoring where requested

What to enter or collect

Nominal and usable energy as separate figures.

Why it matters

Energy capacity helps estimate duration; it is not inverter output power.

Battery operating mode

Where it is used

Battery Setting

What to enter or collect

Supported managed-lithium mode and protocol, or documented voltage-based configuration.

Why it matters

A chemistry label alone does not prove communication compatibility.

BMS communication path

Where it is used

Battery port / integration instructions

What to enter or collect

CAN or RS485, exact cable pinout, ports and battery addressing.

Why it matters

An RJ45 connector does not prove that an ordinary Ethernet cable is correct.

Battery current limits

Where it is used

Battery Setting / live BMS data

What to enter or collect

Approved charge and discharge limits, units and whether values are bank or per-module.

Why it matters

Battery, inverter and installed DC path all constrain usable current.

Charging voltage rules

Where it is used

Battery documentation / supported setup

What to enter or collect

Manufacturer targets and temperature rules only where the selected mode requests them.

Why it matters

Protection cutoffs and charging targets serve different purposes.

Battery reserve

Where it is used

Operating plan / work mode

What to enter or collect

Desired routine reserve and how this firmware applies it.

Why it matters

An everyday reserve is distinct from the BMS emergency stop.

Shutdown, low battery, restart

Where it is used

Battery Setting if available

What to enter or collect

Documented thresholds and units for the selected battery mode.

Why it matters

These names describe different events; equal thresholds can produce unstable behaviour.

System Work Mode

Where it is used

System Work Mode

What to enter or collect

Chosen supported mode and the loads it is intended to cover.

Why it matters

Zero Export to Load and Zero Export to CT describe different measured boundaries.

CT or meter model

Where it is used

Meter / limiter configuration

What to enter or collect

Exact supported measuring device and connection method.

Why it matters

The controller needs a compatible and correctly configured measurement source.

Meter position and direction

Where it is used

Drawing / commissioning

What to enter or collect

Measurement boundary, CT orientation, phase assignment and an import test.

Why it matters

A wrong sign or phase mapping can make the controller respond in the wrong direction.

Export policy

Where it is used

Work Mode / approved connection

What to enter or collect

Permitted export and power limit; verify Solar Sell state.

Why it matters

The words zero export alone do not document all export-related settings.

Zero-export target

Where it is used

Work Mode if available

What to enter or collect

The exact manual interpretation of the field and commissioned target.

Why it matters

Do not transfer a numeric example or hard/soft-limit interpretation between regional firmware versions.

Clock and timezone

Where it is used

Basic Setting / plant settings

What to enter or collect

Local date, time, timezone and daylight-saving behaviour.

Why it matters

A correct schedule can operate at the wrong real time when clocks differ.

Time of Use enable

Where it is used

System Work Mode

What to enter or collect

Whether scheduled operation is enabled and which days apply.

Why it matters

Visible rows may be inactive until enable controls are selected.

Schedule intervals

Where it is used

Time of Use table

What to enter or collect

A complete sequence of intervals including the overnight transition.

Why it matters

Check every interval, not just the cheap-price window.

Schedule battery target

Where it is used

Time of Use table

What to enter or collect

The SOC percentage or voltage requested for each period.

Why it matters

Its effect depends on work mode and charge permission; it is not an always-charge command.

Schedule Power field

Where it is used

Time of Use table

What to enter or collect

The exact manual definition and permitted value in W.

Why it matters

Do not assume this is grid-charging power; common hybrid manuals describe a battery discharge limit.

Grid charging permissions

Where it is used

Battery Setting / Time of Use

What to enter or collect

Overall permission, per-period selection and charging current.

Why it matters

Schedule, battery target, source availability and BMS limits must all agree.

Generator role

Where it is used

GEN port / generator controls

What to enter or collect

Approved role, generator capability and supported start/stop interface.

Why it matters

Generator input, smart load and AC coupling can use the same configurable port differently.

Backup circuits

Where it is used

LOAD/EPS output / drawing

What to enter or collect

Connected circuits, continuous and starting demand, and model-specific phase limits.

Why it matters

The grid-side house wiring is not automatically backed up by a battery.

PV array record

Where it is used

PV design / MPPT inputs

What to enter or collect

Panel model, series/parallel counts, temperature-corrected Voc, current and tracker allocation.

Why it matters

Check exact MPPT voltage, current and short-circuit limits before installation.

Protection and wiring record

Where it is used

Approved electrical design

What to enter or collect

Cable routes, isolation, overcurrent protection, earthing and protective devices.

Why it matters

Device ratings do not replace installation-specific protection design.

Logger and app identity

Where it is used

Logger label / plant account

What to enter or collect

Logger model and serial, supported app, owner account and access roles.

Why it matters

DeyeCloud and SOLARMAN arrangements depend on logger and provisioning.

Network record

Where it is used

Router / logger setup

What to enter or collect

Supported Wi-Fi band or wired connection, signal condition and online timestamp.

Why it matters

A connected phone does not prove that the logger has reached its cloud service.

Commissioning evidence

Where it is used

Handover record

What to enter or collect

Saved settings, normal-load import test, charging test and approved backup test.

Why it matters

Reopen saved settings and verify measured behaviour before handover.

What to check or record

1. Identify all model suffixes and the applicable regional manual.
2. Record units with every value: A, W, kWh, Ah, V and % are not interchangeable.
3. Establish compatibility and protection before entering operating settings.
4. Save, reopen and verify settings against actual power-flow behaviour.

Match the complete nameplate code, including phase, voltage and final suffix.

For Deye SUN hybrid systems, start with the full model on the inverter label. “Deye 12 kW” is incomplete: SG05LP3-EU-SM2, SG02LP1-EU-AM3-P and SG01HP3-EU-DM2 refer to different equipment. The manual cover must include your exact variant.

Keep a photograph of the label beside the saved manual and firmware record. If a search result has a similar name, compare its cover before using a menu illustration. This simple record prevents an attractive but unsuitable online setup from becoming your configuration.

What to check or record

1. Photograph the entire model code and serial label.
2. Match the manual cover and document revision.
3. Record MAIN/HMI versions before comparing menu screens.

The battery voltage class is a hardware requirement.

Deye low-voltage and high-voltage hybrids use different battery architectures. For example, the SG03LP1 specification lists a 40–60 V battery range, while SG01HP3-EU-DM2 specifies 160–700 V lithium batteries. These are examples for those families, not universal Deye ranges.

Matching nominal voltage alone is insufficient. A compatible installation also needs the correct battery arrangement, BMS communication and approved hardware. Treat an LV-to-HV change as a system redesign; a menu setting cannot convert one inverter into the other.

What to check or record

1. Check the exact inverter battery-voltage range.
2. Identify the complete battery system and controller.
3. Obtain the matching compatibility and installation documents.

Phase arrangement changes how loads and measurements must be planned.

In the cited European families, SG03LP1 is single phase and SG05LP3 is three phase. A three-phase system requires a phase-by-phase view of the installation. A large number on the front does not prove that one individual circuit can use all of that power.

Ask for a load schedule showing the largest appliances on each phase and which circuits receive backup. This is more useful than comparing total connected appliance wattage alone. An oven, heat pump or EV charger can make one phase the deciding constraint.

What to check or record

1. Confirm the actual supply and inverter phase arrangement.
2. Record the largest simultaneous loads per phase.
3. Check the exact model’s per-phase and total ratings.

Use the old settings as a record of intent, then validate every field.

SG04 and SG05 are family identifiers, not interchangeable configuration files. Deye publishes separate manuals for SG04LP3-EU and SG05LP3-EU-SM2. Hardware, connectors, limits and software features must be matched to the actual replacement unit.

Translate the old configuration into plain-language goals first: which loads should be supplied, whether export is allowed, and when stored energy should be used. Then map those goals to documented fields on the new unit. Copying every number can carry an old mistake into a new system.

What to check or record

1. Save photographs of the original settings.
2. Compare the exact new manual and battery integration.
3. Test the replacement’s behaviour after commissioning.

Document operating preferences; leave electrical design to the installer.

For Deye hybrid systems, useful owner checks include displayed time, operating mode, schedule, energy flows and alarm history. Installation, protective settings, wiring and electrical measurements need the qualified person responsible for the system.

A readable menu is not evidence that changing it is appropriate. Before altering a field, write down what result you expect and how you will recognise it. If the field changes grid protection, earthing, source switching or battery protection, resolve its design basis first.

What to check or record

1. Keep the original value and reason for each change.
2. Separate operating preferences from protective settings.
3. Use the installer’s handover record for electrical limits.

Record equipment, intended behaviour and proof that the system actually does it.

For any Deye installation, assemble an equipment list, a single-line drawing and a list of backed-up circuits. Add the full inverter, battery, meter and logger models, firmware versions and manuals used. A photograph of the home screen alone does not describe the installation.

Define observable outcomes: normal daytime operation, evening discharge, an allowed charging window and planned backup loads. Record readings during each test. This becomes a practical reference when a later software update or household change alters the behaviour.

What to check or record

1. Save the design and model/version list.
2. Capture settings before and after commissioning.
3. Keep dated results for the agreed operating scenarios.

A screenshot belongs to a particular product, firmware and interface.

Deye manuals cover individual product families, and feature availability can depend on firmware. The built-in display and Deye Cloud can present operating choices differently. Missing or renamed fields should be checked against the exact device instead of filled using a nearby-looking option.

Compare the purpose of the setting as well as its name. Keep a photograph of the complete screen so that checkboxes, units and neighbouring fields remain visible. A cropped number often hides the condition that makes it relevant.

What to check or record

1. Record model, MAIN/HMI and app/logger versions.
2. Compare the exact manual’s menu section.
3. Ask support to identify an unfamiliar field before changing it.

Begin with the installation’s load boundary and export policy.

On SG05LP3-EU-SM2, the work-mode menu distinguishes Selling First, Zero Export To Load and Zero Export To CT. The choice determines which loads the inverter tries to support and whether export is part of the strategy.

Sketch the grid connection, ordinary household circuits, backup circuits and measurement point. Mark where energy is allowed to flow. That drawing makes the mode choice understandable; selecting a mode merely because its name sounds economical does not.

What to check or record

1. Identify LOAD output and grid-side household circuits.
2. Confirm where whole-site power is measured.
3. Write down whether PV and battery export are permitted.

It targets the circuits connected to the backup LOAD output.

For SG04LP3-EU, Zero Export To Load serves the backup output; it does not extend self-consumption control to every grid-side household circuit. The separate Solar Sell option must also be considered when assessing export.

If an appliance is connected elsewhere in the installation, changing its schedule will not move it electrically onto the backup output. Ask the installer to label the circuit groups. This prevents a normal grid-side purchase from being mistaken for a defective inverter.

What to check or record

1. Locate the appliance on the circuit schedule.
2. Record the selected mode and Solar Sell state.
3. Compare LOAD power with actual backup appliances.

It uses external measurement to include grid-side home loads.

For SG05LP3-EU-SM2, Zero Export To CT can support backup circuits and home loads measured at the site boundary. The documented arrangement requires external CTs or a supported meter.

The measurement point is therefore part of the control system. If an outbuilding, charger or second solar inverter lies outside that boundary, the displayed balance may not represent the entire property. Have the drawing and sensor position checked before adjusting power limits.

What to check or record

1. Confirm all intended loads are inside the measurement boundary.
2. Verify the configured sensor or meter against installed hardware.
3. Test a known load and observe its measurement change.

Check Solar Sell, measurements and other generation sources.

On SG04LP3-EU, Solar Sell allows surplus PV export even when a zero-export mode is selected. Read the whole page of settings: the mode title alone does not describe the final behaviour.

Separate persistent export from a short response to a load change. Compare the inverter display with the site meter over the same interval and include other solar inverters. Changing multiple controls at once makes it harder to discover which setting or measurement caused the result.

What to check or record

1. Check Solar Sell and work mode together.
2. Record the duration and magnitude of export.
3. Include every generating device in the drawing.

It is a control offset, not a target for annual energy purchases.

The SG05LP3-EU-SM2 manual describes Zero-export Power as a small grid-import allowance used by the export controller. Use the exact manual and commissioned requirements to choose it; a value borrowed from another installation is not a verified setting for yours.

Judge the result with a repeatable test. Observe steady operation, switch a normal household load and examine how the system settles. A short spike and a continuing error are different observations. Keep both the time scale and units in your notes.

What to check or record

1. Record the current offset and units.
2. Verify correct site measurements before tuning.
3. Compare steady-state and load-change behaviour separately.

Sensor direction, phase association and sign conventions need checking.

On Deye systems using CTs, the installer must confirm sensor placement and orientation against the exact wiring diagram. A negative number is meaningful only after the display’s sign convention is understood; it is not a reason to reverse wiring by trial and error.

A useful diagnostic is a controlled, known load while other power flows are understood. The measured change should agree with that load’s location and direction. Photograph the reading, label the phase and record whether solar generation was present.

What to check or record

1. Ask the installer to verify the exact CT diagram.
2. Record before/after readings for a known load.
3. Keep phase labels and measurement signs in the evidence.

Total power and per-phase power answer different questions.

Deye three-phase models have model-specific unbalanced-output capability. The SG05LP3 14–20 kW datasheet specifies a per-phase limit alongside the total rating. “Unbalanced” does not mean unlimited output on one phase.

Inspect all phase readings simultaneously and locate the heavy appliance. A small total can hide a large individual phase flow. The response may involve load distribution or commissioning choices, not increasing the global power limit.

What to check or record

1. Capture L1, L2 and L3 simultaneously.
2. Check the exact model’s per-phase limit.
3. Have phase mapping and load distribution reviewed.

Support includes the exact meter, interface and configuration.

For SG04LP3-EU, the manual includes specific external-meter arrangements and a meter selection menu. A device being called a smart meter does not establish compatibility with that inverter.

Give the installer the complete meter designation and wiring instructions, including associated CTs. Confirm how it reports direction and phases and how the inverter receives its data. A display that powers up is not proof that the control measurements are valid.

What to check or record

1. Record complete meter and CT model numbers.
2. Match the manual’s connection and selection instructions.
3. Verify displayed power against a known load.

Look for a restriction on discharge before assuming a fault.

On the documented SG05LP3-EU-SM2 interface, grid-connected discharge depends on Time Of Use configuration. A high state of charge alone is not an instruction to discharge.

Build a snapshot: time, active row, requested behaviour, available battery power and actual load. Then identify which condition prevents the expected flow. This is more effective than lowering several limits together, particularly when backup reserve and daily self-consumption have different aims.

What to check or record

1. Check the active schedule and target.
2. Record actual load and allowed battery power.
3. Compare the observed result with the intended mode.

Energy needs somewhere to go.

In a Deye self-consumption installation, a full battery and a small load leave little local demand. If export is also restricted, reduced PV production can be the expected energy balance rather than a panel fault.

Compare generation, consumption, battery flow and export at the same time. If production rises when a useful load starts, that is evidence of a demand constraint. Use the solar troubleshooting section for a separate check of weather, strings and equipment faults.

What to check or record

1. Compare all power flows over the same interval.
2. Check whether charging and export have reached their limits.
3. Record the response when a useful load is switched on.

Power describes the rate; energy describes the accumulated amount.

For a Deye system, kW describes how quickly energy is produced, used or transferred at a moment. kWh describes an amount over time. A steady 2 kW load running for three hours uses 6 kWh; this arithmetic example ignores changes in the load.

Use power to examine simultaneous loads and equipment limits. Use energy to examine daily consumption and backup duration. A large battery capacity does not, on its own, establish how much instantaneous AC power the installed system can supply.

What to check or record

1. Check whether each number is W, kW, Wh or kWh.
2. Use a consistent interval when comparing energy totals.
3. Keep capacity and maximum power as separate entries.

It makes the configured charge and discharge periods active.

In the SG05LP3-EU-SM2 manual, the Time Of Use checkbox enables the schedule. Its time rows are not merely a chart showing what happened; they are instructions for the operating strategy.

Before enabling it, read every row through midnight. Describe each row: when it applies, whether grid charging is allowed and what reserve is intended. This catches unintended overnight behaviour that a screenshot of one daytime row can miss.

What to check or record

1. Confirm the Time Of Use checkbox.
2. Review the complete 24-hour sequence.
3. Reopen after saving and verify the active row.

It is a scheduled target, not the battery’s present reading.

The Deye SG04LP3-EU Time Of Use examples use the row’s battery target when deciding scheduled charging or discharge. Interpret it together with that row’s charging permission and overall work mode.

Distinguish three numbers in your notes: actual state of charge, target for the current period and energy wanted for an outage. If the target changes at a time boundary, the next action may change even though household consumption has not.

What to check or record

1. Identify the current period and target.
2. Record its grid-charging permission.
3. Compare readings across a schedule boundary.

Keep power limits and current limits separate.

The SG05LP3-EU-SM2 manual labels TOU Power as maximum permitted battery discharge power. Other charging limits are set elsewhere; check their units and effects separately.

A number in watts cannot be copied into a field in amperes. Treat every entry as a value plus unit plus purpose. When the result differs from your expectation, identify the active restriction instead of assuming that the largest number overrides the others.

What to check or record

1. Read the unit and exact manual definition.
2. Record charge and discharge limits separately.
3. Confirm actual power during the intended period.

Check the charging permission and active period.

Deye’s Cloud manual illustrates mode changes affecting both charging options and Time Of Use. Review the schedule with the associated battery charging settings, not in isolation.

Start with the clock and saved configuration, then compare actual charge with the intended target. Record alarms or an unavailable source. If a second controller manages the installation, confirm that it has not issued a newer command.

What to check or record

1. Verify clock, active period and charging permissions.
2. Compare actual charge with the target.
3. Read back settings and check for another controller.

Check day selection and the device clock.

The SG04LP3-EU manual includes weekday selection for Time Of Use. A correct series of periods may still be inactive on a day that is not selected.

Record the inverter’s displayed day and time rather than relying only on your phone. Check again after a clock change or service visit. If comparing app graphs with a tariff, make sure both refer to the same local interval.

What to check or record

1. Check every intended weekday.
2. Compare inverter time, app time and local time.
3. Observe a period boundary on an affected day.

A time schedule and a price optimiser are different controls.

The SG05LP1-EU-AM2-P datasheet advertises six charging/discharging periods. Fixed times do not, by themselves, demonstrate that future electricity prices are being fetched or optimised. Optional services must be checked for the actual device and region.

For additional energy management, establish who supplies prices, who writes settings and what happens if connectivity fails. Define desired behaviour independently of the app name: preserve backup reserve, respect site limits and apply the intended price periods.

Deye Cloud also documents Deye Copilot, which is separate from the inverter’s fixed schedule. Its setup includes a tariff plan, import/export permissions and an optimisation strategy. Check availability for your plant, equipment, account and region before relying on automatic tariff control. Agree which controller is responsible and record how to return to manual mode.

What to check or record

1. Identify fixed scheduling versus an external optimiser.
2. Check tariff interval, region and local time basis.
3. Document fallback behaviour if external control stops.

Begin with the loads and outage duration you want to cover.

For a Deye installation, reserve is an operating decision needing an energy budget. List essential appliances, estimate average demand and decide how long they should run. Then account for available usable energy and operating losses.

For example, 500 W sustained for four hours represents 2 kWh at the loads before losses. This is planning arithmetic, not a recommended percentage. Have the installer translate the requirement into appropriate settings for the actual battery system.

What to check or record

1. List essential loads and running hours.
2. Estimate energy before choosing a percentage.
3. Review reserve after measuring actual backup consumption.

Operating control does not replace electrical protection.

For SG02LP1-EU-AM2/AM3-P, the manual explains that grid peak shaving can be exceeded when available sources cannot meet the load. It is not an unconditional protective cutoff.

Have the installer coordinate settings with the supply, circuit protection and load-management design. Test ordinary peak loads and document what happens when battery support is unavailable. The fallback case matters as much as the sunny, fully charged case.

What to check or record

1. Record supply and protection ratings.
2. Check the exact peak-shaving limitations.
3. Test the agreed low-battery-support fallback.

Only designed backup circuits have a verified backup path.

Deye installation diagrams distinguish Backup Load from On-Grid Home Load. Covering a circuit through self-consumption while the grid is present does not prove that it will remain energised during an outage.

Ask for a labelled backup circuit schedule and supervised functional test. Include lighting, internet equipment and any appliance whose loss matters. Discovering a required socket is on the ordinary grid side during an outage is avoidable.

What to check or record

1. Obtain the backup circuit list.
2. Identify loads excluded from backup.
3. Have the installer perform a controlled outage test.

Use available energy and average load, then verify with a test.

For a Deye backup system, a first estimate is usable energy available to the loads divided by average load power. If 4 kWh is actually available at the loads and average demand is 1 kW, the idealised estimate is four hours.

Real appliances cycle, batteries have operating limits and the inverter consumes energy. Solar may help but is not guaranteed. Use this arithmetic to compare scenarios, then replace assumptions with observations from the installed system.

What to check or record

1. Use usable available energy, not only nameplate capacity.
2. Measure average backup demand.
3. Keep an estimate for little or no solar.

Starting demand can exceed a limit despite modest average power.

For Deye backup systems, total output, per-phase capability and the connected battery all matter. The SG05LP3 14–20 kW datasheet gives a per-phase ceiling as well as the system rating.

Record the appliance, other running loads and any alarm. An average graph can miss a brief starting event. The installer can use the appliance specifications and test results to decide whether sequencing, load selection or sizing must change.

What to check or record

1. Record the appliance and simultaneous loads.
2. Capture exact alarm and event time.
3. Compare starting demand with installed system limits.

Check the specification and configured backup delay.

For SG01HP3-EU-DM2, the manual describes a Backup Delay function and notes firmware dependence. This setting is separate from a datasheet claim about transfer performance.

If a computer or control device must ride through an interruption, verify the requirement against the complete installation. A successful light-bulb test does not establish every appliance’s tolerance. Record which devices restarted during the agreed test.

What to check or record

1. Check the exact backup specification.
2. Record any configured Backup Delay.
3. Test the actual sensitive equipment under supervision.

Battery-free operation and reliable backup are separate requirements.

Some Deye hybrid manuals include a No Batt configuration. Verify it for the exact family; its presence does not mean every operating mode behaves like a fully commissioned battery system.

Describe the requirement precisely: daytime solar with the grid, continued operation during an outage, or starting without AC supply. Ask the installer to confirm each case for the specific hardware and firmware. One successful daytime test does not prove the other cases.

What to check or record

1. Confirm battery-free support in the exact manual.
2. State grid-present and grid-absent requirements separately.
3. Document what was tested at handover.

Its selected function must match the connected equipment.

The SG02LP1-EU-AM2/AM3-P manual describes Generator Input, SmartLoad Output and Micro Inv Input uses. These are distinct functions; the enclosure label does not tell you which is configured.

Before connecting or repurposing equipment, have the installer compare the drawing with the port setting. Record intended behaviour with the grid present and absent. A software change cannot make an incompatible connection safe.

What to check or record

1. Label connected equipment and port function.
2. Check the GEN Port Use selection.
3. Review any changed use against the wiring design.

Separate the start signal, generator readiness and charging permission.

In SG04LP1-EU-SM1/SM2 documentation, the generator start interface is a control contact. The generator still needs compatible remote starting and its own working starting system.

Test in stages with the installer: confirm the generator can run, confirm the control request reaches it, then confirm accepted supply and charging. Missing charging does not automatically mean the start threshold is wrong.

What to check or record

1. Check generator readiness and remote-start compatibility.
2. Record start condition and signal state.
3. Verify accepted input and charging once running.

Connection location and outage control need a design review.

Deye SG01HP3-EU-DM2 supports AC coupling for retrofit applications. The existing inverter, connection point and backup architecture require compatibility review; sharing an AC voltage is not the complete test.

Draw where the existing inverter sits relative to GRID, LOAD and GEN. Document what should happen when the battery is full, demand is small and the grid fails. These conditions reveal whether the proposed system can manage surplus generation.

What to check or record

1. Identify the existing inverter and connection point.
2. Confirm supported surplus-generation control.
3. Test grid-connected and outage behaviour after installation.

Use a supported combination and complete expansion design.

Deye publishes parallel-operation limits by family. The SG05LP1-EU-AM2-P datasheet states up to 16 units; the cited SG05LP3 14–20 kW datasheet states up to 10. These limits do not approve a particular mixed-model combination.

Expansion changes protection, communications, measurement and backup design. Retain the original model and firmware record and obtain confirmation of the proposed combination before buying an additional unit. Matching the brand alone is insufficient.

What to check or record

1. List full existing and proposed models and versions.
2. Confirm the supported parallel arrangement.
3. Update the design and commissioning tests.

Gather the evidence that makes configuration values meaningful.

Use this worksheet for a Deye hybrid before changing its strategy. Identify the exact inverter and battery system. Add the meter, logger, existing solar inverter and generator, if present. Keep model names complete and store matching manuals.

Describe the actual installation in one drawing: grid entry, backup output, measurement point and every generating device. Do not substitute a generic brochure example for the installed arrangement.

Write operating goals as observable statements: stored solar after sunset, an agreed outage reserve, or grid charging during selected periods. Separate owner preferences from ratings and protective limits.

Ask the installer to mark the source of each value: equipment documentation, electrical design or owner preference. Keep unknown information visibly unresolved until checked.

After commissioning, reopen saved settings and retain dated test evidence. Record conditions and results so that later changes can be compared with known working behaviour.

Exact inverter variant

Where it is used

Nameplate and Device Info

What to enter or collect

Full SUN code, suffix and firmware.

Why it matters

Selects the correct manual and feature set.

System drawing

Where it is used

Installation record

What to enter or collect

GRID, LOAD, GEN, sources and measurement boundary.

Why it matters

Explains which equipment supplies each circuit.

Operating objective

Where it is used

Owner and installer agreement

What to enter or collect

Self-consumption, export, scheduled charging and backup needs.

Why it matters

Gives a reason for mode and schedule choices.

Verification record

Where it is used

Handover

What to enter or collect

Settings, test conditions, readings and alarms.

Why it matters

Makes later changes comparable.

What to check or record

1. 1. Photograph equipment labels and record versions.
2. 2. Obtain the installation drawing and backup circuit list.
3. 3. Document desired import, export, charging and reserve behaviour.
4. 4. Have the installer confirm ratings and compatibility.
5. 5. Save settings and perform agreed functional tests.
6. 6. Reopen settings and retain dated results.

A structured check for an already installed system.

Use this process for an installer-commissioned Deye hybrid with an export-control requirement. Define the point where import and export must be assessed. Draw every load and generating device relative to it.

Have sensor direction, phase association and meter compatibility verified before tuning controls. Compare readings during a known load change. An incorrect measurement cannot be repaired by choosing an unrelated power limit.

Review the selected mode and separate export permissions together. The SG04LP3-EU documentation distinguishes load-only and external-measurement arrangements. Use your own model’s instructions to map the intended result to fields.

Observe steady operation and a normal load change. Record simultaneous PV, battery, load and site-meter readings. Distinguish transient response from persistent export.

Keep the drawing, settings and results together. If the target is not met, these provide useful evidence for the installer. Wiring and protective settings are outside an owner-level measurement review.

What to check or record

1. 1. Draw the measurement boundary and all sources.
2. 2. Have sensor direction, phase mapping and configuration verified.
3. 3. Read the mode and separate export permissions.
4. 4. Record steady operation and a known load change.
5. 5. Compare simultaneous site-meter readings.
6. 6. Reopen settings and document discrepancies.

Translate the operating plan into a complete daily sequence.

Use this process for a Deye model with documented Time Of Use. Start on paper with periods for permitted grid charging, use of stored energy and the intended outage reserve.

Read each row as a complete instruction: time boundaries, target, power field and charging permission. Demonstration values do not describe your battery, tariff or required reserve.

Check the device clock and applicable weekdays. Establish which controller owns the schedule if external energy management also writes settings.

Save and reopen the configuration. In the first relevant period, record time, target, state of charge and power flows. Observe a boundary as well as a stable interval.

Review a representative day before changing the plan. Adjust one operating assumption at a time and retain previous values. Keep household requirements alongside any cost-saving objective.

What to check or record

1. 1. Write the operating plan and reserve requirement.
2. 2. Fill every period using the exact field definitions.
3. 3. Confirm permissions, clock and weekdays.
4. 4. Save, reopen and compare values.
5. 5. Observe an active period and next boundary.
6. 6. Review measured flows before adjusting.

Verify the circuits and appliances that matter before an outage.

For a Deye backup installation, list appliances that must remain available and the desired duration. Separate essential loads from loads that can wait. Include internet equipment and heating controls.

Obtain the actual backup circuit list and system power limits. Self-consumption coverage does not establish an outage supply path. Assess large loads against the exact inverter’s phase limits.

Agree on a supervised procedure covering grid loss, normal backup loading, a representative appliance start and grid restoration. Electrical isolation and protection checks remain the installer’s responsibility.

Record which devices stayed on or restarted, indicated power and alarms. Note initial charge and solar contribution so that results can be interpreted.

Use measurements to update circuit labels, reserve expectations and any load sequence. Retain the completed record to assess later equipment changes against the original requirement.

What to check or record

1. 1. Define essential appliances and duration.
2. 2. Confirm backup circuits and system limits.
3. 3. Agree on an installer-led outage/restoration test.
4. 4. Record device behaviour, power and alarms.
5. 5. Compare the result with the requirement.
6. 6. Keep the completed record with the configuration.

Match the complete battery system to the inverter’s battery voltage class and supported integration.

A SE-G5.1 Pro-B is a low-voltage battery. A BOS-G rack uses a series arrangement of modules and a high-voltage control box. Similar module labels do not make the completed systems interchangeable. The relevant number is the voltage range at the inverter’s battery terminals.

Build a compatibility record containing both full model numbers, battery controller, firmware and required communication method. This prevents an expensive mistake: choosing on kWh alone while overlooking voltage, permitted current or the missing control box. If a document covers a related suffix or another region, it is a lead for further checking, not approval for the installed combination.

What to check or record

1. Record inverter and battery nameplates.
2. Match the complete operating-voltage range, not only nominal voltage.
3. Confirm the exact combination with current integration documentation.

Energy capacity describes duration; output power is limited separately.

SE-G5.1 Pro-B is specified as 51.2 V and 100 Ah, giving 5.12 kWh nominal energy. That number is not a promise of constant AC output. Battery current, inverter capability, temperature and the permitted operating window determine how quickly energy can be used.

As a calculation example, 2 kW for 2 hours consumes 4 kWh before allowing for losses. Conversely, 100 A at 51.2 V equals 5.12 kW on the DC side; actual voltage varies and AC output is lower after conversion. Keep kW and kWh in separate columns when choosing equipment or diagnosing short runtime.

What to check or record

1. List continuous and peak power separately.
2. Use the actual bank voltage for current calculations.
3. Include reserve and conversion losses in runtime estimates.

Use the supported bank configuration, and distinguish the configured value from what the BMS reports.

For identical batteries connected in parallel, amp-hour capacity adds while nominal voltage stays the same. Three 100 Ah modules form a 300 Ah bank at their original voltage. This arithmetic does not establish that all three modules are actually connected, enabled or recognised.

Check physical quantity against the battery controller’s device list and inverter battery information. A manually entered capacity can look correct even when a communication link is missing. Do not multiply an individual module’s Ah by the number of series modules in an HV rack: series raises voltage, while the string Ah remains that of one module.

What to check or record

1. Write down the series and parallel arrangement.
2. Compare installed, enabled and recognised module counts.
3. Confirm whether the inverter field is user-entered or supplied by BMS.

The energy available to the home also depends on reserve, temperature, rate and conversion losses.

A datasheet’s usable DC energy is measured under stated test conditions. It is not the same measurement as energy recorded by the household AC meter. Deye documents may use different discharge windows between revisions, so compare the footnote as well as the headline number.

For planning, an illustrative 10 kWh bank used from 90% to 20% SOC exposes about 7 kWh before losses; this is arithmetic, not a recommended Deye setting. A fair capacity test must use a documented method and consistent starting and ending states. A cloudy day with loads running is not a controlled battery-capacity test.

What to check or record

1. Record whether the figure is nominal, usable DC or measured AC energy.
2. Include the chosen operating reserve.
3. Use the manufacturer’s test procedure for a warranty capacity claim.

The setting must fit the battery bank, inverter and complete DC circuit.

An inverter setting is an upper allowance, not a target that the system must reach. Start with the battery maker’s permitted continuous current for the installed arrangement; then consider inverter limits and the current rating of cables, terminals, disconnects and protection. The most restrictive applicable limit controls the design.

Do not copy the current from another owner’s screenshot. Even two installations using the same inverter can have different battery counts or cable arrangements. Ask the installer to record the reason for each limit and whether it applies to one module, one battery input or the combined bank. A BMS reduction during operation is a separate live condition to investigate.

What to check or record

1. Record charge and discharge limits independently.
2. Check the rating of the whole current path.
3. Confirm whether the number is per input or system-wide.

No. Peak values have a specified duration and operating conditions.

A brief surge rating and a continuous current rating answer different questions. The SE-F16 Max family’s documentation separates recommended, continuous and short-duration values. Setting a charger to a peak figure does not turn that peak into a sustained operating capability.

When a motor starts, ask whether its surge lasts longer than the permitted battery and inverter overload window. When charging, evaluate the steady current and thermal conditions. Repeated trips at the same demand are evidence to collect, not an invitation to increase protection settings. Your design should remain within the supported continuous envelope during ordinary use.

What to check or record

1. Read the duration and temperature attached to a peak value.
2. Check both battery and inverter overload limits.
3. Record the load that triggers a trip.

A communication problem or BMS limit should be diagnosed before changing the control method.

Lithium integration lets the supported battery communicate operating information to the inverter. A voltage-controlled mode is a different arrangement, with responsibility for charging limits placed elsewhere. Manufacturer-specific guides illustrate why the battery model and protocol matter; their numerical settings are not transferable to unrelated batteries.

If power increases after disabling managed control, that observation identifies a control difference. It does not prove that the higher power is safe. Capture the BMS current request, temperatures, alarm state and module count while the problem occurs. Resolve the cause with the relevant battery and inverter documentation instead of using a mode change as a permanent bypass.

What to check or record

1. Record the original battery mode before changing anything.
2. Capture live Li-BMS values and alarms.
3. Use voltage control only when the exact integration explicitly permits it.

The connector shape does not identify the electrical signals or protocol.

Deye battery documentation distinguishes the PCS communication port from inter-battery IN and OUT links. CAN and RS485 are different interfaces, even where a connector carries pins for both. The inverter’s selected protocol must agree with the battery, cable and port being used.

Treat every cable as a documented assembly with a device at each end. A network cable, an inverter-to-battery cable and a module-to-module cable can look identical while serving different functions. Plugging into an available RJ45 socket is not a meaningful compatibility test. Label cables by purpose before commissioning to make later troubleshooting clear.

What to check or record

1. Identify the port name at both ends.
2. Verify protocol and cable part number.
3. Keep Ethernet, BMS and parallel links clearly labelled.

Read the pin tables for both exact devices; there is no universal RJ45 recipe.

For the SE-F16 manual dated September 2026, the PCS table identifies CAN-H on pin 4 and CAN-L on pin 5, with RS485-A on pin 7 and RS485-B on pin 8. Its IN/OUT tables have different assignments. These are battery-side definitions for that document, not instructions for every Deye battery or inverter.

An installer must match signal names end to end using the connector orientation shown in the manuals. A pin number without a viewing direction is ambiguous. Use the supplied approved cable where applicable; have any replacement continuity-checked while disconnected. Do not experiment with live connector pins or assume that matching cable colours prove correct wiring.

What to check or record

1. Record the exact manual revision and connector view.
2. Compare signal names at the battery and inverter.
3. Use a documented cable and test it disconnected.

Power wiring and data communication are separate paths.

Voltage at the inverter shows that a DC potential is present; it does not demonstrate a working data link. In a supported managed installation, inspect the battery-information screen for coherent values such as SOC, current allowance and temperature. A static or blank screen needs further diagnosis.

Start with observations that do not disturb wiring: alarm indicators, selected mode, protocol, number of recognised modules and the time the problem began. Compare these with the approved commissioning record. If the issue followed a cable replacement or firmware change, tell support exactly what changed. Have the installer inspect physical connections under the documented shutdown procedure.

What to check or record

1. Photograph the battery-information screen.
2. Record mode, protocol and firmware versions.
3. Separate missing communication from a battery protection event.

Check the battery network rather than increasing capacity manually.

The inverter usually receives the bank’s information through the designated battery controller or master connection. A missing link between modules can leave a plausible-looking system view while reducing the resources actually available. Some Deye families use automatic networking; others have a different controller or addressing procedure.

Compare three records: how many modules are installed, how many report normal operation, and how many the battery controller recognises. Aggregate values alone can conceal a missing module. Do not assume the number of illuminated cabinets equals the number included in the bank’s control calculations. Use the model-specific connection drawing when tracing the communication chain.

What to check or record

1. Check module-level indicators and controller device count.
2. Record aggregate capacity and allowed current.
3. Use the exact family’s networking and addressing procedure.

Compare the source, timestamp and level of aggregation before deciding that a reading is wrong.

SOC is an estimate of remaining charge, not a direct energy-meter reading. A battery’s own display, an inverter screen and a cloud graph may describe a single module, a combined bank or a value sampled at another time. A difference can therefore be a reporting issue rather than immediate evidence of lost capacity.

Take simultaneous photographs or exported readings during a steady operating period. Note whether power is flowing and whether one display has stopped updating. If the bank SOC jumps, inspect module-level alarms and communication history. Avoid forcing a displayed percentage to 100% just to make two screens agree; that can hide the underlying problem.

What to check or record

1. Compare timestamps and live versus historical views.
2. Distinguish single-module SOC from bank SOC.
3. Capture a before-and-after timeline of sudden jumps.

A percentage alone does not specify energy or load.

The same displayed 100% can describe one small battery or a large bank. Runtime also changes with load, reserve, temperature and conversion losses. A connected system can reach its control endpoint while still providing a different usable window from the capacity-test conditions in the battery documentation.

Measure energy over a defined interval and record the average load. For example, a 1 kW load lasting 4 hours needs 4 kWh before losses. If runtime becomes shorter, first compare identical starting SOC, reserve and demand. Then inspect battery count and alarms. This makes a support report more useful than a single screenshot of a full battery.

What to check or record

1. Record start SOC, end SOC and delivered kWh.
2. Compare like-for-like loads and reserves.
3. Check that every intended module participated.

Available charging power can change as the battery approaches its permitted endpoint.

The battery’s permitted current is not necessarily constant throughout a charge. Deye battery specifications explicitly qualify current by SOC and temperature. A lower request near the upper end of the operating window can therefore be part of normal control rather than a solar fault.

Observe the trend instead of increasing the current setting immediately. Record charge power, BMS allowance, SOC and temperatures together. If charging stops repeatedly at an unexpected percentage, include alarms and individual-module information in the report. A full bank, a cold module and a missing communication link can produce superficially similar low-power symptoms but need different responses.

What to check or record

1. Compare the requested current with actual current.
2. Check temperature and alarm state.
3. Track behaviour across the final part of a normal charge.

Charging and discharging temperature ranges can differ.

For example, the SE-G5.1 Pro-B documentation lists charging from 0°C to 55°C and discharging from -20°C to 55°C. This is a model-specific example, not the temperature range for every Deye battery. A broad marketing phrase such as operation down to -20°C must not be read as permission to charge an unheated pack at that temperature.

Compare the battery’s own measured temperature with its charging specification, not only the room thermometer. A cold-soaked cabinet can remain cold after the room warms. Do not override a low-temperature block; correct the installation conditions or use the documented heating function of an appropriate variant.

What to check or record

1. Read separate charge and discharge temperature rows.
2. Record the BMS temperature at the time of refusal.
3. Wait for supported conditions before resuming charging.

Treat each suffix as a separate product specification.

The October 2026 EU brochure distinguishes SE-F16 Max from SE-F16 Max-H: the H version specifies a charging range down to -20°C with heating on, while the standard Max lists charging from 0°C. That distinction must not be transferred to a plain SE-F16, a Max-6 regional model or another series.

Record the complete label and obtain the matching regional manual before promising winter charging. A temperature figure does not explain activation conditions, power availability or heating behaviour on its own. Those details belong to the exact product’s operating instructions. If a seller’s description and the nameplate differ, resolve the discrepancy before changing settings.

What to check or record

1. Check the complete model suffix.
2. Verify heating availability and activation conditions.
3. Keep regional Max-6 documents separate from EU Max/Max-H documents.

The SE-F16 manual describes separate logo, LED and LCD versions.

The September 2026 SE-F16 manual identifies SE-F16-L, SE-F16-E and SE-F16-C by their front-panel arrangement. A guide showing an LCD error code is therefore not a literal screen-by-screen guide for every unit sold under the SE-F16 family name.

Use the variant-specific indicator table to interpret an alarm, then record the exact pattern or displayed code. A photograph is often clearer than saying that a light is red. Keep the display variation separate from unrelated assumptions about heating, enclosure protection or compatibility: one visible difference does not establish every internal specification.

What to check or record

1. Record L, E or C when present on the product record.
2. Use the corresponding indicator explanation.
3. Photograph the complete display and alarm pattern.

Expansion requires an approved compatibility and commissioning plan.

Deye publishes separate BOS-G expansion instructions, including region-specific versions. These consider manufacturing age, firmware, state matching and the system arrangement; they are not simply instructions to connect another module. The applicable limits may differ between adding modules within a string and adding a complete cluster.

Before ordering, give the installer the existing serial numbers, controller model, firmware and proposed new modules. Ask for the exact expansion document to be identified in the work plan. Do not use a published limit from a different region or generation to justify mixing equipment. Expansion changes both the electrical design and the bank’s configuration record.

What to check or record

1. Obtain approval for the exact old/new combination.
2. Identify in-string expansion versus an additional cluster.
3. Keep commissioning and post-expansion test records.

A similar family name is not evidence of interchangeable parts.

BOS-G and BOS-G Pro documentation lists different system components and controller names. The Pro brochure, for example, identifies BOS-G-Pack5.1 and BOS-G-PDU-2. Compatibility must be established for the complete assembly rather than inferred from a shared 5.12 kWh module energy.

Create a bill of materials that includes the rack, controller, modules, communication parts and power cables. Ask the supplier to confirm it as one supported configuration. This is particularly important when replacing a failed component: replacing like-for-like means matching the approved part and revision, not choosing the closest available name.

What to check or record

1. Record the exact module and PDU part numbers.
2. Use one approved system bill of materials.
3. Confirm replacement compatibility before installation.

No. Identify the protection event and its cause before recovery.

Battery alarms can refer to cell voltage, temperature, internal communication or other conditions. Raising a system voltage because the battery has stopped accepting charge can worsen the condition that caused protection. An inverter setting cannot repair a damaged cell or a failed sensor.

Record the first alarm, the operating state and any later secondary faults. Follow the model-specific recovery guidance with the installer or service team. A recurring alarm after a reset needs diagnosis. If the cabinet is damaged, leaking, producing smoke or unusually hot, stop using it and follow the site emergency procedure; do not open it for a customer-level inspection.

What to check or record

1. Capture the original alarm before clearing logs.
2. Report recent wiring, firmware or configuration changes.
3. Use only the documented recovery process.

Collect module electrical data, inverter input limits and the site’s temperature assumptions.

Deye’s string calculator asks for module Voc, Vmp, Isc, Imp and the temperature coefficient, alongside inverter voltage, current and MPPT limits. Panel wattage alone cannot answer how many modules belong in a string. The design must also reflect how strings are assigned to physical inputs and trackers.

Keep the calculation with the installation drawing. An installer should verify the proposed layout against the exact inverter datasheet, panel datasheet and applicable design rules. If panels are changed later, repeat the calculation: a newer panel with a similar watt rating may have substantially different voltage and current.

What to check or record

1. Record the exact panel and inverter models.
2. List series modules and parallel strings for each tracker.
3. Retain the cold-temperature voltage and current checks.

PV voltage rises as cells get colder; the absolute input limit must still be respected.

Open-circuit voltage is a different quantity from the voltage observed while the array is producing power. Series module voltages add. A string that appears comfortably within range on a warm afternoon can therefore approach a higher voltage during a cold start.

As an arithmetic example only, ten modules with a corrected cold Voc of 50 V each form a 500 V string. The permissible count must come from the actual module temperature coefficient and inverter limit. Do not treat inverter clipping as protection against excessive PV voltage: power limiting and maximum voltage are different constraints.

What to check or record

1. Use the module’s Voc temperature coefficient.
2. Apply the site design minimum temperature.
3. Check the absolute inverter PV-voltage limit independently of power sizing.

One describes starting behaviour; the other describes the tracking operating window.

Deye datasheets list startup voltage and MPPT range separately. Reaching the startup threshold does not guarantee that the array remains in a useful tracking range under load or at high panel temperature. The full-power voltage window may add another constraint.

If a system repeatedly wakes and sleeps at dawn, compare the voltage and power trend with the expected light level. If it fails during strong sunlight, investigate string design or faults rather than explaining everything as a startup issue. A single instantaneous voltage screenshot cannot establish performance across the day.

What to check or record

1. Read startup, MPPT and maximum voltage as separate limits.
2. Record time-of-day voltage and power trends.
3. Have the installer evaluate warm-weather operating voltage.

No. Physical string connectors and independent trackers are different counts.

Deye specifications separately state the number of MPP trackers and the string inputs assigned to each tracker. Some inputs share a tracker. Consequently, counting connectors on the enclosure is not enough to plan different roof sections or assess a current limit.

Mark each cable on the installation drawing with both its physical input and tracker. When comparing currents, confirm whether the displayed value and datasheet allowance refer to one connector or the combined tracker. This avoids interpreting a legitimate combined current as a fault or assuming that each socket receives a separate full allowance.

What to check or record

1. Read the tracker/input arrangement for the exact model.
2. Label every string by tracker.
3. Check combined current where strings share a tracker.

Plan roof groups using their electrical behaviour, orientation and shading.

Arrays facing different directions reach their best operating conditions at different times. Independent trackers can follow different groups independently; a shared tracker has one operating voltage for the connected group. The result depends on the actual module and string configuration rather than orientation alone.

Ask the designer to explain why each roof group is assigned to a tracker. Keep mismatched module types and unequal string lengths out of ad hoc changes. If shading is the problem, first identify its location and timing. An optimizer is a specific engineered component with compatibility requirements, not a universal repair for an unsuitable string layout.

What to check or record

1. Record orientation, tilt and string length per roof group.
2. Compare same-time power only for comparable arrays.
3. Confirm any optimizer design with its own documentation.

A power plateau can reflect an inverter or system limit rather than failed panels.

Panel nameplate power is measured under defined test conditions. An installed system also has inverter conversion limits, PV input limits and possible export or battery limits. Adding module wattages therefore does not predict the maximum AC power shown on a screen.

Compare the plateau with the relevant limit and record battery SOC, load and export at the same moment. A stable plateau at an identifiable limit points to curtailment or clipping; an abrupt unexplained reduction with an alarm needs a different investigation. Do not increase voltage or current limits merely to remove a flat section from the graph.

What to check or record

1. Compare DC PV power and AC output separately.
2. Record the operating limit active at the plateau.
3. Check for alarms and thermal conditions.

Start with conditions and comparable measurements before blaming the inverter.

Deye’s PV FAQ identifies weather, shade, module orientation and temperature among the contributors to reduced generation. Bright sunshine does not mean cool panels or standard test conditions. Partial shading can also affect an array more than its small shaded area suggests.

Compare similar dates, weather and operating conditions. Record each tracker’s voltage, current and power, then note any export restriction or full battery. If one comparable string suddenly diverges from the others, give that evidence to the installer. Electrical measurements and connector inspection should be performed with the appropriate isolation and test procedure.

What to check or record

1. Photograph shading at the time output falls.
2. Compare tracker readings and historical trends.
3. Check whether power has somewhere to go.

Yes, if the system has no permitted destination for the available energy.

Power must go to a load, a battery or an allowed export path. When the battery cannot accept more and export is restricted, reducing PV harvest can be the expected result. The panels’ potential production and the power actually requested by the system are different quantities.

To interpret a low-PV period, view the whole power-flow picture at the same timestamp. If normal household demand rises and PV then rises with it, that supports a demand-limited explanation. It does not prove every string is healthy; retain tracker comparisons and alarms when diagnosing an unexplained change.

What to check or record

1. Record load, SOC, charge allowance and export together.
2. Check the selected export strategy.
3. Compare behaviour when ordinary demand changes.

Voltage alone does not demonstrate useful current or available power.

Electrical power is voltage multiplied by current. An illuminated string can show voltage while producing very little current in weak light, or while the system is limiting harvest. For example, 300 V at 0.1 A is only 30 W; the voltage figure can look substantial while power remains small.

Record voltage, current and watts together. Distinguish dawn or cloud conditions from a persistent failure in strong sunlight. If the inverter reports an input fault, pass the exact code and string layout to the installer. Do not disconnect PV plugs under load to experiment: the measurement question should be resolved through the approved test procedure.

What to check or record

1. Compare V, A and W at the same timestamp.
2. Note weather and operating limits.
3. Escalate persistent one-string differences with the installation drawing.

Treat it as an electrical fault requiring diagnosis, especially if it follows rain.

The SG04LP3 manual distinguishes leakage-current and insulation faults. Possible causes must be investigated on the actual installation; the code alone cannot identify a specific damaged panel or connector. Wet-weather recurrence is useful evidence, but it is not proof of a harmless moisture effect.

Record the exact code, time, weather and which inputs were operating. Keep the installation available for qualified inspection. Do not defeat protective earth, repeatedly reset the inverter to keep it running, or perform insulation tests with electronics still connected contrary to their instructions. The installer should choose the correct test method for the complete system.

What to check or record

1. Save the alarm history and weather timeline.
2. Report any recent roof or cable work.
3. Have the installer investigate before returning a recurring fault to service.

Heat and airflow must be assessed against operating load, ambient conditions and alarms.

The SG04LP3 specification describes active cooling and temperature-dependent derating. A warm enclosure or fan operation can accompany normal conversion losses. A falling power limit at high temperature may therefore be protective behaviour rather than an arbitrary setting change.

Look for a change from the installation’s usual behaviour. Record room temperature, demand, alarm history and blocked airflow without touching hot surfaces or opening the unit. Do not enclose the inverter for noise reduction without a thermal design review. If there is a burning smell, visible damage or repeated thermal alarms, stop normal operation and seek service.

What to check or record

1. Check that prescribed ventilation space remains clear.
2. Compare fan behaviour with load and ambient temperature.
3. Record alarms rather than judging by touch.

No. Enclosure protection and installation conditions vary by exact battery.

SE-G5.1 Pro-B is listed with IP20, while the SE-F16 Max/Max-H brochure specifies IP65. Those ratings do not make installation guidance interchangeable. The location also has to satisfy temperature, humidity, sunlight, flood exposure, structural support and access requirements.

Assess the inverter and battery separately: a weather-resistant inverter does not make an adjacent indoor battery weather-resistant. An improvised box can introduce condensation or overheating. Before moving equipment, ask the installer to confirm the complete location against both manuals and the site’s requirements.

What to check or record

1. Read the exact product’s enclosure rating.
2. Check temperature and condensation exposure.
3. Confirm location and structural support before mounting.

They must be designed together for the actual DC circuit.

The relevant Deye inverter manual provides model-specific connection requirements, but an installation also has cable length, routing, ambient temperature and fault-current considerations. Battery protection is not simply a fuse selected to match the inverter’s marketing wattage. A DC device must be suitable for the circuit’s voltage and interruption duty.

Have the installer document cable size, conductor arrangement, termination method, protection and isolation. Higher current produces greater cable heating and voltage drop, so a cable that fits a terminal is not automatically adequate. Never replace a fuse with a larger one to stop nuisance trips without diagnosing why it operates.

What to check or record

1. Keep the DC protection schedule with the system drawing.
2. Use approved terminations and specified tightening procedure.
3. Recheck the design when adding batteries or increasing current.

Follow the exact battery’s maintenance and storage schedule, including charge-state checks.

Low self-discharge does not mean indefinite storage without attention. The RW-M6.1-B manual includes periodic storage charging requirements and prompt recharge after deep discharge. A switched-off installation still needs a documented plan if it will remain unused for months.

For normal ownership, keep ventilation and access clear, observe external damage or alarms, and retain the system log. Cleaning, electrical inspection and maintenance must follow the relevant isolation instructions. Record storage start date, SOC and the next inspection date; do not depend on a cloud notification from equipment that has been disconnected from power or internet.

What to check or record

1. Use the exact model’s storage temperature and charging schedule.
2. Record SOC and inspection dates.
3. Report damage, leakage or abnormal indicators promptly.

No. A system can have several independent energy sources.

Grid supply, PV strings, batteries and generators can energise different parts of the installation. The inverter’s front-panel button is not proof of isolation. Deye manuals require the relevant AC and DC isolation procedures and waiting periods before maintenance.

The installation should have a labelled shutdown plan showing every source and the equipment it supplies. A qualified person must verify the electrical state before work. For an owner, the useful preparation is to know the emergency isolation procedure and support contact, rather than improvising a switch sequence from a different Deye model.

What to check or record

1. Keep the installation-specific shutdown instructions accessible.
2. Identify all AC and DC sources.
3. Leave verification of isolation and internal work to qualified personnel.

Use this sequence to organise commissioning evidence before entering battery settings.

First identify the system. Record inverter model and firmware, battery model and region, module count, controller and connection arrangement. Include the serial numbers in a private service record rather than a public screenshot. Select the exact manual and approved integration document for that combination.

Next make a settings worksheet. Separate fixed equipment facts, installer-designed limits and owner preferences. Capacity is a system fact; permitted DC current depends on the equipment and installation; the backup reserve reflects an operating preference within supported limits. This distinction makes it clear who can approve each value.

Have the installer complete physical and protective checks using the applicable documents. For a managed battery, confirm that the chosen interface, protocol and communication cable match both devices. The user-facing check is the resulting battery information: coherent SOC, temperatures, current allowances and the intended module count.

Observe normal operation after the settings are saved. Record one ordinary charging period and one ordinary discharge period, including power, SOC, alarms and controller limits. Reopen the settings to verify persistence. A quiet display with no alarm is useful, but it does not by itself prove that every module or backup circuit was commissioned.

Complete the handover with the configuration record, shutdown instructions, manual revisions, service contact and a list of the tests performed. If a value is unknown, record it as unknown with an owner for resolution; do not fill the gap with a forum default.

What to check or record

1. Identify the exact models and supported integration.
2. Complete capacity, current, communication and reserve fields with their source.
3. Have the installer verify wiring and protection.
4. Confirm live BMS information and module recognition.
5. Reopen saved settings and record ordinary charge/discharge behaviour.
6. Retain the completed commissioning and shutdown record.

Build a short evidence record that separates weather, design, control limits and electrical faults.

Begin with the symptom: no generation, consistently low generation, one weak tracker, a midday plateau, or a sudden drop. Write down when it started and whether anything changed. A new alarm after roof work deserves a different response from a low-yield winter day.

Collect one aligned set of readings: PV voltage, current and power by tracker; battery SOC and charge allowance; household load; grid import or export; and inverter temperature or alarms where available. Use matching timestamps. Cloud graphs can average values, so preserve a local display reading when an event is brief.

Compare the PV design record with the exact panel and inverter data. The installer should confirm string length, tracker allocation, corrected cold Voc, operating voltage and current limits. Deye’s calculator is useful for collecting the necessary inputs, but its result is not a substitute for a complete site design.

Look for an explanatory pattern. If production increases when normal load increases with a full battery and restricted export, a system control limit is plausible. If one comparable string stays weak under similar light, or an insulation fault appears after rain, electrical inspection becomes more important. Keep these as diagnostic hypotheses until tested.

Send the installer the concise evidence bundle and change only the settings supported by the diagnosis. Have physical PV work and electrical tests performed under the documented isolation procedure. After a correction, compare the same readings under similar conditions and keep the before-and-after record.

What to check or record

1. Describe the symptom and its start date.
2. Capture aligned tracker and system readings.
3. Compare against the exact array design.
4. Separate expected limiting from alarms or persistent imbalance.
5. Have the installer test the suspected cause.
6. Verify the result under comparable conditions.

Check compatibility, architecture and commissioning requirements as one project.

List the existing equipment and the proposed addition separately. Include every battery module, controller, inverter input and relevant firmware version. Record whether the work adds parallel LV modules, modules within an HV string, or an entire HV cluster. Those are different engineering changes.

Ask the supplier or installer to identify the applicable manufacturer expansion document. Deye’s BOS-G guidance includes checks that depend on region, module age and expansion method. Keep the document revision and written compatibility confirmation with the order so that a similar-looking replacement is not substituted unnoticed.

Reassess the whole installation. Extra energy capacity may improve runtime without increasing permitted inverter output. Extra battery current capability is only useful if the inverter, cables, busbars, protection and control arrangement support it. Conversely, a larger bank can change fault-current and isolation requirements even when the desired output remains unchanged.

Have the installer plan firmware alignment, state matching, wiring, communication and commissioning in the order required by the exact system. This page intentionally does not give a generic live connection sequence. A series HV rack and a parallel LV bank require different procedures, and the battery manual may require service-team involvement.

After expansion, verify the recognised module count and aggregate values, save the revised settings and run the documented functional checks. Replace the old system drawing and emergency instructions with the completed version. Retain both versions so that later troubleshooting can distinguish pre-expansion and post-expansion behaviour.

What to check or record

1. Define exactly what is being added.
2. Obtain the correct expansion procedure and compatibility confirmation.
3. Recheck current paths, protection and isolation design.
4. Commission using the exact battery-family procedure.
5. Verify recognised capacity and normal operation.
6. Update drawings, settings and service records.

Use the platform specified for the installed logger and inverter, and preserve access to the existing plant.

Deye equipment has been supplied with different monitoring arrangements. Deye publishes both Deye Cloud documentation and SOLARMAN logger guides. The Deye name on the inverter therefore does not, by itself, tell you which app is already serving the installation.

Start with the logger label, its manual and the installer’s handover. Confirm the active platform before creating accounts or attempting migration. A different app is not a firmware upgrade, and adding an account does not automatically transfer device ownership, historical records or control permissions.

What to check or record

1. Record logger model, serial number, app and existing plant name.
2. Confirm which account owns the plant and which platform is supported.
3. Keep original access until any supported migration and its data have been verified.

Check the account, data centre, selected plant and permissions before assuming a logger failure.

Deye Cloud registration includes a data-centre selection. Owner and installer may also use different personal or business contexts. A successful login proves that the account exists; it does not prove access to the expected plant.

Compare the current account with the handover record and any invitation. If the plant is visible to the owner but not another user, investigate authorization first. Avoid creating repeated replacement plants: that makes later ownership and data troubleshooting harder.

What to check or record

1. Check the exact sign-in identity and data-centre selection.
2. Confirm the plant name and owner’s account.
3. Have the owner verify intended access rather than sharing their password.

Use the identifier requested by the screen; logger and inverter serial numbers are different.

The Deye-hosted SOLARMAN guide adds the logger using the number on its body or packaging. The inverter can have another serial number, and the battery another again. Entering a correct number in the wrong device field can still fail.

Label these separately in the system record. For support, provide the logger number together with the inverter model and serial so the data path can be traced. Keep full identifiers out of public screenshots when they are not needed.

What to check or record

1. Read whether the screen requests a logger, inverter or battery identifier.
2. Scan the matching label and compare the text with the printed number.
3. Keep a private label photo for support and warranty records.

The phone, logger and router each need to complete their own part of setup.

For the SOLARMAN Wi-Fi workflow, the phone joins the site network, then temporarily connects to the logger’s AP network during configuration. Internet access on the phone does not prove that the logger has received the correct network details. Follow the prompts through verification.

Stay close during onboarding. Check the SSID, supported band and app permissions. Keep any error number: SOLARMAN distinguishes Bluetooth authorization, location permission, password and communication failures. They require different fixes.

What to check or record

1. Confirm the selected SSID and supported Wi-Fi band.
2. Allow permissions requested for the documented setup method.
3. Record the failed step and error before trying another change.

Follow the exact logger specification; a blanket rule for every generation is inaccurate.

Deye Cloud’s documented onboarding uses a 2.4 GHz network. However, SOLARMAN’s current logger FAQ identifies LSW-4 as supporting 5 GHz. Advice for an older stick should not automatically be applied to another generation.

Wi-Fi security also differs. SOLARMAN lists LSW-3/MW-3 as WPA2-capable but not WPA3-capable; LSW-4/MW-4 and LSW-6/MW-6 support both. If an older logger stops connecting after a router change, check compatibility rather than weakening every network.

What to check or record

1. Read the full logger model and suffix.
2. Check band and WPA security support in its documentation.
3. Use a compatible secured SSID and verify connection.

They identify different communication links; use the exact logger’s indicator table.

On the DL1000B-ETH guide, NET concerns cloud connection and COM concerns communication with the connected device. A steady blue NET with a failed COM link means that internet access has not completed inverter communication.

Older SOLARMAN sticks use another indicator scheme, including READY on some models. Do not diagnose a DL1000B using an old green-light table. Record each label, colour and flash pattern after startup, then compare it with the matching guide.

What to check or record

1. Photograph the logger model and indicator labels.
2. Record NET and COM separately, including flashing.
3. Allow the documented startup wait before interpreting a persistent fault.

An offline cloud device can be a communication problem while the inverter continues supplying power.

Compare the cloud timestamp with the inverter’s local screen. A stale dashboard does not itself establish loss of power conversion. The chain includes inverter-to-logger communication, router access, internet access and the cloud service.

SOLARMAN’s offline guide checks network conditions and allows time after configuration. Our diagnostic approach identifies the broken link before resetting: note whether the inverter, logger or whole plant is offline, and whether the site network still has internet access.

What to check or record

1. Record last update and current local inverter status.
2. Check logger indicators and router connectivity without opening electrical equipment.
3. Reconfigure the affected communication link using its guide; preserve evidence first.

Cloud access and communication with the inverter are separate checks.

A logger can contact the platform without receiving a valid inverter response. SOLARMAN lists address, baud rate, connection and logger compatibility among checks. Its address-1 instruction belongs to the supported logger arrangement; it is not permission to give every device in a parallel network the same address.

Give the installer the exact logger/inverter pair and present communication settings. Physical reseating must follow shutdown and removal instructions. Blind address changes, another RJ45 socket or an arbitrary cable can introduce another fault.

What to check or record

1. Compare local operation with logger and inverter status in the device list.
2. Have the installer check the documented port, rate and addressing.
3. Use a supported substitution test if needed and record which component the fault follows.

Cloud displays are sampled and delayed; compare timestamps with live readings.

SOLARMAN describes periodic uploads and dashboard processing. Its updated dashboard documentation says some fields appear within 60 seconds after upload, while its device upload example is every five minutes. This is not a universal real-time guarantee.

A short kettle or compressor event may appear differently on a sampled chart. Compare the same time window rather than a live value with an older cloud point. For fast commissioning checks, use suitable local measurements; the dashboard is useful for longer trends.

What to check or record

1. Read last-update time before comparing power.
2. Compare sustained operation over several updates.
3. Keep sampling delay separate from control response or backup transfer time.

Monitoring access and permission to change settings are different.

SOLARMAN states that a missing Remote Control button can mean the account lacks device-control permission. The installer or dealer is the first contact. Visibility of graphs does not prove that every control should be available.

Ask for the access needed for the task and identify the parameter you intend to change. A permission issue is not solved with another user’s raw commands or credentials. When access is granted, read the current setting and document the intended value.

What to check or record

1. Check account role and the correct device.
2. Confirm whether remote control is supported and authorized.
3. After an approved change, verify the value read back.

Read retrieves present inverter values and avoids overwriting them with stale form contents.

Deye’s remote-control guide requires Read before configuring several modules, including System Work Mode and SmartLoad. A form left open while someone changes settings locally can be outdated. Read the module again before editing.

After sending a change, inspect the control log and read values back. A sent-command notification does not prove the inverter retained and applied the setting. Deye reserves customized commands for maintenance personnel and developers; ordinary users should use supported parameter screens.

What to check or record

1. Read the module and save a before-change record.
2. Change only the intended field and send the documented command.
3. Check the result, read back and confirm actual behaviour.

Use plant authorization and an appropriate role instead of sharing your password.

Deye Cloud provides plant access management with viewing and management roles; exact options depend on account context. SOLARMAN supports giving other accounts access to an existing plant. This keeps each person’s account separate.

Agree whether the installer needs readings only or permission to change settings. Verify the recipient and review temporary access when work is complete. Keep an appropriate owner account under the customer’s control.

What to check or record

1. Verify the exact recipient account.
2. Select the minimum role needed for the agreed task.
3. Review access at handover or when changing maintenance provider.

Resolve existing ownership or binding rather than repeatedly resetting the logger.

SOLARMAN directs the plant creator to manage unbinding. If you are not the creator, contact them. If the previous plant cannot be identified, support uses the serial number and binding-error screenshot to investigate.

A Wi-Fi factory reset handles local network configuration; it is not an ownership-transfer procedure. For used equipment, keep proof of purchase and ask the seller to complete the legitimate transfer. Check history and access before deleting a working plant.

What to check or record

1. Record the binding message and serial privately.
2. Contact the current creator or platform support.
3. Verify owner access and historical records after transfer.

Update the logger’s network configuration and verify its new connection.

In the SOLARMAN AP workflow, the phone connects to the logger network and runs its setup wizard to select the site SSID and new password. The label and matching manual identify access details. Keep the AP password separate from the router password.

After configuration, confirm that the logger receives a network address and reconnects to the server. Reopening the app cannot repair an old stored Wi-Fi password. Do not delete the plant merely because the network changed.

What to check or record

1. Use the exact logger’s supported configuration method.
2. Select the new compatible SSID and current credentials.
3. Check connection and a fresh timestamp in the original plant.

A working cable does not establish that logger addressing and access are correct.

SOLARMAN’s Ethernet troubleshooting checks whether a logger retains a static address and whether the network supplies an address through DHCP. A laptop may receive working settings while the logger holds settings from another installation.

Have the network administrator compare addressing and access rules with the intended network. Record settings before a reset. Use the designated Ethernet connector; similarly shaped inverter ports can carry other communication signals.

What to check or record

1. Confirm logger model and correct physical port.
2. Check address assignment and the router client list.
3. Verify server connection and subsequent uploaded readings.

Local access depends on hardware and its supported connection method.

SOLARMAN explains that Local Mode requires Bluetooth or a local access point. A 4G device without Bluetooth and without an AP cannot offer that discovery path. Failure to find it locally is not proof of a broken logger.

Check the connection method before buying an accessory or resetting equipment. Local viewing, cloud monitoring and remote control are separate capabilities. Availability of one does not establish that all three work with the installed combination.

What to check or record

1. Identify Bluetooth, Wi-Fi AP, Ethernet or cellular capability.
2. Use the app mode documented for that hardware.
3. Ask for the supported diagnostic route if no local wireless mode exists.

Compare device data and plant data sources before changing electrical settings.

SOLARMAN distinguishes device readings from the calculated plant overview. Its battery-data guidance recommends comparing portal and machine, then checking the data source when they disagree. A missing diagram element does not prove the battery is disconnected.

Our comparison uses three levels: inverter screen, inverter device details and plant dashboard. If the first two agree but the overview differs, investigate presentation and aggregation. If the inverter itself lacks battery data, investigate the underlying communication with the installer.

What to check or record

1. Compare the same variable and time on all three views.
2. Check plant type and sources against the actual topology.
3. Keep before/after screenshots of dashboard configuration changes.

A plant summary may aggregate devices instead of showing one battery’s value.

SOLARMAN says plant SOC comes from the average SOC of online devices. Its device guidance explains that SOC is received from the inverter. Compare individual device records before treating a difference as battery-calibration trouble.

For several inverters, record which are online and what the screen represents. An average of percentages is not automatically remaining usable energy for unequal banks. Use documented battery information for capacity and reserve decisions.

What to check or record

1. Check device SOC and timestamps individually.
2. Identify offline devices or a changed device list.
3. Do not adjust charging limits simply to match a dashboard average.

They may use different boundaries, periods and accumulation methods.

SOLARMAN can calculate cumulative generation from equipment counters or summed plant daily records. Changing the basis can change the displayed number without changing generation. Record the method before comparing totals.

A practical reconciliation separates PV, battery charge/discharge, consumption and grid import/export. The utility meter measures at the supply boundary; the inverter may report another boundary. Compare matching dates and units, allowing for gaps and conversion losses before adjusting a sensor.

What to check or record

1. Write down the definition and time range of each quantity.
2. Compare complete daily kWh records, not instantaneous kW.
3. Check calculation method, missing days and measurement boundary.

Check cloud time zone and the inverter clock separately.

SOLARMAN provides the plant creator a Timezone setting under home/plant settings. A wrong zone makes cloud charts difficult to compare with local observations. Users without editing permission need the creator to correct it.

Record a recognizable event with local time and compare the inverter clock and chart timestamp. Correcting cloud time zone should not be assumed to correct the inverter’s time-of-use clock. Verify both after commissioning and daylight-saving changes.

What to check or record

1. Record the local zone and cloud setting.
2. Compare the inverter clock with a reliable local clock.
3. Check the next schedule transition and daily chart boundary.

Identify display convention, data source and physical measurement as separate possibilities.

SOLARMAN documents a convention where a negative load appears as an absolute number with a reversed flow arrow. Read direction and label together. A positive-looking number alone cannot establish power-flow direction.

If the local inverter also reports implausible flow, ask the installer to verify CT/meter orientation, phase mapping and position against the exact diagram. If only the cloud overview differs, investigate its data source first. Do not reverse a CT or alter its ratio merely to make one screen look plausible.

What to check or record

1. Capture number, arrow, label and timestamp together.
2. Compare local grid power and device data during a stable known load.
3. Have physical metering checked against the exact installation drawing.

Use the supported export and retain the meaning of each column.

SOLARMAN offers plant and device-data export through its web services. Its Business help states that report export requires the Business web portal rather than the app. Columns and date ranges depend on platform and account.

Export normal operation before the event, the event and recovery. Keep timestamps, units, identity and selected filters with the file. An annotated screenshot helps, but an export allows PV, grid, battery and load to be compared on one timeline.

What to check or record

1. Choose the correct plant/device and incident period.
2. Retain original headers, units and time zone.
3. Share privately with the installer and a concise symptom description.

Use firmware approved for exact hardware through the installer or Deye support.

SOLARMAN notes that inverter upgrade permission depends on the manufacturer. Another owner’s version number does not establish compatibility with your model, regional variant, control board or battery integration.

Record existing inverter and logger versions and the problem being addressed. Ask for the intended version and settings to check afterwards. Maintain the conditions required by the manufacturer’s update procedure, then verify operation and saved settings.

What to check or record

1. Provide model, serial and current versions.
2. Obtain the approved update route and reason.
3. Recheck charging, metering, schedules, alarms and monitoring afterwards.

Use the fault table for the complete inverter model.

For the linked SUN-7–10K-SG05LP1-EU-SM2 manual, F35 identifies absent AC grid and F56 identifies low DC bus voltage. These descriptions guide investigation; they do not establish that a component needs replacement.

Record message, time and operating conditions. Compare grid availability and battery status locally. Ask the installer to investigate recurring faults using that model’s procedure; do not defeat protection settings.

What to check or record

1. Check model and matching fault table.
2. Save the first fault and nearby events.
3. Escalate recurring faults with local readings and battery status.

Check every unit in the group.

The linked SUN-7–10K-SG05LP1-EU-SM2 manual describes F41 as parallel-system stop and notes that an off unit can trigger it on other units. The first stopped unit may contain the earlier useful fault.

Record each unit’s status and event time. Have the installer check the approved parallel design and communication. Do not change roles or restart units in random order.

What to check or record

1. Record all inverter states.
2. Find the earliest event.
3. Use the exact-model recovery procedure.

Check platform notification choices and the phone or email destination.

Deye Cloud includes message-centre notification settings. SOLARMAN also offers alert delivery as a platform service. An alarm in history does not prove that push messages or email were enabled for the right recipient.

At handover, review the channels the customer uses and verify them with an available platform test or harmless documented notification. Avoid deliberately causing an electrical fault. Delivery of an alert is separate from recovery of the equipment.

What to check or record

1. Review notification settings and destination.
2. Check phone permissions and email filtering.
3. Verify delivery and keep the escalation contact available.

Verify actual records; do not assume every gap can be reconstructed.

SOLARMAN’s offline documentation addresses restoring communication, while platform services expose recorded data. Neither is a universal promise that every logger retains and re-uploads each missing interval.

After reconnection, compare device and plant history. If a gap remains, record its start/end and ask support whether backfill is supported for that hardware and failure. Do not fill missing values with zero: unknown production differs from measured zero.

What to check or record

1. Record the outage window and last successful timestamp.
2. Check whether device records return after reconnection.
3. Label unresolved gaps clearly in analysis.

Preserve the existing plant until support confirms deletion is necessary.

SOLARMAN says a deleted plant cannot be recovered as that plant, although device history may remain visible in inverter details. Creating a new plant is not equivalent to refreshing the app.

Before structural changes, record ownership, sharing, data sources and reports. Prefer the targeted fix: network configuration, access or data-source correction. If support requires recreation, verify the effect on history and associations first.

What to check or record

1. Export records and record access/settings before approved deletion.
2. Resolve network or permission issues at their own layer.
3. After recreation, check history and intended users.

Confirm a supported interface and coordinate all writers before enabling automation.

SOLARMAN provides an API access process and distinguishes data access from control permission. An API account or readable sensor does not prove arbitrary writes are supported. Use applicable integration documentation and keep credentials private.

Start with observation and compare values locally, then enable only understood controls. Two controllers overwriting the same schedule or mode can create confusing behaviour. Record who controls each setting and how to restore the agreed configuration.

What to check or record

1. Confirm protocol, model, access role and rate limits.
2. Validate read-only data before any writes.
3. Document control ownership, logs and disable/restore procedure.

Provide an equipment record and short timeline, not only a cropped alarm number.

For inverter problems, SOLARMAN directs users to the installer or distributor. NKON’s practical support record should connect the exact product to the symptom: model and serial, firmware, battery/logger models, operating mode and event time.

Add local photos, timestamped cloud screenshots, the first fault and recent changes. Explain what still works and whether the symptom repeats. Exclude passwords and API secrets; support can request an appropriate access invitation if needed.

What to check or record

1. Record model, serial, firmware and topology.
2. Include the timeline, local readings and exported data.
3. List attempted changes and results; retain original configuration.

Handover is complete when the customer can see fresh data from the intended inverter, not merely when an app accepts a QR code.

Prepare the equipment record: inverter and logger models, separate serial numbers, supported app and intended owner. Use the official app instructions for that logger. Keep customer and installer accounts separate.

Create or select the right plant. In Deye Cloud’s Wi-Fi method, select the logger configuration flow, supply site network details, connect to its indicated AP when prompted and return to the app. Bluetooth equipment may offer another discovery route; follow the matching guide.

Complete verification. A phone connected to the AP is an intermediate state. Confirm logger-to-router, cloud and inverter communication. For Ethernet, verify addressing and cloud access on that interface.

Compare a current inverter reading with the device screen after allowing upload delay. Check that the plant overview uses the right devices, time zone and system type. This practical acceptance sequence supplements electrical commissioning.

Record the successful timestamp and roles. Show the customer where to find device data and alarm history, and how to reconnect after a router change without deleting the plant.

What to check or record

1. Identify the supported logger/platform pair and owner.
2. Add the correct serial to the correct plant.
3. Complete the hardware’s network setup.
4. Verify cloud and inverter communication separately.
5. Compare fresh device data with local operation.
6. Confirm customer access and save the handover record.

Locate the discrepancy between measurements and dashboard before changing settings.

Choose one symptom and time window. Record quantity, units and boundary: grid, inverter output, backup load, household demand, PV or battery SOC. These variables differ; a Load label needs exact-model context.

Compare the local value, cloud device record and plant overview, allowing upload delay. If local and device values agree while the plant differs, investigate aggregation. If the first value is implausible, an app correction cannot repair the measurement.

For several inverters, list included devices and master/slave reporting. SOLARMAN describes a case where automatic selection uses the master and manual selection is needed to sum both. That is not a universal instruction to sum every field: a master may already report a system total.

For daily energy, compare matching dates and accumulation methods. For money, record tariff assumptions; SOLARMAN exposes revenue per kWh. Such an estimate is not automatically the utility bill, especially with losses or time-varying rates.

Change one justified configuration at a time. Keep a before/after record and verify a complete subsequent interval. Ask the installer to resolve physical CT/meter discrepancies rather than masking them in the dashboard.

What to check or record

1. Define one variable and complete comparison window.
2. Record local, device and plant values with timestamps.
3. Review included devices and data sources.
4. Check units, calculation basis and tariff assumptions.
5. Refer physical metering discrepancies to the installer.
6. Recheck a fresh interval and keep the result.

Capture the first event and system context to separate a cause from later alarms.

Begin with safe observation: photograph local status and record time. For visible damage, smoke, burning smell or another immediate hazard, keep clear and follow site emergency arrangements. Do not open equipment or make live measurements.

Record whether the symptom affects power, battery operation, monitoring only or some devices. Cloud-offline status and an electrical fault need different investigations. In parallel, record each inverter’s status and first alarm.

Collect complete model, serial and firmware, battery/BMS status, logger model, mode, schedule and relevant limits. Preserve original settings. Note any update, installation work, router change or expansion just before the event.

Export an incident window if available, retaining units and time zone. Attach local photos and timestamped screenshots. Explain expected versus observed behaviour rather than sending unexplained images.

Send privately to the installer or seller and follow the confirmed exact-model procedure. Record each requested change and result. Repeated resets before collecting evidence can hide the useful event sequence.

What to check or record

1. Record the first fault, time and local state.
2. Classify power, battery, measurement or communications symptoms.
3. Collect exact model/firmware and configuration.
4. Attach timestamped readings and exports.
5. List recent changes and earlier attempts with outcomes.
6. After repair, verify ordinary operation and the original use case.

Energy Pattern sets the priority for solar energy; it is not the whole operating strategy.

The SUN-7.6–12K-SG02LP1-EU-AM2/AM3-P manual defines Energy Pattern as PV-use priority. Batt First prioritises battery charging; Load First prioritises the loads. In this manual, enabling Grid charge makes Load First the default and disables this priority choice. Check the exact family before transferring that rule to another model.

If the question is why solar is being exported before the battery reaches the desired charge, capture Energy Pattern, work mode, Solar Sell and the active TOU row together. Add actual charging power and the battery’s permitted charge limit. A priority label is not a promise that the battery will always accept the configured maximum current. Compare steady readings before changing another field.

What to check or record

1. Read the exact model’s Energy Pattern definition.
2. Capture work mode, Solar Sell, Grid charge and the active TOU row together.
3. Compare simultaneous PV, load, battery and export readings.

Smart Load switches an output; its threshold and grid overrides need separate checks.

For SUN-3–6K-SG03LP1-EU, the manual describes Smart Load as a switched GEN output using battery SOC and PV-power conditions. It specifies separate ON and OFF thresholds. On Grid always on keeps the smart output enabled when the grid is present; off grid immediately off stops it after grid disconnection. These options are not descriptions of solar-only energy.

Distinguish switching a heater or charger on from continuously controlling its consumption. The documented function does not establish that an attached appliance will track every change in solar surplus. Record the appliance’s actual demand, measured PV power, SOC and the complete GEN Port Use screen. If PV is already curtailed, do not assume the displayed Power threshold represents an estimate of unused solar potential.

What to check or record

1. Confirm SmartLoad Output is the selected GEN function.
2. Review ON/OFF, Power and both grid-related overrides together.
3. Test the intended appliance and compare its demand with the measured energy flows.

Export regulation and source separation are different requirements.

No. In the SUN-18K-SG01LP1-EU-AM3-P manual, Zero Export To CT measures grid flow and adjusts generation; the grid can still supplement the loads when PV and battery power are insufficient. That is a grid-connected control strategy, not evidence that the installation has no electrical connection between sources.

Write the requirement precisely: prevent export, use the grid only as a fallback, or ensure mutually exclusive sources through an approved switching arrangement. Those are different design goals. Have the installer show the actual supply paths and switching states on the drawing. A low grid reading, a mode name or a forum suggestion cannot demonstrate electrical separation or establish local connection approval.

What to check or record

1. Separate the no-export objective from any source-separation requirement.
2. Ask for the actual connection and switching diagram.
3. Verify the agreed operating states with the responsible installer.

Separate grid-to-load current capacity, off-grid output and service continuity.

The SUN-5–12K-SG04LP3-EU manual lists maximum continuous AC passthrough from grid to load separately from rated inverter output and off-grid peak power. These describe different operating limits. The grid-present passthrough rating is not extra battery-backed power available during an outage.

A current rating also does not promise what happens in every shutdown or fault state. If household circuits depend on LOAD, include inverter servicing and failure in the handover discussion, not only grid failure. Ask the installer to document the supported supply path and any designed maintenance bypass, with a controlled functional test. An owner’s report that their switched-off unit still passed power is not a guarantee for another model or fault.

What to check or record

1. Record passthrough, rated output and off-grid limits separately.
2. Document how essential circuits are supplied during inverter maintenance.
3. Have the installer verify the actual designed operating states.

An inverter charging schedule and balancing inside a battery are different functions.

The April 2026 SUN-3–6K-SG04LP1-EU-SM1/SM2 manual places Equalization voltage, days and hours on its voltage-based charging page; its Lithium page instead selects a BMS protocol. Separately, the RW-M6.1-B manual describes cell balancing as a function of the battery’s internal BMS. A similarly named inverter setting is therefore not a documented timer for that internal balancer.

If modules drift apart, collect their individual SOC, current, temperature and available cell-voltage records over the same period. Let the battery supplier distinguish a reporting issue, operating condition or cell problem. Do not copy a lead-acid equalization voltage, change charging mode or prescribe a recurring forced charge solely because a forum calls it balancing. Use the approved procedure for the exact battery and integration.

What to check or record

1. Identify the battery mode and the exact menu label.
2. Keep module-level and cell-level observations separate.
3. Obtain the battery-specific balancing or service procedure.

It is a documented recovery function, not a universal faster-charge or capacity-calibration switch.

In the May 2026 SUN-5/6/7.6/8K-SG02LP1-EU-AM2 / SUN-10/12K-SG02LP1-EU-AM3 manual, Activate Battery assists recovery of an over-discharged battery using a low charging current from PV or grid. The label does not mean that an otherwise healthy battery is disabled when the box is clear. Nor does that description promise to repair a failed BMS or synchronise every module’s SOC.

Whether the option should remain enabled belongs to the exact integration instructions: for example, PowerPlus Energy specifies it enabled in its own Eco4840P/Eco4847P voltage-mode setup. That does not authorise the same choice for another battery. Record the battery’s alarms, available voltage/SOC information and approved recovery instructions before attempting recovery. Do not disconnect BMS communication or raise charging voltage merely to force a non-responsive pack to accept energy.

What to check or record

1. Read the recovery function in the exact inverter manual.
2. Confirm the battery maker’s prescribed setting and recovery method.
3. Record the result and the final approved configuration.

Operating-current and short-circuit-current ratings are separate design limits.

The September 2026 SUN-5–12K-SG04LP3-EU datasheet lists maximum operating PV current and maximum input short-circuit current separately. Compare the array’s operating current and short-circuit current with their corresponding limits for the actual tracker arrangement. Deye’s design calculator requests both Imp and Isc; panel watts alone do not establish compatibility.

A fuse is a protective device, not an operating-current regulator, and fitting one does not increase an inverter’s published input rating. Do not use an expectation of clipping as permission to ignore the short-circuit limit. Ask the designer to check the panel data, parallel-string totals and applicable site corrections, then document a compliant arrangement. If a proposed array exceeds a published limit, resolve that design question before connecting it instead of experimenting with fuse sizes.

What to check or record

1. Record Imp and Isc separately for the proposed array.
2. Check limits per tracker and any shared inputs.
3. Keep fuse selection and inverter-input compliance as separate checks.

Compare individual currents and operating states before treating different SOC indicators as a fault.

An inverter’s total battery current does not show how that current is shared. Record each module’s current, SOC, temperature, alarm state and communication status during the same steady charging or discharging period. Different LED steps alone cannot establish unequal current, while a recognised module list alone cannot establish that every module contributes power.

Have the installer compare the actual power connections with the battery’s approved parallel diagram and verify the individual current paths. The September 2026 SE-F16 manual specifies its own cables and parallel arrangements; those requirements must not be replaced by a generic forum wiring recipe. Record whether the difference follows one module, one connection or a temperature/limit condition before drawing conclusions. A persistent module that reaches protection first needs battery-level investigation; increasing the bank’s entered Ah is not a diagnosis.

What to check or record

1. Capture simultaneous module readings over a steady interval.
2. Have wiring and current paths checked against the exact battery manual.
3. Send persistent differences and individual alarms to the battery supplier.

Changing the response to lost communication does not restore the communication link.

The SUN-5–12K-SG04LP3-EU manual V3.3.0 associates F58 with loss of inverter-to-BMS communication while BMS_Err-Stop is active. Its fault table also mentions disabling that setting. Read this as a change to the inverter’s response, not evidence that battery data has returned or that the original fault has been repaired.

Preserve the first event and compare the inverter’s battery-information screen with the battery’s own status. Record the exact models, protocol, firmware and any recent cable or module change. The installer should restore the approved communication arrangement and verify fresh operating limits. Any intentional operation without BMS communication needs a documented, supported configuration for that battery; a cleared alarm alone is not that confirmation.

What to check or record

1. Verify F58 against the installed family’s fault table.
2. Capture the setting and battery information before changes.
3. Confirm restored live BMS data, not only disappearance of the code.

Read the model-specific definition and the battery integration’s required value.

The January 2026 SUN-3.6–8K-SG05LP1-EU manual describes this option for a lithium battery communicating through BMS: when the requested charging current becomes zero, the inverter retains the charging voltage at its then-current value. That is a specific control response, not a general instruction to set a float-voltage field to zero or to turn battery charging off.

Do not infer a universal checkbox value from the word lithium. For comparison, PowerPlus Energy’s Eco4840P/Eco4847P Deye guide specifies Disable Float Charge disabled for its own voltage-mode integration. Confirm the prescribed value for your exact combination. If behaviour changes after toggling it, save the before-and-after settings, BMS request and measured current; keep unrelated work-mode and scheduling changes out of that comparison.

What to check or record

1. Identify whether the system uses working BMS communication or a supported voltage mode.
2. Confirm the required checkbox value in the exact integration guide.
3. Reopen the saved setting and compare actual operation.

Check the energy source, charging permissions and live battery limits in that order.

First identify whether charging should come from solar, the grid or a generator. Compare live source power with household consumption and the saved work mode: solar production alone does not show how much power is available for the battery. For scheduled grid charging, check the inverter clock and day, the active period, grid-charge permission and the target SOC or voltage. Use the exact model’s manual because menu behaviour and available options differ.

Then compare actual battery current with the configured charge-current limit and, in a supported BMS-controlled installation, the live BMS charge allowance. Record SOC, temperature, alarms and recognised modules at the same time. A zero charge request, missing communication and an unavailable energy source are different findings. If the cause remains unclear, send these readings and the saved settings to the installer. Do not raise voltage, disconnect BMS communication or change from Lithium to voltage mode just to make charging start.

What to check or record

1. Confirm the intended charging source and its actual availability.
2. Check the saved work mode, charging permission, active schedule and target.
3. Capture battery current, live BMS allowance, SOC, temperature and alarms together.

Treat migration as a separate transfer with a progress report and acceptance check.

Deye provides a Data Migration workflow in Deye Cloud. It asks for the SOLARMAN account, the plants to transfer and a choice concerning retained or deleted source data. Personal and business destinations differ; a business migration requires its super administrator. Simply adding the logger to another app is not the same workflow.

Before submitting, record the source plants and export important history. Review the retention choice deliberately. Deye says another migration request cannot be submitted while one is running; use Migration Progress and the resulting report instead. Afterwards, compare an older date and a recent date, device identities and access rights. If data is missing, send the report and affected dates to support rather than deleting plants or assuming the transfer is complete.

What to check or record

1. Record source account, destination and selected plants before submitting.
2. Keep the progress/report and avoid duplicate migration attempts.
3. Verify historical dates, current data and intended access after completion.

Cloud connectivity does not prove support for the local protocol your integration expects.

Identify the logger model and firmware separately from the inverter. A local integration must match the logger’s interface and the software’s supported transport. For example, Deye’s DL1000B-ETH V1.0 specification lists TCP 502 for Modbus TCP. This is a model-specific specification, not a port setting to copy to every Deye or SOLARMAN stick.

Compare the integration’s current documentation with the installed hardware before replacing a logger or requesting firmware. Record the address, selected transport, port, firmware and exact connection error. Ask Deye or the installer which local interface that combination supports. A forum success with another firmware is useful evidence to investigate, not approval to downgrade or install its image. Keep control writes disabled until readings are coherent.

What to check or record

1. Record exact logger, inverter and firmware identities.
2. Match local transport and port to the supported combination.
3. Validate read-only data before enabling automation or writes.

Check the integration’s model profile and decoding before changing electrical settings.

Third-party software interprets inverter registers through a device profile. The ha-solarman maintainer lists different Deye profiles for different inverter families, including deye_hybrid, deye_p3 and deye_micro. A connection that returns numbers does not establish that those numbers have the correct meaning or scale.

Capture the same quantity locally and in the integration at matching times. Record the full model, firmware, integration version, selected profile, entity name and unit. An impossible temperature or a consistent multiplier is evidence for a decoding investigation, not proof of a damaged sensor. Do not change a CT ratio, battery voltage or charge limit to compensate for a software display. Ask the integration maintainer to confirm the profile and correction, then review any history affected by the earlier values.

What to check or record

1. Compare matching local and integrated quantities, units and timestamps.
2. Verify the documented profile for the complete inverter model.
3. Retain diagnostic values and check affected history after the correction.

For the specified SG04LP3-EU-AM2-P manual, F13 describes a working-mode change; persistent events still need investigation.

The January 2026 SUN-(5–12)K-SG04LP3-EU-AM2-P manual associates F13 with changes to grid type/frequency, switching the battery mode to No battery, and some older firmware’s work-mode changes. It says the event generally clears automatically. This definition must not be applied to another Deye family without its matching fault table.

Record the exact change immediately before the event and whether normal operation returns. An event that persists, recurs without an intended change or accompanies loss of supply deserves installer investigation. Preserve the original settings and fault timeline. Do not alter the grid code merely to clear the message; any recovery switching should follow the exact model and installation procedure.

What to check or record

1. Match the full model and manual before interpreting F13.
2. Record preceding changes and whether the event clears.
3. Escalate persistent or unexpected repeats with the settings and fault timeline.