đ¯ Journey A: I Know My Symptom
Use this page when you already know what's wrong â a device is offline, a specific alert fired, flow readings look off. Find your symptom below and go straight to its debug steps. No need to work through the full funnel.
If nothing below matches, or you're not sure what's actually wrong yet, switch to 𧊠Journey B: Start From the Beginning â it walks the full chain step by step and surfaces likely causes as you go.
đ Find Your Symptomâ
| Symptom | Likely area | Go to |
|---|---|---|
| đ´ Device shows offline on the dashboard | IoT / Sensor | Offline due to network issue |
| đ´ Device offline, never reconnects, no telemetry activity at all | IoT | Device damage or Power supply failure and powered off |
| đ´ Device offline right after a power cut | Sensor / IoT | Power supply failure and stops measuring |
| â ī¸ Device online, but no data / stopped mid-stream | Sensor | Sensor gets damaged and stops measuring in between |
â ī¸ device_status alert firing | Sensor | Communication cable gets damaged or Sensor gets damaged |
đ no_flow alert â flow reading is zero/flat | Sensor | Flow meter starts counting false water flow or Follow the right installation practices |
đĄ no_level_variation alert â level reading is flat | Sensor | Follow the right installation practices or Selection of right sensor |
đĩ water_balance_leakage alert | Sensor | Flow meter starts counting false water flow |
| đ Data is arriving but the dashboard doesn't reflect it | Sensor / Software | Reverse flow conditions |
| đ§ Values look junk / wildly out of range | Sensor | Junk values posted from the sensor or Data outside the permissible range |
| đ ī¸ Issue started right after a service visit / replacement | Sensor | Improper re-configuration during replacement/service activities |
| đ Issue started right after a deployment/release | Software | New deployment affects the real-time data pipeline |
| đŠī¸ Many unrelated devices/zones affected at once | Software | Unexpected system downtime due to failure of any architecture component |
| đŗ Device offline around a recharge/payment due date | Recharge | Devices go offline due to failed recharge on time |
| đŗ Whole account/site unreachable, payment related | Recharge | Cloud system goes down due to payment failure on time |
𧰠Quick Tool Jumpâ
If you'd rather go straight to a tool instead of a symptom:
| Tool | Use it for |
|---|---|
| đ Offline Dashboard | Is the device connected right now? |
| đ Uptime Metrics | Has it been sending data reliably over time? |
| đļ IoT Telemetry | Live, per-device connection + data arrival. |
| đ¨ Data Integrity Alerts | Is incoming data flagged as wrong? |
| đī¸ Data Validation | What raw data actually landed, incl. reverse flow flag. |
| đ Unit Reset | Fix action after confirming reverse flow / bad config. |
| đ User Logs | What changed recently, and who changed it. |
After You Fix Itâ
Each linked factor page has a How to verify checklist and a Mitigation / Status callout. If you followed the steps and the symptom is resolved, you're done. If the steps don't explain what you're seeing, don't guess further here â move to 𧊠Journey B: Start From the Beginning and let the funnel narrow it down layer by layer.