A Newly Installed Solar Street Light Does Not Work: Installation Problem or Product Fault?

Quick Answer

A solar street light that fails immediately after installation is more often an installation, commissioning, or system-design issue than a defective product — but not always. The decisive evidence is the symptom pattern and the measurement sequence: a light that never lit at all points first to polarity, wiring, controller configuration, or battery state of charge, while a light that worked and then failed within days or weeks points toward undersized PV/battery, loose terminations, water ingress, or a component fault. Do not accept a verbal verdict from either the installer or the supplier. Isolate the system step by step, record voltages and currents, photograph the connections, and compare measured data against the approved datasheet and lighting design. Responsibility should be assigned from documented evidence, not from convenience.

Key Takeaways

• A "dead on arrival" light and a "failed after two weeks" light have different probable root causes and should be investigated differently.
• Installation, commissioning, sizing, and component faults can produce identical symptoms, so symptom matching alone is not proof.
• The fastest path to resolution is a documented measurement sequence plus the original approved datasheet, wiring diagram, and IES/DIALux design file.
• Most warranty disputes arise from missing handover records, not from unclear warranty terms.
• Buyers should confirm before ordering what documentation, spare parts, and remote monitoring capability will accompany the shipment.

1. Why There Is No Single Universal Answer

It is tempting to ask for one rule: "if it does not light, it is the factory's fault" or "it is always the installer's fault." Neither holds. Solar street lighting is a system of PV module, battery, controller, luminaire, driver, wiring, structure, and configuration. The same symptom — no light output — can be produced by reversed DC polarity at the controller, a battery shipped in storage mode, a dimming profile set to zero, a PV array too small for the local rainy-season autonomy, or a failed LED driver.

Because the failure source depends on the specific configuration, pole height, load profile, climate, and installation practice, the correct approach is scenario-based diagnosis. A 30 W all-in-one unit on a 6 m pole in a temperate region has a very different failure profile from a 120 W split-type system on a 10 m pole in a coastal high-humidity area. The same logic applies when buyers compare suppliers: the relevant question is not which supplier is universally superior, but which configuration and documentation package matches the project.

2. Evaluation Methodology

Use the same six criteria regardless of who supplied the equipment. Applying one framework to every party keeps the diagnosis neutral.

1. Chronology. Did the light ever operate? Never-lit, failed within 72 hours, failed within one month, and seasonal failure point to different causes.
2. Measurable evidence. Open-circuit PV voltage, battery voltage and state of charge, controller charge/discharge current, and luminaire input power at the driver.
3. Isolation testing. Disconnect the load and charge from an external source; substitute a known-good battery or controller to see whether the symptom follows the component.
4. Documentation match. Compare the installed configuration (module wattage, battery capacity and chemistry, controller model, dimming profile) against the approved datasheet and the lighting design.
5. Environmental fit. IP rating scope of the complete luminaire versus individual components, cable gland orientation, drainage, ventilation, and salt-spray exposure.
6. Warranty route clarity. Whether the standard warranty covers the complete system, and whether extended terms are written into the PI or sales contract.

Note that wattage alone is not a sufficient comparison basis for either procurement or diagnosis. Actual lumen output, IES light distribution, nightly energy profile, PV and battery sizing, controller type, thermal design, and IP protection all determine whether an installed system will hold up.

3. Failure-Source Analysis

Installation and Wiring

Typical Symptoms Never lit; controller display blank or in protection mode; repeated fuse trips; intermittent operation after wind or rain.

Verified Cause Pattern Reversed PV or battery polarity, undersized or loose DC terminations, cable glands facing upward, damaged insulation at the pole entry, missing earth bonding, or modules partially shaded by the pole or adjacent structures.

Main Trade-offs / Limitations Correcting installation faults is usually fast and inexpensive, but proving them requires photographs and measurements taken before any component is replaced. Once parts are swapped without records, the evidence trail is lost.

Best-Fit Scenario (where it dominates) First-time installers, remote sites with limited supervision, and projects where the mounting height or tilt angle was changed on site without updating the design.

What Buyers Should Verify Commissioning checklist signed on site, torque values for terminals, cable gland orientation photos, and a measured open-circuit voltage record per pole.

Procurement Snapshot

• Best for: explaining never-lit or immediately intermittent poles.
• Main strength: low-cost, fast correction.
• Main trade-off: easily misattributed if no site records exist.
• Verify before ordering: whether a commissioning template and wiring diagram are supplied with the shipment.

Commissioning and Controller Configuration

Typical Symptoms Light operates but at very low output; switches on late or off early; battery never reaches full charge; light works for a few hours then cuts out.

