Slim profile,
wide awake.
The flat-profile all-in-one, with a camera on the same pole: panel, battery, optic and IoT node in one slim casting, and surveillance running off a supply of its own. Solara I covers 20–90 W, Solara II 100–200 W, and both report to the same cloud.
One pole,
everything on it.
Solara generates its own power, stores it, and decides what to do with it — no trench, no meter, no grid connection to wait for. Panel, pack, controller and luminaire share one aluminium body, and the camera rides beneath them on a supply of its own, which is what lets the whole pole go up on a spigot in an afternoon. Select a part in the viewer to isolate it.
Philips Lumileds, eight optics
210–220 lm/W from one to four LED modules, over 50,000 h, in 2500–6500 K bands. The lens is chosen per road rather than per catalogue: eight IES distributions, from a 60×100° throw down a carriageway to a 150° wash over a yard.
02 — The controllerMPPT charge and IoT in one
An MPPT controller tracking above 99.9%, with five-stage dimming, motion mode and — on Controller C — dusk-to-dawn and a time-of-turn-off that works back from sunrise. The IoT node rides the same board and reports what it did.
03 — The supplyPanel and pack in one body
A monocrystalline module at 24% and a LiFePO₄ pack good for more than 4000 cycles, sized together against a six-hour charge. Both are inside the same housing as the light, so there is nothing on the pole to align, cable or steal.
04 — The platformOne console over all of it
Every pole reports to iNET Cloud: dimming schedules and policy out, energy, state of charge and faults back. Dashboards, a live map, alarms pushed as they are raised, and reporting an energy contract can be settled on — from a browser, with no software to install and nothing on site to maintain.
The engine,
the optic,
and where it points.
Three things decide what a solar street light actually lays on the road: how efficiently the engine makes light, how tightly the optic cuts it, and where the head is aimed once it is up. The first two are specified; the third is set on site, and the travel quoted here is what the head actually clears on the pole, not the fitter's nominal rating.
Up to 220 lm/W, IK08
Philips Lumileds in one to four modules, over 50,000 h, CRI 70 nominal, in different CCT bands from 2500–6500 K. Eight IES distributions cover the roads a solar light actually gets specified for. IP66 and IK08 in RAL9005, on a slip fitter with a 0°–90° adjustable spigot.
Eight distributions,
cut at the LED
The beam is shaped at the source. Every engine carries a moulded lens array — one optic over each LED — so the pattern is made where the light leaves the die rather than trimmed afterwards by a reflector or a shield, and very little of it is thrown at the sky or through a bedroom window. Which of the eight distributions a pole is built with is chosen per road — a 60×100° throw down a carriageway, a 150° wash over a courtyard — and it is a different lens plate, not a setting.
The 70×135° array, as supplied. Each dimple is one LED's optic and the plate is a single moulding, so the pattern cannot drift out of alignment on site.
- 60×100°
- 65×145°Type IV-S
- 65×155°Type II-M
- 70×135°shown here
- 75×150°
- 80×150°
- 110°
- 150°
Left: how the light leaves the luminaire. Intensity in candela against the angle from straight down, in the plane across the carriageway (C0–C180) and along the road (C90–C270). Almost nothing is thrown behind the pole, which is what keeps the light on the road instead of in the windows facing it.
Right: what that puts on the ground. Set the mounting height and the pattern redraws: colour shows relative brightness, the contour lines are absolute lux, and the kerb and a 7 m carriageway give the scale.
The Type III-M is one of the eight distributions listed above — the same luminaire, a different lens for a different road.
Aimed on site, not in the factory
Two joints, and they are independent. Every light engine hinges on its own mount through ±30°, so a pole on a bend can throw each module down a different line; the whole fixture then swings on the slip fitter's knob. That travel stops where the head would meet the pole — the figure the slider stops at is the travel you really get, not the fitter's nominal rating. On Solara II the camera aims too: its ball tilts inside the housing, on a control of its own. Drag to walk round the joint.
Made on the pole,
kept in the pole.
A solar light is an energy budget with a lamp on the end of it. The panel sets what comes in on a short winter day; the pack decides how many of those days the light can miss and still work. Both are sized per model — the table under Specification carries the per-model figures.
Monocrystalline, multi-busbar
Multi-busbar monocrystalline cells at 23% conversion, 24% at module level, with output held to ±3%. PID-resistant and tested to IEC 62804, rated to 18 V or 36 V, and warranted 10 years on materials against a 25-year linear output curve — longer than the pole is usually specified for.
LiFePO₄, Grade A+ cells
More than 4000 cycles, with two cell grades: standard cells charge from 0 °C, and advanced cells charge down to −20 °C for winter sites where a standard pack would simply refuse. Both discharge across the full −20…60 °C range. Capacity is measured, not estimated — see the monitor module below — and maintenance is guaranteed for 5 years.
The stack, and the tube
it lives in
E-Lite builds its own packs, and a pack is not a box of cells with a lid on it. The case is a single extruded aluminium section with several cell rows formed into it, closed at each end — one cap blind, the other carrying the gland, the charge port, the breather and the test button. Inside, the LiFePO₄ stack is joined by nickel busbars and watched by its own protection boards. Hover either half to hold it and drop the other back.
Every cell is inspected, and every finished pack is parameter-verified and aged through three complete charge–discharge cycles before it ships. A pack that has its fault found on the pole instead of on the bench costs a truck, a lift and a night of darkness, which is why the ageing step is not the one that gets skipped.
Everything it knows,
and who it tells.
From here on it is the same pole seen from further away: the node that runs it, the six things it senses about itself, the console it reports to and the mesh it reports over.
Flexible IoT Connectivity Architecture
The charge controller and the IoT radio are integrated together, so what the light decides and what the platform sees cannot drift apart. IP67 with 3000 V TVS surge protection. Work mode, dimming profile and thresholds are all set remotely; a light with no signal falls back on its own programme rather than on darkness.
What the light knows
about itself
Six of them, and not one is decoration. The light switches on its own panel voltage, counts the charge in and out of its pack, knows if it has been leaned on, and refuses to charge a frozen battery. What they measure is what the console shows — there is no second, friendlier set of numbers.
Dusk to dawn
The panel is the sensor: the controller switches on the falling panel voltage against a programmable 5.0–10.0 V threshold, with a 0–30 minute delay so passing cloud does not cycle the light.
Two power levels
In motion mode the light holds 100/60/30/70% while something is moving and drops to 30/20/10/20% when nothing is — the saving that buys the small hours without leaving a street dark.
Measured, not modelled
A high-precision battery monitor module reports voltage, current, power, real capacity and time remaining. A pack that is ageing shows up as a falling capacity years before it shows up as a dark pole.
Permanently powered GPS
A mini tracker hidden in a part of the battery pack an installer cannot reach, followed live from the app. It is there for the battery packs that leave site on the back of somebody’s truck.
Gyroscope and accelerometer
The installed angle is locked at commissioning. A knock, a lean or an attempt to unbolt the head raises an alarm at the operation centre and sends an SMS from the management system.
0 °C charge protection
Standard lithium is not charged below freezing. The controller holds charge off until the pack is warm enough to take it, which is the single thing that most shortens a solar light’s life in a cold climate.
A camera that
runs on its own sun.
Not a camera cabled into the lighting battery. It carries its own photovoltaic module, its own pack and its own 4G link, so a pole that has dimmed to 30% at two in the morning is still a pole that is watching — and a camera that stays up whether or not the lighting network does.
Nothing taken
from the light
The light stays an ordinary iNET node: its controller reports over the RF mesh to a gateway and on to iNET Cloud, exactly as a pole without a camera does. The two paths are independent by design, so neither failure takes the other with it. Fitted model: .
One console
for the whole estate.
A cloud central management system for provisioning, monitoring, controlling and analysing lighting. Multi-tenant, reached from a browser on a laptop, tablet or phone, and scaling to thousands of locations under a single interface.
A lit street, in real time.
Three poles on one kerb of a four-lane carriageway, spaced at 3.5× mounting height so the throws cross and the road lights evenly. Take one light or all three, dim them, switch them — or leave the photocell to it and watch a whole day pass in seventy-five seconds.
A working simulation of the iNET Cloud console. Every control responds the way it does in the real thing, so you can try the platform here before you see it on your own estate. Nothing is switched: commands end in a notice saying so, and every name, location and reading on screen is invented. Hover a control for a hint, and each screen explains itself when you arrive. Map data © OpenStreetMap contributors, ODbL.
Every light, on the map
Create, import and edit device attributes — fixture coordinates and type, fixture wattage before and after retrofit, lamp type. iNET performs GIS‑to‑GPS matching to correlate fixture IDs with physical devices, so device IDs need not be recorded during installation.
Map and floor plan
A map-based interface for status, health and overrides, extended to floor plans for indoor structures such as parking garages. Faulty devices are located from the same view that reported them.
Groups and priority
Assets group logically for event scheduling, and a group can hold several schedules at once — regular and special events kept apart, with the engine resolving the day from event priority rather than from the operator remembering.
Collected several times a day
Light level, energy use and faults, with per-point monitoring levels for voltage, current and power factor when a circuit needs investigating.
Failure finds you
Built-in alarms per asset class, configurable to e-mail and SMS. The system watches for lamp failure, night outages and day burners, and the logs export as CSV.
Asset, selection or city
Energy reports compare performance across lighting assets; data logs trend light level, wattage and schedules over a period. Everything exports to CSV or PDF.
Every interface to iNET uses SSL with AES encryption. Access is role-based and can be restricted at different levels of a geozone hierarchy, password policy follows industrial standards, and a timeout after repeated failed logins closes the obvious attack.
Multi-tenant and built on current web technology, so it ports across platforms and web interfaces. Supported on Chrome, Firefox and Edge.
Every node
relays for its neighbours.
The gateway talks to the server over cellular or ethernet, and to the nodes over SUB-1GHz radio. Between the nodes it is a mesh: any node can act as a repeater, so an instruction from the server reaches a light that cannot hear the gateway directly.
SUB-1GHz, nine channels
IEEE 802.15.4 on ISM 315 / 433 / 490 / 868 / 915 / 928 MHz, 9-channel direct sequence spread spectrum at +22 dBm from the node and +24 dBm from the gateway. Node to node and node to gateway both reach 1 km line of sight.
Wireless
It leverages its integrated 4G modem to connect over any cellular carrier. Downstream nodes operate independently and remain unaffected regardless of the gateway’s connectivity method.
100–200 nodes, 2000 m across
One gateway carries up to 200 controllers out to 1000 m line of sight, and the mesh between them spans a network up to 2000 m in diameter. Beyond that, add a gateway rather than a trench.
A gateway.
A node per light.
Two devices carry the whole system. The gateway is the bridge to the server; the node is the part that actually holds a luminaire's behaviour, and there is one in every fixture.
The bridge to the server
Connects the field controllers to the management system through an ethernet link for LAN, or a 4G link through an integrated cellular modem. Star-mesh repeater topology, wall or pole mounted, with a built-in lightning surge arrester on every antenna port and a 5-year limited warranty.
Two ways to fit it
Standard installs inside the fixture, normally in the drive box — the choice for new luminaires and for retrofits where the housing opens. NEMA fits the NEMA 7-pin socket on top of a street light or area fixture, with an onboard photocell, and needs no one inside the housing at all.
The controller’s clock steps the level from block to block. Traffic changes nothing in this mode.
The sensor raises the level the moment it sees movement; after a short delay it falls back.
After the panel’s voltage crosses the day/night threshold (D/N Thr) the light waits a short delay (D/N Dly) — at dusk and again at dawn — so a passing cloud does not switch it.
TOT (dashed) and Time 5 are counted back from the sunrise the controller recorded the day before, so Time 5 ends as the sun comes up on a short night and a long one. Times and levels are an example.
Solara I
and Solara II.
From the Solara I and Solara II Integrated Solar Street Light & Smart Surveillance specifications. Panel and battery are sized on 6 hours of charging. The table follows the series selected at the top of the page.