Local dashboard
Reached over the node's own WiFi hotspot at 10.42.0.1, within a few metres of the node.
For installation, first tests, maintenance and any check that must work when the node is offline.
Operation
Dashboards, monitoring and reports
MIND AIoT gives you two views of the same node: a local dashboard on site and a cloud dashboard from anywhere. Use the local view during installation and service, and the cloud view for day-to-day monitoring.
On this page
Two dashboards, two jobs
Cloud dashboard
Reached over the internet at app.mannamind.ai, from anywhere.
For history, configuration, alarms, analytics and reports across one node or many.
Changes to sensors, equipment and behaviour are made in the cloud dashboard and reach the node when it is online.
What the local dashboard shows
- Sensor data — the current reading from each configured sensor.
- Climate status — each equipment channel and whether it is on, off or following automatic control.
- Connection status — whether the node has internet and cloud connectivity.
- Configuration — which sensors and controllers the node is using, and whether each is reporting.
- Manual control — a switch for each channel, for testing wiring and equipment.
What the cloud dashboard shows
- Live and historical data — current readings and graphs over time.
- Units — every node on the site, with its name, location and status.
- Equipment status — which outputs are active and how they have been cycling.
- Configuration — sensors, controllers, targets and alarm rules.
- Change history — what was changed and when.
- Power — average and cumulative consumption where the installation measures it.
Keep the site's timezone and location correct. They affect timestamps and any weather-related analysis.
Testing equipment
- Connect to the local dashboard and set every output to off.
- Switch each channel on, one at a time, and confirm the correct device starts.
- Switch it off and move to the next channel.
- When every channel has been checked, return the node to automatic operation.
If a channel does not switch its device, the fault is between the controller, the relay and the equipment wiring. Stop and fix it before leaving the node in automatic operation.
Alarms
Alarms tell you when something needs attention instead of waiting for you to notice a graph. Configure them in the cloud dashboard.
| Alarm | What it detects |
|---|---|
| Connection | The cloud stops receiving updates from the node. This usually means the node or the site has lost power. |
| Climate | A measured value leaves the limits you set. |
| Sensor | A sensor stops reporting. |
| Power | Unusual consumption compared with normal operation. |
Start with connection and climate alarms and add the others once you know the site's normal behaviour. Add the people who should be contacted for each node.
Analytics and reports
Beyond alarms, ask the questions your operation raises. Agents analyse the stored data and produce the answer as a view or a report.
- Compare rooms or periods and show the differences that matter.
- Investigate an unusual reading and explain what happened.
- Summarise equipment run time, power use or out-of-range conditions.
Describe the report you want in the same way you described the behaviour during setup. Availability of individual report features is agreed for the project. Data export and API access are part of the platform's development and are confirmed for each installation.
Daily checks
- Open the cloud dashboard and look at the trends, not only the current values.
- Confirm every configured sensor is reporting.
- Review any alarm that fired and note what caused it.
- After maintenance, test each channel on the local dashboard before returning the node to automatic operation.