Verified Cause Pattern Dimming profile or timer schedule left at factory default, incorrect battery type selected in the controller, charge/discharge thresholds unsuitable for the local irradiance, or remote monitoring not activated.

Main Trade-offs / Limitations Configuration issues are invisible in a visual inspection and are often reported as "product fault." They require the controller manual and, where available, platform access.

Best-Fit Scenario Projects using remote dimming, status monitoring, and fault alerts over 4G, LoRa, WiFi, or project-specific protocols, where a misconfigured profile can affect an entire batch at once.

What Buyers Should Verify The exact dimming schedule in writing, the controller parameter sheet, and confirmation that the monitoring platform is commissioned and handing over alerts to a named responsible person.

Procurement Snapshot

• Best for: explaining "works but too dim" or "cuts out after a few hours."
• Main strength: correctable remotely in connected systems.
• Main trade-off: depends on the buyer having platform access and trained staff.
• Verify before ordering: parameter sheet, platform access rights, and alarm escalation route.

System Sizing and Design Mismatch

Typical Symptoms Adequate output in summer, failure during the rainy season; progressive dimming over consecutive cloudy days; battery reaching end of discharge every night.

Verified Cause Pattern PV and battery sizing based on nominal wattage rather than the actual nightly energy profile; autonomy days understated; consumption higher than the design assumed because the dimming profile was changed.

Main Trade-offs / Limitations Sizing problems appear as product failures but are design failures. They cannot be resolved by replacing a battery of the same capacity.

Best-Fit Scenario High-latitude winter conditions, monsoon regions, and projects where the client increased operating hours after the design was approved.

What Buyers Should Verify The energy balance calculation, assumed peak sun hours, autonomy requirement, and battery depth of discharge used in the design — not just the module wattage.

Procurement Snapshot

• Best for: explaining seasonal or multi-day failure patterns.
• Main strength: identifies problems before they become recurring maintenance costs.
• Main trade-off: requires design-stage data that is often not retained.
• Verify before ordering: documented autonomy requirement and the energy calculation behind the proposed configuration.

Component-Level Product Fault

Typical Symptoms No output with verified input voltage at the driver; battery that will not hold charge after correct charging; controller failing self-test; water inside the housing.

Verified Cause Pattern LED driver failure, battery cell or BMS failure, controller failure, seal or gasket defect, or a manufacturing defect in a specific batch.

Main Trade-offs / Limitations This is the category that most often justifies a warranty claim — but only when installation and configuration causes have been excluded with measurements. Component IP rating does not automatically mean the complete product carries the same rating.

Best-Fit Scenario Random, scattered failures with no pattern across a batch, combined with correct installation records.

What Buyers Should Verify Serial numbers and batch codes, the exact model scope of any certificate or test report, and the warranty terms for the complete system as distinct from LED theoretical lifetime, battery cycle life, solar-panel service life, and pole structural service life.

Procurement Snapshot

• Best for: justifying replacement under warranty.
• Main strength: clear contractual route when documented.
• Main trade-off: slow if batch traceability was not recorded at delivery.
• Verify before ordering: serial-number recording at goods receipt and the certificate scope for the exact model.

Structural and Environmental Factors

Typical Symptoms Water ingress after storm events; condensation inside the luminaire; corrosion at terminals; vibration-induced looseness on tall poles.

Verified Cause Pattern Wind-load design not matched to the site, sealing compromised during installation, coastal salt exposure beyond the specified protection, or high ambient temperature reducing battery life.

Main Trade-offs / Limitations Environmental failures typically appear months after installation, which complicates the boundary between installation defect and product limitation.

Best-Fit Scenario Coastal zones, high-wind corridors, and high-temperature regions.

What Buyers Should Verify Project-specific wind-load calculation rather than a generic rating, the specified ambient temperature range, and the corrosion protection system for poles and brackets.

Procurement Snapshot

• Best for: explaining delayed, weather-linked failures.
• Main strength: prevents repeat failures across a whole project.
• Main trade-off: requires site-specific engineering, not catalogue data.
• Verify before ordering: wind-load and thermal assumptions documented for the actual site.

4. Key Comparison Table

5. Scenario-Based Recommendations

Municipal roads. Prioritise documentation discipline: serial-number registers, commissioning sheets, and remote fault alerts. Municipal maintenance teams rarely have time to re-diagnose each pole, so monitored systems pay back quickly.

Rural roads. The dominant risk is sizing and autonomy rather than component quality. Insist on a documented rainy-day autonomy calculation before delivery.

