String drop-out
A string suddenly stops conducting while its peers continue. Caught within seconds, not the next report.
Real-time, string-level solar plant monitoring
Catch every dead string in seconds, not the next morning.
SolarPing is real-time, string-level solar plant monitoring. It watches every string, MPPT and inverter across every plant you run, and pings your team on Telegram the instant something fails.
1.4smedian fault detection
57plants monitored live
92MWpunder continuous watch
A failing string can hide for hours, and quietly burn your yield.
Vendor dashboards were built for record-keeping, not for catching faults. The cost shows up on the generation report.
Dashboards refresh slowly
Cloud portals update every 10–15 minutes. A dead string bleeds power long before anyone sees a number change.
No alarm when it matters
A string at 0.00 A just sits in a long table. Nothing flashes, nothing pings. You have to spot it yourself.
Too many sites to watch
One manager, 8–10 plants, hundreds of strings. Watching every dashboard for 10 hours a day is impossible.
Y-string faults stay hidden
When one leg of a paired Y-string fails, the other keeps producing, so the loss looks invisible on aggregate views.
From the panel to your pocket, in four steps.
SolarPing plugs into the loggers you already have. No new hardware, no portal logins for your team.
Read
Pulls live string, MPPT and inverter data every 1–2 seconds from your existing loggers.
Detect
Smart rules spot the fault, even at single-string level, and filter out dawn/dusk noise.
Alert
Pushes an instant alert to your Telegram group and tags the person who needs to act.
Resolve
Auto-clears the alert when the issue is fixed. Every event is logged for audit.
String-level intelligence for your whole portfolio.
SolarPing reads live data down to every individual string and flags the faults that actually cost you energy.
Partial under-output
A string running below its peers (early soiling, connector wear or shading), surfaced before it worsens.
Y-string imbalance
Paired-string layouts where one leg fails while the other masks the loss on aggregate dashboards.
Inverter offline
An inverter that stops reporting during sunlight hours is flagged immediately, not hours later.
Overheating & faults
Insulation drops, thermal derating and ground faults, pre-empted before a shutdown costs you a day.
Underperformance
An inverter quietly lagging its peers' yield is ranked and flagged in plain language every evening.
Coming soon
The SolarPing plug-and-play logger.
Today SolarPing works with the loggers you already have. Soon, you'll be able to drop in our own purpose-built device. No configuration, no integration project.
- › Connect it to the inverter and power on. It's live in minutes.
- › Auto-discovers strings, MPPTs and inverters on the network.
- › Streams string-level data straight into SolarPing. Zero setup.
- › Built for sites with older or no compatible logger.
Want early access? Join the waitlist →
Why teams switch
The same fault, found two very different ways.
A string sitting at 0.00 A. Here is what each approach does about it.
Vendor cloud dashboard
- ✕ The 0.00 A reading appears only after a 10–15 minute delay
- ✕ No alarm is raised, it just sits in a long table
- ✕ Someone must open every site and scan every string
- ✕ Easy to miss, and every missed fault is lost power
With SolarPing
- ✓ The fault is caught within 1–2 seconds of happening
- ✓ An instant alarm lands in your Telegram group
- ✓ The responsible person is tagged automatically
- ✓ Nothing to watch. The alert finds you
What operators tell us.
Paraphrased from pilot conversations. Names withheld for commercial confidentiality.
We were spending the first hour of every day reading yesterday’s yield report and chasing why one plant came in 3% low. By the time we found the dead string the loss was already booked.
Our Sungrow dashboard pinged us when an inverter tripped, never when a single string went dark. On a 6 MWp plant that is real money sitting on the roof.
Telegram works because our field guys already live in it. A new portal would have been ignored. The alert tells them which combiner box to open, and that is the whole conversation.
How much are undetected faults costing your plants?
When a string or inverter fault goes unnoticed on a slow dashboard, it quietly drains revenue every hour. Use this free solar power-loss calculator to estimate what real-time detection recovers across your portfolio, then book a demo to measure it precisely on your own sites.
sites
MW
/ kWh
hrs
faults
Annual revenue you stop losing
₹47.2 L / year
across 18 plants · 72 MWp total · ₹3.9 L / month · 56,160 kWh recovered monthly
- Portfolio capacity
18 plants × 4 MW = 72 MW - Productive hours lost per fault
6 hrs hidden × 0.65 sun-overlap = 3.9 hrs - Energy lost per fault, per plant
4,000 kW × 2.5% × 3.9 hrs = 390 kWh - Monthly portfolio loss
390 kWh × 8 faults × 18 plants = 56,160 kWh - Annual revenue at risk
56,160 kWh × ₹7/kWh × 12 mo = ₹47.2 L
2.5% = conservative per-fault production loss (industry field studies put it at 2–5%). 0.65 = fraction of a fault's hidden window that overlaps productive sun. Both numbers stay fixed; only the five inputs above move.
A conservative estimate. Actual recovery depends on your fault mix and detection latency baseline. After the demo, a 1-week trial on one of your plants measures it precisely on your own strings.
Already watching real megawatts, every second.
57
Solar plants
Monitored live, pan-India
92
MWp under watch
And scaling each quarter
4,128
Monitoring points
Strings, MPPTs and inverters
1.4s
Median detection latency
vs 10–15 min on vendor portals
Everything you need to know.
SolarPing detects string, MPPT and inverter faults within 1–2 seconds of them occurring. That compares with the 10–15 minute delay typical of vendor cloud dashboards, where a failing string can quietly burn hours of yield before anyone on your O&M team even notices.
Yes. SolarPing is logger-agnostic and integrates with the data loggers and inverters you already have: Huawei, Sungrow, SMA, Solis, Growatt, Delta, ABB and most other major brands. There is no new hardware to install, no firmware to flash, and no rip-and-replace migration.
SolarPing pushes an instant alert into your Telegram group the moment a fault is detected, tags the engineer responsible for that plant, and auto-clears the alert once the issue is resolved. The chat only ever shows what is genuinely wrong, so the team trusts every ping.
Yes. SolarPing is built for portfolio operators. It monitors every string across every plant simultaneously, so a single manager can confidently oversee dozens of sites without watching dashboards all day. Per-plant routing means each fault reaches only the right team.
No. SolarPing uses sunrise/sunset suppression, wiring-map awareness and debounce logic, so dawn and dusk ramps, partial shading, and unwired positions never trigger noise. You only get pinged for real, persisting faults, keeping alert fatigue near zero across your operation.
Start with a 30-minute demo on your portfolio data. If it fits, we run a 1-week trial on a single plant at no cost: we connect to your existing logger, ingest historical baseline, map your wiring, tune thresholds, and set up your Telegram alert group. You see real detections on your own strings before signing a contract.
Get started
See SolarPing on your own plant before you commit.
Book a 30-minute demo on your portfolio data. If it fits, we run a one-week trial on a single plant at no cost so you see real detections on your own strings before any contract.
Contact us
[email protected]Book a demo call →Or ask about a 1-week, 1-plant trial after the demo. We reply within one business day.