Is This Your Problem?
Bird droppings create severe thermal hotspots in individual cells and fire risks that string-level monitoring misses. Tucson detection and exclusion guidance.
Get Matched With a Local ProLocalized soiling like bird droppings creates severe thermal hotspots in individual cells, which can trigger fire risks that string-level monitoring misses
This is the one soiling problem that is a safety issue rather than a performance issue, and it is the one most likely to go undetected for years. Droppings do not cover the array evenly like dust; they land on specific cells, in the same places, and they come back. A string-level monitoring chart will not flag a site like that, because the array as a whole is still producing at a normal-looking number while one cell on one module runs hot enough to damage itself.
Why one spot on one cell is worse than a film across the array
Cells in a module are wired in series, so the current in a string is limited by the worst-performing cell in it. When a dropping shades part of one cell, that cell can no longer pass the current the rest of the string is generating. It becomes reverse-biased and starts dissipating the power of the surrounding cells as heat. That is the thermal hotspot. Bypass diodes inside the module junction box are designed to route current around a group of cells when they are badly shaded — but a spot that covers only part of one cell may not drive the group hard enough to activate the bypass, which means the heat has nowhere to go except into that cell and its encapsulant.
This is precisely why the problem is described as something string-level monitoring misses. Monitoring that aggregates a whole string, or even a whole array, is looking at the average of many modules. A hotspot is a local event on one cell, and a small energy loss spread across a long string barely moves the total. The damage, however, is entirely local: discoloured and browned encapsulant, solder-joint fatigue, delamination and, in the worst case, the fire risk that the source flags.
Tucson's bird pressure is structural, not seasonal. Tiled roofs with an air gap under the field, ridge lines, and the shaded gap behind a tilted array are roosts. Vent pipes, HVAC units, and any hardware that gives a bird a perch near a module edge attract repeat deposits in exactly the same location. Pool and fountain areas draw doves in numbers, and arrays mounted near pools accumulate deposits on the modules facing the water. Whatever the reason a bird chose your array, it tends to choose the same module every time.
| Roof feature | Why birds use it | Where deposits land | What it does to the array |
|---|---|---|---|
| Ridge line and peak | High perch with a clear view | Top rows of the array, heaviest on the upper edge | Persistent shading of the same cells after every visit |
| Tile roof field with gaps under the tiles | Roosting shelter | Under-array area, then the module edges above the roost | Both rear-plane obstruction and top-surface deposits |
| Vent pipes and HVAC hardware | Ready-made perch close to the modules | The module directly beside the perch | The same cell shaded repeatedly — a textbook hotspot site |
| Pool, fountain or water feature | Water access | Modules facing the water, often the whole bottom row | Recurring deposits that no single cleaning resolves |
| Nearby trees and roost trees | Overhead cover | Modules under the canopy | Droppings plus pollen and leaf debris at the same time |
| Shaded gap behind a tilted array | Shelter out of the sun | Rear plane, frame edges and roof surface below | Rear shading and trapped debris that is hard to see |
Descriptive of typical Tucson roof conditions. The key pattern is location and repetition — a hotspot problem is defined by deposits recurring on the same cells, not by the total volume of dirt.
What hotspots cost the homeowner
There are three costs, and they escalate in that order. The first is yield: each shaded cell drags down the whole string it belongs to, and because the deposit is permanent between cleanings, that drag persists every sunny day. The second is module damage: sustained reverse-bias heating degrades the cell, the solder joints and the encapsulant, which is permanent and not reversible by cleaning. The third is risk, and it is the reason this problem deserves a different level of attention than dust — localised hotspots are a fire precursor, and monitoring that cannot see them will not warn you before damage becomes failure.
Worked example, illustrative and easy to redo: a Tucson array producing 14,000 kWh a year at a blended 16¢ per kWh. A persistent localised defect that costs 2% of production is 280 kWh, about $45 a year, and roughly $1,120 over a 25-year life — small enough to be ignored, which is exactly the trap. If the same defect degrades into a module that must be replaced, the arithmetic changes entirely: you pay for the diagnosis, the replacement module, the labor, the re-roofing at the attachment points, and the production lost while the string is down. Catching hotspots early is a maintenance cost; catching them late is a capital cost.
| Method | Can see | Cannot see | Why it matters here |
|---|---|---|---|
| String-level monitoring | Aggregate output of a long string | A localised hotspot on one cell | The stated blind spot: a hot cell barely moves the string total |
| Physical inspection from the array edge | Deposits on visible surfaces; recurrence in the same place | Mid-array cells hidden by tilt; anything under the array | Cheap, effective and repeatable at every cleaning |
| Thermal imaging of the array | Hot cells and anomalous heat patterns | The cause of the heat — dropping, crack or failed diode | Turns an invisible hazard into a located one |
| Module-level monitoring (optimisers, microinverters) | Per-panel underperformance | An individual hot cell inside a healthy-looking panel | Narrows the search to the right module |
| Current-voltage curve trace | Electrical signature of a shaded, degraded or faulty module | Exactly where on the glass the shade is | Confirms damage severity before replacement |
| Junction box and bypass diode check | Failed or degraded bypass diodes | Cell-level damage inside the laminate | The module protection device is part of the diagnosis, not separate from it |
Even module-level monitoring only shows a panel's average behaviour; a single hot cell inside that panel remains invisible without thermal imaging or a physical look.
How to detect it before it becomes a fire risk
Detection is mostly about looking in the right place at the right time, and about not trusting the dashboard to tell you what is happening on one cell.
- Inspect after every cleaning and after every storm. Walk the array edge and look at the modules nearest to perches, ridges, vents and pools. Recurrence in the same spot is the signature to look for.
- Look for permanent staining, not fresh deposits. Fresh droppings are obvious. Brownish or dark etched marks that survive cleaning are the residue of a cell that has been running hot, and those marks are the real warning.
- Book thermal imaging on a sunny, still day. A thermal inspection localises hot cells and shows whether the deposit has already damaged the module or is only shading it. This is the single most useful paid check on a suspected hotspot array.
- Compare modules, not just strings. Where you have optimisers or microinverters, look for one panel tracking consistently below its neighbours over weeks. Where you do not, a current-voltage trace on the suspected string will separate a damaged module from a soiled one.
- Check the junction boxes. Faulty bypass diodes inside module junction boxes can cause full string failures or localized overheating, so a suspected hotspot is also a reason to have the diodes tested rather than only the glass cleaned.
- Do not diagnose from the dashboard alone. If your only evidence is a modest dip in total output, you are reading the one signal this failure mode deliberately does not create.
| Action | Fixes | Timing | Practical caution |
|---|---|---|---|
| Prompt removal of fresh deposits | Removes the shading before heat builds | Within days of the deposit, not months | Soak first; scraping dry droppings scratches the glass |
| Soft-brush wash with mild solution and a clean rinse | Deposits plus general soiling | Morning, cool glass | No abrasives, no hard-water source; see the soiling page for method |
| Thermal imaging inspection | Locates hot cells and confirms damage | Sunny, still day | A finding on one module justifies checking the whole array |
| Physical exclusion at the roost | Prevents recurrence, which is the actual problem | Before the next nesting season | Mesh and deterrents must not block airflow or shade the modules |
| Module replacement | Restores the string where a cell is already damaged | After thermal or electrical confirmation | Requires the same attachment and flashing work as a new install |
| Bypass diode and junction box service | Removes a separate overheating path | At the same visit as diagnostics | A failed diode and a soiled panel can present identically from the ground |
Sequence matters: exclude the roost and clean promptly, or the same cells will be soiled again next month and every paid inspection repeats itself.
What to do about it
Treat deposits as urgent and recurrence as the root cause. Fresh droppings should come off within days rather than at the next scheduled maintenance, because the damage window opens as soon as the cell is shaded on a hot, high-irradiance afternoon. Soak the deposit with water, lift it with a soft brush, and rinse clean. Never chip at a dried deposit with a scraper or a dry rag; the glass will lose that trade.
Then stop the deposit from coming back. Identify the perch itself — the ridge, the vent pipe, the HVAC cabinet, the tile gap — and address it there. Physical exclusion is the durable fix: mesh and deterrents on perches, screening where tiles leave an entry gap, and removing whatever feature is attracting birds to that exact spot. Any exclusion hardware has to respect the array's airflow and rear clearance, which is the same constraint discussed in flush-mount restrictions on bifacial arrays, and it must not create new shading.
Where you cannot eliminate the perch — a pool, a roost tree, a neighbouring structure — move to a scheduled inspection rather than an on-call one. Add a look at the known-favourite modules to every cleaning, and put a thermal inspection on the calendar if the array is near water or heavy roosting. A five-minute visual check at the right location is what separates a $45-a-year shading loss from a module replacement.
Finally, fix the documentation side. When a module is replaced or a hotspot is confirmed, keep the inspection report, the thermal images and the serial number record. If the damage is later claimed under a product warranty, an owner who can show that a specific cell was running hot before failure is in a far stronger position than one who can only report that a module stopped working.
Related Tucson problems
Hotspots sit at the intersection of soiling, electrical faults and physical damage. For the general dust and pollen case read soiling from dust and pollen; for the mechanism behind cracks that also produce hot cells read cell micro-cracking; for the thermal side of the same physics read cell efficiency losses from high heat. The full local index is at common solar problems in Tucson.
Next Step
Every case above resolves the same way in practice: someone qualified looks at the actual array, measures what is really happening, and only then prices a fix. Call (520) 593-0496 or request a free match with up to three local pros who work on Tucson roofs every week — no cost, no obligation.
