Troubleshooting
Check common connection, reading and configuration problems, and collect information for support.
Find the relevant topic below, then look for your symptom or message in its table and follow the suggested checks. Some checks use the dashboard; others require checking power, network connections or device wiring.
Connections
| Symptom or message | What to check |
|---|---|
| Header shows Device unreachable | The RevPi may be powered off, restarting or unreachable over the network. Wait one minute. If the status remains red, check that the RevPi has power and that the network cable is connected at both ends. |
| MQTT disconnected | The connection to intelliThings CORE is down. The RevPi continues reading inputs and running local automation rules. If the connection does not recover, open System → Device identity and IoT, check the certificates and use Reconnect broker. |
| Vidya reports that it is unreachable | The RevPi cannot connect to the AI service. Check the RevPi’s internet connection. If it is working, report the problem from System. |
Readings and outputs
| Symptom or message | What to check |
|---|---|
| A device card shows No data yet | The RevPi has not received readings from this device. Open the device’s page and use the wiring diagram to check both ends of the connection. Check Advanced to see whether the device is responding. |
| A reading is not arriving at the platform | Open Measurements. Check that the reading is selected for sending and that you have saved the page. Also check that the connected device is providing readings, as described under No data yet above. |
| A platform command has no effect | Check that the command key exactly matches Command key on the output’s page. The output configuration must be saved and enabled. |
| No modules appear on the port map | The modules have not been configured. Open Change the module layout on the I/O page and add the modules fitted to the RevPi. See Changing which modules are fitted for the steps and the effect of applying the layout. |
| A reading uses unexpected units | Set the port’s multiplier and unit, then check the result in the preview. See Inputs & outputs. |
Device-specific problems
| Symptom or message | What to check |
|---|---|
| ABB readings show only dashes | Check the wiring: P → A and N → B. Match the baud rate and parity to the settings on the meter’s display. Make sure the scale is not assigned to the same serial port. Check Advanced for the specific error. |
| DGT readings show dashes | Check the wiring: P → terminal 3 and N → terminal 4. Make sure the mode (ASCII/Modbus) and baud rate in Advanced match the transmitter’s settings. |
| Shelly shows Unreachable | Check that the Shelly has power, is connected to the same network as the RevPi and uses the address entered in its configuration dialog. |
| The camera shows no image | Check the camera’s IP address and that the live stream is enabled, then click Reconnect. “Stream daemon unreachable” means the camera helper service on the RevPi is restarting. Try Reconnect and check Autostart under Advanced on the camera page. |
Saving changes
| Symptom or message | What to check |
|---|---|
| Saving is rejected with “... the configuration changed elsewhere ...” | Another user has saved changes since you opened the page. Click Discard, review the current settings, then make your changes again. |
| Saving is rejected with a field error | Check the indicated field. A duplicate datastream name or command key is a common cause; these names and keys must be unique on the RevPi. |
Contact support
If Report a problem is configured on your RevPi, open System, describe the problem and click Send report. This sends your description and device information to support.
Otherwise, click Create diagnostics package on System and attach the downloaded ZIP file to your support email or ticket. Downloading the package does not send it automatically.
See System for the information included in each option.