Troubleshooting

Use this checklist to isolate the most common problems when a sensor is not visible in Visamic.

No messages arrive

Check the connection in this order:

1. Confirm that the publisher is connected to the expected broker and port.
2. Confirm that the publisher and Visamic use exactly the same topic.
3. Subscribe to the topic with an MQTT client and verify that messages are actually published.
4. Check the username, password, TLS mode, and certificate when the broker requires them.
5. Review the device connection status and open its logs when available.

Messages arrive but no values are visible

• Validate the payload as JSON before publishing it.
• Check that the attribute names in the payload match the attributes configured in the Thing.
• Check whether the values are numbers or strings and use the type expected by the selected panel or function.
• Confirm that the Thing and the datapanel are enabled.
• If historical values are expected, confirm that data retention is enabled and that the datapanel loads retained data.

The dashboard is empty

Confirm that the datapanel uses the intended Thing and that at least one attribute, function, or filter is selected. Filters and display limits can hide values even when the connection is healthy.

TLS or authentication errors

Confirm the broker hostname, port, credentials, and certificate as a set. A certificate for one host cannot necessarily be used with another host. Do not paste passwords or private certificates into support requests.

Before requesting help

Record the environment, device status, topic, connection mode, and a redacted sample payload. Do not include passwords, tokens, private certificates, or other sensitive data.

Broker hosts, ports, URLs, and available fields may change between environments. Verify them in the current application before treating an older example as authoritative.