Data logger
Fitted by the DISCOM at installation; reads the inverter every 15 minutes.
How it works
From a reading on a roof to a fixed panel.
Scroll to follow one reading from a 3 kW roof in Dwarka, through the diagnosis, to the family's single WhatsApp message.
- 1
Every roof reports itself
A DISCOM data logger, the inverter's cloud or a camera clip sends yesterday's reading to AWS IoT Core. The family does nothing.
- 2
Compared with what the sun allowed
Satellite sunlight and haze for that exact roof and day give the output it should have made.
- 3
Smog, dust or fault, told apart
Smog drops both lines together. Dust widens the gap every dry day. A fault collapses output overnight.
- 4
Claimed, chased, verified
A free-maintenance claim goes to the vendor with evidence. Miss the deadline and the DISCOM steps in. When output recovers, the family hears once.
One reading, 12 OctSimulated
Rooftop3 kW · Dwarka
Inverter9.1 kWh today
Data loggerevery 15 min
AWS IoT CoreMQTT over TLS
AgentsStrands + Bedrock
Expected vs actual, 14 daysSimulated
Should have made11.6
Made9.1
Performance100%
What the agent checkedSimulated
Smog in the airAlready counted in “expected”
Ruled outInverter faultNo fault code, no sudden drop
Ruled outDust on panelsGap widens every dry day; rain reset it
DiagnosedCase SS-0142 · free cleaningFiled
- Complaint sent to the vendorChart, readings and ₹ lost attached
- Deadline missedNo visit within 3 days
- Escalated to the DISCOMFull case file, automatically
- Fix verified from new readingsPerformance back to 96%
The only message the family getsआपके panels पर धूल थी। हमने मुफ्त सफाई करवा दी। Output वापस 96% पर है।
Diagnosis rules · v1
Simple rules the agent can explain
The rules decide; the model explains each decision in plain words and acts through tools. Every decision is logged with its reason.
PerformanceActual ÷ expected, where expected already includes that day's haze.Measure
SmogExpected is low but performance stays above 90%.No action
Dust3-day average below 91% and falling over 5 dry days. Closes itself if rain restores it.Claim cleaning
FaultPerformance below 60% overnight, or the inverter reports a fault code.Claim repair
Verified fixPerformance back above 93% after the visit.Close case
Works with any roof
No new hardware on most roofs
Inverter cloud
The maker's cloud API, pulled once a day with the family's consent.
Camera clip
An ESP32-CAM on FreeRTOS photographs the inverter screen. No wiring touched.
WhatsApp photo
The family sends a picture of the screen; Amazon Bedrock reads the numbers.
Consent once. Then only good news.
- Vendor installs, QR sticker on the inverterConsent recorded once
- Readings arrive every dayThe family does nothing
- Problem found, claim filed, fix verifiedAll automatic
- One WhatsApp message, in HindiPlus a monthly money report
Cases arrive already investigated.
- Open the consoleHealth and ₹ being lost, by zone
- Check the vendor leaderboardWho's slow, who's overdue
- Work the escalation queueReadings, chart and notices attached
- Act on repeat offendersUnder rules that already allow it