Enrollment Failure Due to Device ZUID Issue on Zebra Printers

Publish Date: Last Modified Date: SOTI Connect, SOTI MobiControl
2496

Summary

This article discusses an issue faced by customers using Zebra printers, specifically related to the factory-programmed unique ID (ZUID). This issue can impact their ability to enroll printers into the SOTI ONE Platform.

Related SOTI ONE Platform Products

SOTI Connect;SOTI MobiControl

Related Device OS

Link-OS

Issue Description

Customers are experiencing difficulties with their Zebra ZT510 printers failing to enroll into SOTI Connect due to a malformed Client ID linked to the printer's ZUID.

The following error can be seen in the broker logs:

A log screenshot showing multiple entries of client connections and disconnections. Many lines indicate the disconnection reason as "Sent CONNECT with malformed client id."

Event logs from HiveMQ:


2024-12-09 21:00:17,412 - Client ID: UNKNOWN, IP: 136.********* was disconnected. reason: No CONNECT sent in time.
2024-12-09 21:00:20,713 - Client ID: UNKNOWN, IP: 170.********* was disconnected. reason: TLS handshake not finished in time.
2024-12-09 21:00:23,321 - Client ID: UNKNOWN, IP: UNKNOWN disconnected ungracefully.
2024-12-09 21:00:28,533 - Client ID: UNKNOWN, IP: 142.********* was disconnected. reason: Sent CONNECT with malformed client id.
2024-12-09 21:00:37,095 - Client ID: UNKNOWN, IP: 136.******** was disconnected. reason: No CONNECT sent in time.
2024-12-09 21:00:37,665 - Client ID: UNKNOWN, IP: 24.****** was disconnected. reason: TLS handshake not finished in time.

Environment

Zebra ZT500 and ZT600 printers

Symptoms

  • Inability to enroll ZT510 printers into SOTI Connect.
  • An error message indicating malformed Client ID.
  • Device ZUID does not report as expected.
    • Check the device ZUID with the command:
      • Execute the following command on the printer using Zebra Setup Utilities:
        !U1 getvar "device.zuid"
      • The ZUID of a device that works as expected is an alphanumeric value.
        A screenshot of a Zebra printer communication tool displaying the same command ! U1 getvar "device.zuid" executed, but with a response showing a different ZUID: T3JZ42900E6E9DA1D691 
      • The ZUID of a ZT510 device that is having issues has special characters.
        A screenshot of a Zebra printer communication tool displaying a command ! U1 getvar "device.zuid" executed, with a response showing the device ZUID as *ïð~3DA6CBDDD4713C 

Cause

The root cause has been identified as a manufacturing issue where the ZUID is not programmed correctly on some devices, requiring repair to reprogram it.

Issue Resolution

Submit a case to Zebra Support - https://support.zebra.com/ - for resolution. 

 

Additional Information

  • The ZUID is critical as it is used for the MQTT topic and MQTT client ID.
  • Each printer generates its ZUID during production unless manually modified, which is generally unsupported.
  • Affected printers may not need to be returned to Zebra for repair:
    • A software update may be provided by Zebra Support to address the issue. The customer should upgrade to their preferred official Link-OS release that is also certified on SOTI Connect. 

Was this helpful?