Troubleshooting

Values travel one way in Overvis HMI: an endpoint connects to the equipment, parameters read values through it, and dashboards and reports show the parameters. When something is missing on a dashboard, check the chain in that order.

The in-app assistant can check the chain for you. Open it with AI, name the dashboard, parameter, or endpoint, and describe what you see. See Get help from the assistant.

The page does not load

If Overvis HMI shows Cannot connect to the server, the service is unavailable or your browser cannot reach it. Keep the page open: it returns to the app on its own when the server answers, or you can select Retry. Changes that failed are not sent again, so check your last edit and enter unsaved form entries again.

If a page shows Could not load this page, check your connection and select Retry.

If the problem continues, check your Internet connection, then contact support at support@overvis.com or helpdesk.overvis.com. These work even when the app does not.

A dashboard shows no values

Start at the equipment and work towards the dashboard:

1. Open Setup → Endpoints and check that the endpoint the values come from is Connected. If it is not, fix the endpoint first; see The endpoint does not connect.
2. Open Setup → Parameters, select the parameters, and turn on Live. If a value shows an error here, the problem is in the parameter or the device, not in the dashboard. Check the parameter’s source: its unit ID, table, and address must match the device’s register map.
3. If the values read correctly in Setup but not on the dashboard, the dashboard shows other parameters than you expect. Open the dashboard’s settings, or edit its tiles, and check which parameters it uses.

Every workspace member can read live values. Writing a value needs the Operator role or higher.

The endpoint does not connect

Open the endpoint’s status page. Check that the endpoint is Enabled, and compare Setup address with Active address. If the state is Error, Disconnected, or Connecting, Last error says why the last attempt failed. The full checklist is in Fix connection problems.

A device behind a gateway does not answer

An MC252 or another gateway can be Connected while a device on its RS-485 bus does not answer. Each parameter reports only on its own device. Device not responding means the gateway was reached but the device at that unit ID did not answer. Check the device’s unit ID, its power and wiring, the A and B lines, and that its serial settings match the gateway’s.

You cannot edit or write

Changing endpoints, parameters, dashboards, and reports needs the Editor, Admin, or Owner role. Writing a value needs the Operator role or higher, and the parameter itself must be writable. If you cannot do something you need, ask a workspace admin for another role; see Roles.

A dashboard is missing from the sidebar

The dashboard may be disabled. Open Setup → Dashboards and enable it. Also check that you are in the right workspace.

A dashboard needs a rebuild

A coded dashboard that shows that it needs a rebuild was built for an older version of the dashboard host. In its pulled checkout, run pnpm hmi build with the current CLI, then pnpm hmi push.

If hmi build fails with has no exported member for @overvis/hmi-shared or @overvis/hmi-workspace-ui, the name moved to a subpath of the package. Import it from the subpath the package reference lists; see Update imports after a package upgrade.

Local CLI commands fail

• The pull command fails. Each pull command works once and expires. Open Workspace settings → General, copy a new command under Develop locally, and run it.
• No local or pulled workspace is found. Run the command inside the pulled project folder.
• The CLI asks to be updated, or fails with client_outdated. The server needs a newer @overvis/hmi-cli. Update the HMI packages together, as the CLI prints and Versions and updates describes. A local workspace app that says it is too old is fixed by the same update.
• The push reports conflicts. Run pnpm hmi pull, settle the conflicts with pnpm hmi resolve, and push again; see Resolve sync conflicts.
• A push was interrupted, or fails with push_id_reused. See Retry an interrupted push.
• The workspace API key is rejected. It was revoked or belongs to another workspace. Pull the workspace again to get a new key.

Other errors print a code and details. Look the code up in the CLI reference.

Still stuck

Open the user menu and choose Report a problem. Describe what happened and what you expected. Attach a screenshot only if you want it included. The form shows a reference once the report is accepted. You can also ask the assistant to report the problem for you and confirm the report it prepares.

For a problem with the assistant, include the Chat ID from the top of the chat; see Report an assistant problem.

To follow up on a ticket, open Helpdesk tickets in the user menu, or go to helpdesk.overvis.com.