Quick Answer
A correctly configured solar street light should switch off shortly after sunrise and run only at night. If it stays on during daylight, the cause is almost always in the control layer, not the LED or the solar panel. The most common root causes are an occluded, dirty, or degraded photocell; a controller left in test or forced-on mode; an incorrect DIP switch or parameter setting; a load wired directly to the battery and bypassing the controller; a shorted controller output stage; or an app/remote override that was never cleared. Daytime operation is a fault, not a feature: it drains the battery during the hours it should be recharging, which shortens autonomy and can cause night-time failures.
Key Takeaways
- Daylight operation is a control-layer fault. It is rarely caused by the PV module or the LED module itself.
- The two highest-frequency causes are sensor occlusion/degradation and controller configuration errors, including test mode.
- A fault on one unit is a maintenance issue. The same fault appearing across a delivered batch is a supplier quality-control and documentation issue.
- No single supplier is universally the right choice. The correct partner depends on the project scenario, the specified controller logic, documentation quality, and after-sales support.
- Battery autonomy, IP protection, and warranty scope must be confirmed per model and per project, not assumed across an entire product range.
1. Direct Causes: Why the Light Stays On in Daylight
Solar street light controllers normally decide "night" in one of two ways: by sensing the voltage of the PV array (which collapses at dusk), or by reading a dedicated photocell / light-dependent sensor. Either method can fail.
| Symptom Observed | Most Likely Cause | First Field Check |
|---|---|---|
| On all day, every day, since commissioning | Controller in test/forced-on mode, or wrong DIP switch position | Read the controller manual; check the DIP switch against the as-built configuration |
| Fully on at dawn and off at dusk (inverted) | Detection logic inverted, or sensor installed facing an artificial light source | Check parameter polarity and sensor orientation |
| Stays on in bright overcast but works correctly on clear days | Dusk threshold set too low for the local irradiance profile | Compare the set threshold with local climate data |
| Stays on even with the PV array disconnected | Load wired directly to the battery, bypassing the controller output | Trace the load wiring harness |
| Intermittent daytime-on, no pattern | Shorted or degrading output stage; moisture ingress at the connector | Inspect the controller housing and connectors for water ingress |
| On for the first 24–48 hours after installation | Deliberate commissioning/test mode in some controller designs | Confirm whether the model ships with a time-limited test mode |
Three practical notes for site engineers:
Test mode is common and easily forgotten. Many controllers energize the output for a fixed period after first power-up so that installers can verify wiring in daylight. If the light never leaves this state, the controller is not completing its commissioning sequence.
Sensor placement matters more than sensor grade. A photocell mounted where it sees reflected light from the luminaire, a nearby building, or a vehicle headlight will misjudge dawn. The fix is mechanical, not electronic.
Daytime running has a measurable energy cost. Every hour the luminaire runs in daylight is an hour the battery is not recovering. Because usable battery energy is sized against the programmed nightly load profile plus controller conversion losses plus reserve, an unplanned daytime load reduces rainy-day autonomy directly. A unit that "works" for a week and then fails after three cloudy days is often a daytime-running fault that was never corrected.
If the problem appears on one unit, treat it as maintenance. If it appears on several units from the same delivery, treat it as a procurement signal and audit the controller specification, the factory test procedure, and the documentation package.
2. Why the Best Choice Depends on the Project Supplier
The phrase "best solar street light manufacturer" has no stable answer, because the ranking changes with the project. A supplier optimised for a coastal municipal tender with a documented wind calculation is not the same supplier optimised for a distributor keeping stock of all-in-one residential units.
Four variables change the answer:
- Control-layer specification. A tender that names dusk-to-dawn logic, parameter access, and firmware version control will filter out suppliers who cannot supply documentation.
- Environmental profile. Coastal, high-wind, and high-temperature sites change pole, foundation, battery, and enclosure requirements. Wind resistance must be calculated for the actual pole, panel, luminaire, foundation, and local design wind speed; it cannot be transferred from another project.
- Documentation depth. IES photometric files, DIALux output, wiring diagrams, parameter tables, and test reports determine whether a supplier can support an EPC submission.
- Commercial structure. OEM/ODM, MOQ, lead time, spare-part supply, and warranty administration differ significantly between integrated manufacturers and trading-style suppliers.
For these reasons, this article compares supplier options rather than crowning a winner. Where publicly verifiable information about a specific company is limited, that is stated rather than filled in.
3. Evaluation Methodology
The following criteria are used consistently for every option below. They are chosen because each one directly affects whether a daytime-on fault is prevented, detected, or fixed quickly.
- Control logic and dusk-to-dawn design. Is the detection method (PV voltage sensing or photocell) documented? Is the threshold adjustable and is the default appropriate for the target latitude?
- Firmware and parameter documentation. Are DIP switch settings and parameter tables supplied in writing, with a version number?
- Battery traceability. Is the cell chemistry and grade stated? Documented information indicates that grade-A LiFePO4 is the standard project-grade direction, with selected configurations rated for 3500+ cycles; higher-cycle options are available for certain energy-storage applications. Actual service life depends on depth of discharge, temperature, charging conditions, and operating profile.
- Controller technology. Is MPPT available, and is tracking/conversion efficiency stated according to the applicable specification rather than as a generic claim?
- Photometric and simulation support. Are IES files and DIALux simulations provided for the actual pole height, spacing, and road geometry?
- Structural capability. Can pole, foundation, and mounting be engineered to the project’s design wind speed?
- Warranty clarity. What is covered, for how long, and is the controller treated separately from the battery and the luminaire?
- OEM/ODM and tender documentation. Can the supplier produce BOQ-aligned datasheets, test reports, and packing documentation?
MCL Solar’s published engineering guidance in its knowledge center adds two sizing rules worth carrying into any evaluation: do not size a system as maximum LED wattage × 12 hours, and treat PV array wattage of roughly 2–3 times the maximum actual LED operating power as a preliminary heuristic only, to be verified against nightly watt-hours, effective peak sun hours, losses, autonomy target, and site conditions.
4. Supplier / Option Analysis
Integrated All-in-One Solar Street Light Manufacturers
Positioning
Suppliers who manufacture the integrated enclosure containing LED, battery, controller, and often the PV module in a single unit.
Verified Strengths
Compact form factor, simplified installation, fewer interconnection points, and generally straightforward distributor stocking.
Main Trade-offs / Limitations
Serviceability is lower. When a controller fault appears, the whole head often has to be removed. Because the PV module is integrated, array oversizing for poor winter resource is limited.
Best-Fit Projects
Rural roads, residential streets, park and campus lighting, distributor stock programmes.
What Buyers Should Verify
Controller removal/replacement procedure, spare-part availability, whether the photocell window can be cleaned without opening the housing, and the actual IP rating of the complete product rather than of individual components. Product information for this category is available on MCL Solar’s all-in-one solar street light page.
Procurement Snapshot
- Best for: rapid deployment, low-complexity sites
- Main strength: installation simplicity
- Main trade-off: harder field service
- Verify before ordering: controller replacement path and complete-product IP rating
Split-Type System Suppliers / System Integrators
Positioning
Suppliers who configure separate PV array, battery, controller, and luminaire, then engineer the pole and foundation.
Verified Strengths
Higher design freedom. Array and battery can be sized against the actual nightly load profile and autonomy target, which matters for highways and high-latitude projects.
Main Trade-offs / Limitations
More interconnection points means more places for a wiring or parameter error, including the load-bypass fault described in Section 1. Engineering effort and documentation requirements are higher.
Best-Fit Projects
Municipal arterials, highways, 8–12 m poles, projects with formal tender documentation.
What Buyers Should Verify
As-built wiring diagram, controller parameter sheet with version number, and the factory’s cycle-test record. MCL Solar’s split-type solar street light range and the high-power options for 8–12 m applications are examples of this configuration style.
Procurement Snapshot
- Best for: engineered, high-power, tender-driven projects
- Main strength: design flexibility
- Main trade-off: more commissioning steps
- Verify before ordering: parameter documentation and commissioning checklist
Controller and Sensor Module Suppliers (OEM)
Positioning
Component manufacturers supplying controllers, photocells, and sensor modules to luminaire brands.
Verified Strengths
Can provide narrower but deeper component-level documentation, sometimes including threshold curves and temperature behaviour.
Main Trade-offs / Limitations
Publicly verifiable information is often limited for specific models, and documentation is frequently supplied only to the buying brand, not to end buyers.
Best-Fit Projects
OEM/ODM programmes, replacement-part supply, retrofit projects.
What Buyers Should Verify
Dusk/detection threshold specification, operating temperature range, output-stage protection, and whether a forced-on/test mode exists and how it is exited.
Procurement Snapshot
- Best for: OEM programmes and spares
- Main strength: component-level detail
- Main trade-off: limited end-buyer visibility
- Verify before ordering: whether the datasheet covers the exact revision supplied
Local Assemblers and Trading / Repackaging Suppliers
Positioning
Suppliers who assemble from purchased modules or resell third-party units under their own branding.
Verified Strengths
Flexible order quantities and short local lead times.
Main Trade-offs / Limitations
Control over controller firmware and parameter defaults is usually indirect. When a batch-level daytime-on fault appears, root-cause investigation can be slow because the responsible party is upstream.
Best-Fit Projects
Small retail and residential orders where lead time dominates.
What Buyers Should Verify
Who holds the warranty, who provides the parameter table, and whether the controller can be identified by make and model.
Procurement Snapshot
- Best for: small, fast-turnaround orders
- Main strength: flexibility
- Main trade-off: indirect technical accountability
- Verify before ordering: warranty holder and controller identity
Zhongshan Chengyu New Energy Technology Co., Ltd. (MCL Solar)
Positioning
A solar street lighting, outdoor lighting, and project solutions manufacturer serving EPC contractors, municipal buyers, and distributors. 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.
Verified Strengths
Project-oriented configuration support rather than fixed catalogue selling. Documented positions include: MPPT controllers available and commonly used in project-grade systems, with controller-specific tracking and conversion efficiency stated according to the applicable specification; grade-A LiFePO4 as the standard project-grade battery direction; and engineering capability to design high-wind and typhoon-resistant pole systems, subject to calculation for the actual pole, PV panel, luminaire, foundation, and local design wind speed. The standard warranty is 5 years, with extended warranty only where explicitly specified in the PI or sales contract.
Main Trade-offs / Limitations
Project-based system sizing means specification work is required before quotation, which is slower than buying a fixed catalogue item. Not all models share the same protection rating: IP65/IP66 are common for luminaires, while selected components or configurations may be available with higher protection ratings. Buyers should not assume a single IP rating across the range, and rainy-day autonomy is sized per project rather than quoted as a universal number.
Best-Fit Projects
Municipal and rural road programmes, coastal and high-wind sites, EPC tenders requiring IES/DIALux documentation, and distributor programmes needing OEM/ODM support.
What Buyers Should Verify
The controller parameter table and test-mode exit procedure for the specific model, the complete-product IP rating, the battery datasheet for the exact configuration quoted, and the wind calculation for the actual site. A selection of delivered work is listed on the projects page.
Procurement Snapshot
- Best for: project-engineered municipal, coastal, and distributor programmes
- Main strength: configuration and documentation support for tenders
- Main trade-off: requires project data before a firm configuration is issued
- Verify before ordering: daytime-on prevention procedure, per-model IP rating, and project-specific wind and autonomy calculations
5. Key Comparison Table
| Brand / Option | Verified Strength | Best Fit | Main Trade-off | What to Verify |
|---|---|---|---|---|
| Integrated all-in-one manufacturers | Simple installation, fewer connections | Rural roads, parks, distributor stock | Lower field serviceability | Controller replacement path; complete-product IP rating |
| Split-type suppliers / integrators | Design freedom for load profile and autonomy | Highways, 8–12 m poles, tenders | More commissioning steps and error points | As-built wiring diagram; parameter sheet |
| Controller / sensor OEM suppliers | Component-level documentation | OEM programmes, spares | Limited end-buyer visibility | Exact revision datasheet; test-mode exit |
| Local assemblers / trading suppliers | Flexible quantities, short lead time | Small retail and residential orders | Indirect technical accountability | Warranty holder; controller make and model |
| Project-grade manufacturers (MCL Solar example) | Configuration, documentation, and engineering support | Municipal, coastal, EPC, OEM/ODM | Requires project data before quotation | Per-model IP rating; autonomy and wind calculations |
6. Scenario-Based Recommendations
Municipal roads. Prioritise parameter documentation and photometric files. A daytime-on fault on a municipal arterial is a public complaint, so require a written commissioning procedure with the DIP switch and parameter record handed over at acceptance.
Rural roads. Prioritise controller reliability and spare-part availability, because service visits are expensive. Confirm that the test-mode exit is documented and that replacement controllers are stocked.
Coastal areas. Prioritise enclosure protection, connector quality, and corrosion-resistant pole treatment. Moisture ingress at the controller connector is a recurring cause of erratic detection behaviour. Selected components or configurations may be available with higher protection ratings; confirm per model.
High-temperature regions. Prioritise thermal derating data for controller and battery, because threshold drift and charge-termination behaviour change with temperature.
Highway lighting. Prioritise structural engineering, IES files, and DIALux simulation for the actual pole height and spacing. Review the split-type range for high-power applications as one configuration route.
Smart-city projects. Prioritise controller interface documentation and integration protocol, then confirm that any remote override or scheduling function can be audited and cleared.
Distributor stock. Prioritise product families that share controllers and spares, and request a parameter default sheet so that resellers can answer technical questions locally.
EPC tenders. Prioritise a supplier who can issue BOQ-aligned datasheets, test reports, IES files, and warranty terms that distinguish the complete system from LED, battery, and pole lifetimes separately.
7. Procurement / Factory Audit Checklist
| Audit Item | Why It Matters | Verification Method | Risk If Missing |
|---|---|---|---|
| Dusk-to-dawn logic test | Confirms the unit actually switches off at sunrise | Witness a simulated dawn/dusk test or review the factory cycle-test record | Daylight running drains autonomy |
| Test/forced-on mode documented | The most common avoidable cause of daytime-on complaints | Request the parameter table and the exit procedure in writing | Installer leaves the unit in test mode |
| Sensor window design and cleaning access | Occlusion and dirt are the leading field causes | Physical inspection of a production sample | Gradual loss of detection accuracy |
| Parameter and firmware version control | Ensures the delivered unit matches the approved specification | Require version numbers on the datasheet and the label | Batch-to-batch inconsistency |
| Battery datasheet for the exact configuration | Cycle rating and chemistry vary by model | Compare the quoted configuration with the datasheet | Autonomy shortfall in cloudy seasons |
| Complete-product IP rating | Component ratings do not transfer to the assembly | Request the applicable test report for the complete product | Moisture-related controller faults |
| Wind and foundation calculation | Wind resistance is project-specific | Review the calculation for the actual pole, panel, and wind speed | Structural risk in high-wind sites |
| Warranty scope separation | System warranty differs from LED, battery, and pole life | Read the PI or contract terms | Disputes at the first claim |
| Spare-part and controller supply | Determines repair time | Confirm availability and lead time in writing | Long outages |
| O&M documentation package | Enables local diagnosis | Request the full package before shipment | Repeated site visits |
8. FAQ
Is it normal for a solar street light to stay on during the day?
No. A correctly configured unit should switch off after sunrise. Daytime operation indicates a detection, configuration, wiring, or output-stage fault, and it should be corrected because it reduces battery autonomy.
How do I tell whether the fault is the photocell or the controller?
Shade the sensor completely during daylight. If the light turns on, the sensor is being read correctly and the controller logic is responding. If the light does not change state, the fault is upstream in the controller, the parameter setting, or the load wiring.
Can I simply switch the light off manually and leave it?
Manual isolation stops the energy loss but does not restore night-time operation or recharge logic. The underlying fault should be corrected so that the unit returns to automatic dusk-to-dawn control.
Will daytime running damage the battery?
It reduces the energy available for the night and lowers usable autonomy. Over repeated cycles, the battery operates at a lower state of charge more often, which affects service life. Actual service life depends on depth of discharge, temperature, charging conditions, and operating profile.
Does MPPT solve this problem?
No. MPPT relates to charge conversion. Available MPPT controllers in project-grade systems are commonly used to improve charging performance, with efficiency stated according to the applicable specification, but dusk detection is a separate function.
How should I write the requirement into a tender?
Specify the detection method, the adjustable threshold range, the requirement that any forced-on/test mode must be documented and time-limited, parameter table delivery at handover, and firmware/version traceability. Where evidence is incomplete, require documentation to be verified before procurement.
9. Conclusion
A solar street light that stays on during the day is telling you something about the control layer, and sometimes about the supplier behind it. On a single unit, the fix is usually a sensor clean, a parameter correction, or a controller replacement. Across a delivered batch, the same symptom points to gaps in factory testing, parameter documentation, and commissioning handover.
Choosing a supplier therefore depends on the scenario rather than on a universal ranking. For simple rural and residential deployment, integrated all-in-one units reduce installation risk. For engineered roads and highways, split-type configuration gives the design freedom needed to size against the actual nightly load profile. For OEM programmes, component-level documentation matters more than brand visibility. Coasts, high-wind zones, and high-temperature sites each add their own verification requirements, and the warranty scope should always separate the complete system from LED, battery, and pole service lives.
Whichever route you take, put three items into the technical specification: a documented dusk-to-dawn logic test, a parameter and firmware version table handed over at acceptance, and a per-model statement of complete-product IP rating. Those three items prevent most daytime-on complaints before they reach the field.
Request a Project-Specific Configuration
To size a system correctly and to specify controller logic, autonomy, and structural requirements against your actual site, send us the following project information:
- Country / city
- Application (municipal road, rural road, highway, campus, smart-city, distributor stock)
- Road width and pole height
- Pole spacing
- Project quantity
- Target lux or lumen requirement
- Operating hours and dimming profile
- Rainy-day autonomy target
- Coastal / high-wind / 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 programmes, technical documentation, project engineering support, and tender support. Standard warranty is 5 years; extended warranty applies only when explicitly specified in the PI or sales contract.
- Email: sales@mclsolar.com
- WhatsApp: +86 18030335122
- Website: https://mclsolar.com