Operation
Troubleshooting
Most MIND AIoT problems are found in the same order: power, then network, then the component, then the configuration. Work down this page before changing hardware.
On this page
Diagnostic order
- Power — is the node on, and do its lights show activity?
- Network — does the node have internet, and does the local dashboard say so?
- Sensors — is each configured sensor reporting?
- Controller — is the controller your installation uses selected in the dashboard?
- Equipment — does each channel switch its device from the local dashboard?
- Configuration — does the cloud configuration match what is physically connected?
- Restart — reboot the node from the local dashboard and wait ten minutes.
Change one thing at a time and note the result. A fault that survives a restart and a fresh configuration is usually wiring or hardware.
The node will not start
Use these checks when the node has power but no WiFi hotspot appears and nothing reaches the cloud.
The hotspot never appears
- Wait at least three minutes after power-on.
- Move within a metre or two of the node and try another phone or computer.
- Check the node's power and activity lights. No lights means a power problem.
- Confirm the encryption key is attached and the memory card is fully seated.
- If none of that helps, re-write the node's memory from MIND AIoT Node OS and start the installation again.
Encryption fails or never finishes
The USB memory stick is the most common cause. Re-write the memory card, use a different, good-quality stick and try again. Confirm the internet connection stayed up for the whole process; a drop can reset it.
The device code step fails
The connection to the cloud usually dropped during installation. Re-write the card, repeat the installation on a stable connection and create the device code again.
Sensors are offline
- Check the sensor configuration in the cloud dashboard and confirm it matches what is physically connected.
- Check the local dashboard: after a start or a configuration change, sensors can take 10–15 minutes to appear.
- Confirm the node is online, so it can receive the latest configuration.
- For wireless sensors, check the address recorded during setup and the battery.
- Check the wiring and any mode switch on the interface board.
- Test with one sensor only. Remove the others from the configuration, confirm the first one works, then add the rest back one at a time.
Equipment does not respond
- From the local dashboard, switch the channel on manually and watch the device.
- Check the relay for that channel, including any indicator light that shows a control signal is present.
- Check the fuse for that equipment.
- Confirm the correct controller is selected in the dashboard.
- Connect the equipment directly to power to prove the device itself still works.
- Confirm the equipment restarts by itself after a power loss. Equipment that stays off after an interruption will not respond when the node cycles power.
If equipment runs continuously and never stops, check the set limits, the equipment's capacity for the space and whether the sensor is reading correctly.
The node is offline in the cloud
- Allow up to 15 minutes. A node can take this long to connect after a start or reboot.
- Check the Ethernet connection and confirm the network uses automatic addressing.
- Connect the local dashboard and read the connection status: first internet, then cloud.
- If the internet works but the cloud does not, the site's firewall or name resolution is the likely cause.
- Reboot the node from the local dashboard and wait ten minutes.
Data appears in the dashboard with a delay
Two different waits are involved. A node can take up to 15 minutes to connect to the cloud after a start. Once connected, how often it reports depends on the configuration of that installation. Wait for a noticeably new reading rather than a fixed number of minutes.
Recovering a node
When a node will not start normally, install it again from MIND AIoT Node OS.
- Write MIND AIoT Node OS to the node's memory. A card and encryption key pair that already exists can be reused for a fresh installation.
- Assemble the node as during installation and complete encryption.
- Create the device code and contact the Manna team to reactivate the licence.
- Register and link the node again if the dashboard requires it.
A memory card and encryption key cannot be separated after installation: a key from one node cannot be paired with another node's card. Keep the pair together and labelled. A backup card cloned for the same node model and used with the same key is a valid spare.
Full steps are in Install MIND AIoT Node OS.
When to contact us
- Licence activation or reactivation is needed.
- A node must be removed or moved.
- A replacement encryption key is required.
- A component needs support that is not covered by these guides.
- The steps above did not resolve the problem.
Have the device code, the site name and the node name ready and contact us.