Event Severity Guide
STATUS
Telemetry received within the last 60 minutes.
WARNING
Telemetry delayed (60–90 minutes).
ERROR
No telemetry received for more than 90 minutes.
Total Logs
168
Today's Events
1
Warnings
1
Errors
3
Recent Device Events
| Date | Time | Device ID | Device Name | Village | Status | Message |
|---|---|---|---|---|---|---|
| 10 Jul 2026 | 11:38:08 | 003C0006 | AWS-1 | Sonegaon | WARNING |
Telemetry delayed by 68 minutes
|
| 10 Jul 2026 | 11:14:32 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1143 hours[ (68624 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 11:11:28 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1143 hours[ (68621 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 11:10:44 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1143 hours[ (68620 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 10:43:26 | 0011001B | AWS-2 | Ambejavalge | STATUS |
Device online
|
| 10 Jul 2026 | 10:43:26 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1143 hours[ (68593 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 10:43:26 | 00120028 | AWS-3 | Khanapur | STATUS |
Device online
|
| 10 Jul 2026 | 10:26:14 | 0011001B | AWS-2 | Ambejavalge | ERROR |
No telemetry received for 1 hours[ (96 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 10:26:14 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1142 hours[ (68576 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 10:26:14 | 00120028 | AWS-3 | Khanapur | ERROR |
No telemetry received for 358 hours[ (21496 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 10:08:05 | 0011001B | AWS-2 | Ambejavalge | WARNING |
Telemetry delayed by 78 minutes
|
| 10 Jul 2026 | 10:08:05 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1142 hours[ (68558 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 10:08:05 | 00120028 | AWS-3 | Khanapur | ERROR |
No telemetry received for 358 hours[ (21513 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 09:42:46 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1142 hours[ (68532 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 09:42:46 | 00120028 | AWS-3 | Khanapur | ERROR |
No telemetry received for 358 hours[ (21487 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 09:13:01 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1141 hours[ (68503 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 09:13:01 | 00120028 | AWS-3 | Khanapur | ERROR |
No telemetry received for 357 hours[ (21458 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 09:12:24 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1141 hours[ (68502 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 09:12:24 | 00120028 | AWS-3 | Khanapur | ERROR |
No telemetry received for 357 hours[ (21457 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 09:11:07 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1141 hours[ (68501 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 09:11:07 | 00120028 | AWS-3 | Khanapur | ERROR |
No telemetry received for 357 hours[ (21456 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 09:10:59 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1141 hours[ (68500 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 09:10:59 | 00120028 | AWS-3 | Khanapur | ERROR |
No telemetry received for 357 hours[ (21455 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 09:09:30 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1141 hours[ (68499 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 09:09:30 | 00120028 | AWS-3 | Khanapur | ERROR |
No telemetry received for 357 hours[ (21454 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 08:53:35 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1141 hours[ (68483 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 08:53:35 | 00120028 | AWS-3 | Khanapur | ERROR |
No telemetry received for 357 hours[ (21438 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 08:48:54 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1141 hours[ (68478 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 08:48:54 | 00120028 | AWS-3 | Khanapur | ERROR |
No telemetry received for 357 hours[ (21433 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 08:47:22 | 0011001B | AWS-2 | Ambejavalge | STATUS |
Device online
|
| 10 Jul 2026 | 08:47:22 | 00330028 | WLD-1 | Bhanasgaon | STATUS |
Device online
|
| 10 Jul 2026 | 08:47:22 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1141 hours[ (68477 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 08:47:22 | 00120028 | AWS-3 | Khanapur | ERROR |
No telemetry received for 357 hours[ (21432 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 08:19:26 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1140 hours[ (68449 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 08:19:26 | 0011001B | AWS-2 | Ambejavalge | WARNING |
Telemetry delayed by 69 minutes
|
| 10 Jul 2026 | 08:19:26 | 00180028 | WLD-2 | Khanapur | STATUS |
Device online
|
| 10 Jul 2026 | 08:19:26 | 00330028 | WLD-1 | Bhanasgaon | ERROR |
No telemetry received for 1252 hours[ (75159 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 08:19:26 | 00270028 | WLD-1 | Sonegaon | STATUS |
Device online
|
| 10 Jul 2026 | 08:19:26 | 00120028 | AWS-3 | Khanapur | ERROR |
No telemetry received for 356 hours[ (21404 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 10 Jul 2026 | 08:19:26 | 003C0006 | AWS-1 | Sonegaon | STATUS |
Device online
|
| 09 Jul 2026 | 15:55:05 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1124 hours[ (67465 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 09 Jul 2026 | 15:55:05 | 0011001B | AWS-2 | Ambejavalge | ERROR |
No telemetry received for 2 hours[ (125 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 09 Jul 2026 | 15:55:05 | 00180028 | WLD-2 | Khanapur | WARNING |
Telemetry delayed by 85 minutes
|
| 09 Jul 2026 | 15:55:05 | 00330028 | WLD-1 | Bhanasgaon | ERROR |
No telemetry received for 1236 hours[ (74175 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 09 Jul 2026 | 15:55:05 | 00270028 | WLD-1 | Sonegaon | ERROR |
No telemetry received for 58 hours[ (3537 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 09 Jul 2026 | 15:55:05 | 00120028 | AWS-3 | Khanapur | ERROR |
No telemetry received for 340 hours[ (20420 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 09 Jul 2026 | 15:55:05 | 003C0006 | AWS-1 | Sonegaon | ERROR |
No telemetry received for 2 hours[ (125 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 09 Jul 2026 | 15:52:32 | 00100028 | WLD-2 | Bhanasgaon | ERROR |
No telemetry received for 1124 hours[ (67462 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 09 Jul 2026 | 15:52:32 | 0011001B | AWS-2 | Ambejavalge | ERROR |
No telemetry received for 2 hours[ (122 minutes)]
Power loss / Network issue (cannot determine exactly)
|
| 09 Jul 2026 | 15:52:32 | 00180028 | WLD-2 | Khanapur | WARNING |
Telemetry delayed by 82 minutes
|