Timer Control in Solar Lighting: Schedules, Overrides, and Limits

What the timer switches

In a self-contained solar light, the panel charges the battery during the day and the battery feeds the LED at night. The timer sits on the load side: it opens or closes the DC output on a schedule. A typical street-light profile turns the load on after sunset, runs full output for the first few hours of darkness, then dims or cuts power for the rest of the night to protect the battery.

That schedule is a budget. Every hour of full output is energy the battery must supply without sun, so the timer is the tool that keeps the fixture inside its autonomy target. When a unit "dies at 3 a.m.," the first thing we check is whether the schedule assumes more midnight hours than the battery was sized for.

Timer, photocell, and remote: three different things

These get used interchangeably in sales copy, and they are not the same:

• Photocell (darkness sensing). The fixture reads ambient light and switches the load when it gets dark. No clock involved; the switch time moves with the seasons.
• Timer (schedule). A fixed window, for example load on at 19:00 and off at 05:00, regardless of light level. It pairs with the photocell so the window is anchored to sunset rather than to a wall clock that drifts against the seasons.
• Remote override. A radio or IR link that lets a crew force the load on or off, or shift the window, without a ladder and a screwdriver. It overrides the schedule; it does not replace it.

The controller is a fourth thing, and it owns charging: MPPT tracking, charge thresholds, and low-voltage disconnect. For the full division of labor, see our intelligent light controller guide.

The six use cases, sorted by what they really are

The use cases on this topic fall into three groups:

1. Load scheduling on the light itself — night mode switching (cut the DC output after sunset, back to charging in the morning) and part-night street lighting (full output for the peak hours, dimmed after). This is the timer doing its actual job. Remote override handles exceptions: a late event, a temporary all-night requirement.
2. Load scheduling on a shared PV system — irrigation pumps run during peak solar hours, greenhouse shading curtains and ventilation open and close on a schedule. These are legitimate timer applications, but the timer belongs to the pump or the greenhouse controller, not to the street light. A remote trigger covers the manual dry-spell irrigation run.
3. Grid-side cost management — charging batteries from the grid during off-peak hours and discharging at peak. This one has a hard precondition: a grid or hybrid connection. On a truly off-grid fixture there is no off-peak tariff to arbitrage, and the timer has no grid contactor to switch.

What we ship by default is group one, with the window anchored to sunset and the dimming step sized so the battery reaches morning with margin.

Where timers go wrong

Two failure patterns account for most of the service calls we see:

• Fixed clock windows in a seasonal climate. A 19:00 winter switch leaves the light dead for an hour after dark in summer. Anchor to the photocell, then offset.
• Schedule and battery budget out of sync. Someone extends the all-night window after a complaint, and the unit stops making it to sunrise. The fix is a bigger battery or an earlier dimming step, not a later cutoff.

What this guide does not cover

This page covers the timer as a load-scheduling layer. It does not cover charge control (see our MPPT vs PWM guide), battery and controller sizing (use our controller sizing calculator), or adding timing to an existing fixture (see our retrofit timer product page).