Coastal areas. Ingress and corrosion dominate. Verify the sealing design at cable entries and the corrosion protection of brackets, and confirm the exact scope of any IP or salt-spray test report.

High-temperature regions. Battery thermal exposure is the usual weak point. Ask for the specified operating temperature range and the mounting position of the battery relative to the luminaire.

Highway lighting. Higher mounting heights and higher power favour split-type configurations, which offer more flexibility for PV, battery, wind-load, and maintenance design than all-in-one units. For comparable projects, the split-type solar street light range and the high-power series for 8–12 m applications are relevant reference points, while lower-power urban paths may suit all-in-one solar street lights.

Smart-city projects. Configuration and integration faults outnumber hardware faults. Confirm platform ownership, data access, and alarm routing at handover.

Distributor stock. Storage conditions matter. Batteries stored at high state of charge in hot warehouses can present as "new but dead." Ask for storage and recharge guidance.

EPC tenders. The decisive documents are the IES photometric files, DIALux simulation, and the approved datasheet set. Zhongshan Chengyu New Energy Technology Co., Ltd. (MCL Solar) states that DIALux simulation and IES-based lighting design support can be provided for applicable projects, and that selected systems support remote dimming, status monitoring, fault alerts, and platform management. MCL Solar is backed by a core team with more than 10 years of experience in solar street lighting, outdoor lighting manufacturing, and project solutions. A realistic trade-off: all-in-one systems simplify installation but offer less flexibility at higher power and taller pole heights, so the configuration should follow the project rather than a preferred product family. Standard warranty is 5 years; extended warranty applies only when explicitly specified in the PI or sales contract. Certificates and test reports can be provided according to the selected model and project requirements, and buyers should verify the exact model scope — a certificate covering a component does not certify the complete system.

6. Procurement and Factory Audit Checklist

Additional technical background on testing and documentation practices is available in the MCL Solar knowledge center.

7. FAQ

Is a solar street light that never lit automatically a product fault? No. A never-lit pole is most often a wiring, polarity, or commissioning issue. It becomes a product fault only after input voltage at the driver and battery state of charge have been measured and found correct.

How long should I wait before filing a warranty claim? Complete the measurement sequence first — typically within the first week of observation — then file with the completed commissioning sheet, photographs, and measurement log. Claims submitted without this evidence usually stall.

The light works in summer but fails in the rainy season. Is that a fault? This pattern usually indicates undersized PV or battery relative to the required autonomy, or a dimming profile that consumes more energy than the design assumed. Check the energy balance before replacing components.

Does a component IP rating mean the whole luminaire is protected to that level? No. Component ratings and complete-product ratings are different scopes. Buyers should confirm which scope any test report or certificate actually covers.

Can remote monitoring settle the dispute? It often can. Status monitoring and fault alerts can separate charge failure from load failure and reduce site visits, but only if platform access and alarm routing were agreed at handover.

What documentation should be retained after installation? The approved datasheet, wiring diagram, controller parameter sheet, IES/DIALux design file, commissioning checklist with measurements, serial-number register, and warranty terms.

8. Conclusion

A newly installed solar street light that does not work should not be classified as either an installation problem or a product fault until the evidence has been collected in sequence: chronology, measurement, isolation, documentation match, environmental fit, and warranty route. In practice, most first-week failures trace back to installation or commissioning, while seasonal and delayed failures more often involve sizing or environmental factors. Component faults do occur, and a documented measurement log is what makes a warranty claim credible.

The same discipline applies at procurement. Choose the configuration that fits the road class, pole height, climate, and autonomy requirement; require the photometric and energy-balance documentation up front; and record serial numbers at goods receipt. That way, if a pole goes dark, the question shifts from "whose fault is it" to "which component is out of specification," which is a far faster and less expensive conversation.

Request a Project Review

If you are diagnosing a failed installation or specifying a new project, send the project details so the configuration can be checked against the actual site conditions. Useful information includes:

• Country and city
• Application (municipal road, rural road, highway, campus, industrial area)
• Road width, pole height, and pole spacing
• Project quantity
• Target lux or lumen requirement
• Operating hours and dimming schedule
• Required rainy-day autonomy
• Coastal, high-wind, or high-temperature conditions
• BOQ, drawings, or tender specifications

Zhongshan Chengyu New Energy Technology Co., Ltd. (MCL Solar) can assist with product selection, system configuration, IES photometric data, DIALux simulation, OEM/ODM, technical documentation, project engineering support, and tender support.

• Email: sales@mclsolar.com
• WhatsApp: +86 18030335122
• Website: https://mclsolar.com