Skip to content

Troubleshooting ​

The machine says Waiting for first reading ​

Nothing that matches a reading has arrived.

  • Open the machine's setup page. Names listed there arrived but match no reading: add them with one click.
  • Refused messages are listed there too, with the reason.
  • Nothing listed at all usually means the connection never got in. Check the points below.

MQTT connects but nothing appears ​

  • The topic must be exactly kealink/<machine-id>/data, with the machine's own id.
  • The payload must be a JSON object or array, not plain text.
  • Values must be numbers, true or false. Strings only go to readings of kind Text.

MQTT does not connect ​

  • Port 50607, with TLS on. Plain MQTT on 1883 or 8883 is not offered.
  • The username and client id are the machine id, the 26 character string, not the machine's name.
  • Outgoing port 50607 must be open on the site's firewall. If it cannot be opened, use HTTP on 443.
  • Only one connection per machine id. A second gateway or an old flow with the same id knocks the first off, and they take turns.
  • A board without a clock refuses the certificate. Set the time over NTP first.

HTTP returns 401 ​

The username must be the machine id itself, not the words "machine id" or the machine's name. The reply says which part is wrong.

HTTP returns 404 ​

The machine id in the address does not exist, or the address is doubled. In the Kealink node for Node-RED, Address is https://app.kealink.co.nz and nothing more.

Some values arrive and some do not ​

The reply's unknownKeys lists names that matched nothing. Common causes:

  • timestamp or time instead of ts
  • A tag renamed in the gateway after the reading was set up
  • machine_id or serial in the payload, which is not needed

The chart times are wrong ​

ts must be Unix time in milliseconds. Seconds read as a time in 1970 and are replaced by arrival time. A gateway with a wrong clock does the same; leave ts out and arrival time is used.

Buffered readings are missing ​

Readings older than 24 hours are not accepted, and arrays hold up to 200 entries. Send a long backlog in several arrays, oldest first.

I am not getting alert emails ​

  • Check your address is the alert contact or has Alert emails switched on.
  • Check the spam folder.
  • Warnings are never emailed; only alarms are.
  • An alert with Alert after N minutes waits that long.
  • At most 30 alert emails per company per hour are sent.

A dashboard widget says Not set up yet ​

The reading or machine it showed no longer exists, or a copied dashboard found no matching reading. Choose another in the designer.